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

DependencyTrack treats newer version as vulnerable while it is not #3583

Open
2 tasks done
jmezach opened this issue Mar 27, 2024 · 0 comments
Open
2 tasks done

DependencyTrack treats newer version as vulnerable while it is not #3583

jmezach opened this issue Mar 27, 2024 · 0 comments
Labels
defect Something isn't working in triage

Comments

@jmezach
Copy link

jmezach commented Mar 27, 2024

Current Behavior

Our DependencyTrack instance is currently reporting Microsoft.Data.SqlClient version 5.2.0 as vulnerable for CVE-2024-0056. According to the CVE that vulnerability only exists in versions 2.1.7, 3.1.5, 4.0.5 and 5.1.3, but not 5.2. I've asked the maintainers of this package what the regular procedure is and whether the CVE needs updating, but according to them that is not how it is supposed to work which makes sense since that would create a maintenance hell. See dotnet/SqlClient#2391 for reference.

Steps to Reproduce

  1. Upload the attached BOM to DependencyTrack bom.json
  2. DependencyTrack shows the project as being vulnerable for CVE-2024-0056

Expected Behavior

I would expect DependencyTrack to not show version 5.2.0 of Microsoft.Data.SqlClient as being vulnerable

Dependency-Track Version

4.10.1

Dependency-Track Distribution

Container Image

Database Server

PostgreSQL

Database Server Version

No response

Browser

Google Chrome

Checklist

@jmezach jmezach added defect Something isn't working in triage labels Mar 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect Something isn't working in triage
Projects
None yet
Development

No branches or pull requests

1 participant