-
Notifications
You must be signed in to change notification settings - Fork 38.5k
BDSA-2024-5369 for springboot 3.4.0-M3 app #33755
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
Comments
This looks like https://spring.io/security/cve-2024-38809 which is fixed already in 6.2 release candidates. In any case, pointing to a RC release as vulnerable doesn't make sense as it's not supported in production in the first place and we only publish advisories for GA versions. I can't find any reference to BDSA-2024-5369 nor where this is metadata is declared and maintained. Can you point us to the source please? |
I'll assume this is a mistake in your vendor's metadata and I'll close this issue. Please reach out to your vendor for support. Note, our public advisories are the reference data for Spring vulnerabilities. |
Hello @bclozel Apologies to bump this ticket again. We waited for 3.4 to be released to post again (again, apologies) This time, I would like to attach the scan evidence: |
So this is in fact about https://spring.io/security/cve-2024-38809. The metadata on those screenshots looks fine to me. Maybe confirm that your application doesn't depend on a vulnerable version first? You can check the dependency version with Gradle:
Or Maven:
If the resolved version is not vulnerable, there is probably a problem with the tool. |
Indeed @bclozel
We will take it up with Black Duck. Thank you again. |
Hello team,
We run daily security scan tools (blackduck, sonarqube, dependecy check, owasp etc)
They are all flagging this:
This is for a latest (as of this writing spring boot 3.4.0-M3 app.
Could you please help take a look at this, and fix the CVE?
Thank you for your kind help
The text was updated successfully, but these errors were encountered: