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-2016-1000027 SonaType finding with 5.3.27 #30640

Closed
aravindhan3112 opened this issue Jun 12, 2023 · 4 comments
Closed

CVE-2016-1000027 SonaType finding with 5.3.27 #30640

aravindhan3112 opened this issue Jun 12, 2023 · 4 comments
Labels
status: duplicate A duplicate of another issue

Comments

@aravindhan3112
Copy link

Affects: Spring v5.3.27


Currently we are using JDK 1.8 and Spring v5.3.27 and our application have few dependencies on the library upgrade to 6.x as per recommendation as it required JDK upgrade as well. Is there any workaround that we can get which is compatible with JDK1.8 or any other minor release version which we can use to remediate this issue.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jun 12, 2023
@bclozel
Copy link
Member

bclozel commented Jun 12, 2023

Please search for issues before submitting a new one, there are plenty of duplicates for this already.

See the following comment.

@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 Jun 12, 2023
@bclozel bclozel closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2023
@aravindhan3112
Copy link
Author

aravindhan3112 commented Jun 12, 2023

Hi @bclozel we looked for few relevant issues, but we are looking for a way which we can either look up for compatibility with JDK 1.8 and non vulnerable version. Can we get a reference ticket more relevant to our use case

@bclozel
Copy link
Member

bclozel commented Jun 12, 2023

This is the most relevant ticket. Please read the comment I've linked to in my previous message.

@aravindhan3112
Copy link
Author

Thanks for your quick support.

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

3 participants