Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2022-31197 - postgresql critical security vulnerability at version 42.3.X and 42.4.0 #32126

Closed
shalomyasap opened this issue Aug 21, 2022 · 4 comments
Labels
status: declined A suggestion or change that we don't feel we should currently apply

Comments

@shalomyasap
Copy link

shalomyasap commented Aug 21, 2022

Please see the follow postgresql security issue
https://www.postgresql.org/about/news/postgresql-jdbc-versions-424142226-security-update-2492/
https://nvd.nist.gov/vuln/detail/CVE-2022-31197

CVE fixed at version 42.4.1

Regards,
Shalom

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 21, 2022
@bclozel
Copy link
Member

bclozel commented Aug 21, 2022

Dependency upgrades are usually done with our semi-automatic process, as stated in the issue template. There's no need to create such issues.

Spring Boot 2.6.x and 2.7.x is on the 42.3.x generation and it seems no patch will be released for this line:

We are not releasing a version for the 43.3.x release line and users are advised to upgrade to the 42.4.1 release to get the fix.

Spring Boot 3.0 is based on the 42.4.x generation right now.

I'm marking this for team discussion as we usually don't upgrade to minor versions in maintenance releases.

@bclozel bclozel added the for: team-attention An issue we'd like other members of the team to review label Aug 21, 2022
@dbahatSAP
Copy link

@bclozel it seems that the postgres team motivation not to upgrade 42.3.x generation is since they saw no reason for dependent components not to upgrade.
If this is not the case, can we please communicate it to them? (perhaps they will keep maintaining 42.3.x if they understand the motivation for spring boot 2.6.x / 2.7.x not to upgrade)

@snicoll
Copy link
Member

snicoll commented Aug 22, 2022

@dbahatSAP Feel free to raise an issue with them if you'd like to suggest a backport.

@philwebb
Copy link
Member

We're going to keep with our documented upgrade policy and remain on the 42.3.x line. It looks like users can upgrade safely themselves if they so wish. If pgjdbc/pgjdbc#2599 is accepted, we'll upgrade to a new 42.3.x version when it is released.

@philwebb philwebb added status: declined A suggestion or change that we don't feel we should currently apply and removed for: team-attention An issue we'd like other members of the team to review status: waiting-for-triage An issue we've not yet triaged labels Aug 22, 2022
@snicoll snicoll closed this as not planned Won't fix, can't repro, duplicate, stale Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

No branches or pull requests

6 participants