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

Can spring-web 5.3.32 fix the vulnerability CVE-2016-1000027 and release a new 5.x version? #32300

Closed
zzwwyfbruce opened this issue Feb 21, 2024 · 1 comment
Labels
status: duplicate A duplicate of another issue

Comments

@zzwwyfbruce
Copy link

Affects: <Spring Framework version>
If there is a vulnerability (CVE-2016-1000027) in spring-web 5.3.32, can it be fixed and a new 5.x version be released?

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Feb 21, 2024
@grubeninspekteur
Copy link

grubeninspekteur commented Feb 21, 2024

Duplicates #24434

Java serialization is intrinsically unsafe, there is nothing Spring could do here to fix it. If you don't use the HttpInvoker mechanism with Java serialization, then you are not affected. If you are using HttpInvoker and the API you built is accessible by a third party, add a serialization filter to whitelist the types you need to accept.

Removing HttpInvoker in 5.x would be a breaking change. If a security scanning tool brought you here and you are not affected, you should mark the CVE as a false positive.

@bclozel bclozel closed this as not planned Won't fix, can't repro, duplicate, stale Feb 21, 2024
@bclozel bclozel added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

4 participants