Repository navigation
Dependency-Track uses NVD severity instead of Trivy's vendor severity (Red Hat) for Trivy analyzer findings - but WHY? #7946
Replies: 3 comments 1 reply
|
That's how 5.1.0 works. Trivy's finding is kept, but its severity gets dropped when DT already has the CVE from NVD.
I traced this in the 5.1.0 source and haven't run it against a RHEL SBOM. If you want vendor severity for OS packages, a feature request is the way to go. |
|
Thanks for the detailed explanation! We tried disabling the NVD data source and re-created our projects, but findings still show NVD data. Is it expected that vulnerability records already mirrored from NVD remain in the database and keep their NVD data after the data source is disabled? If so, is there a supported way to purge them, or do re-analyses by Trivy update those records once NVD is disabled? |
|
Thank you very much for the thorough analysis and the source references, that cleared things up for us completely. As suggested, I've opened a feature request: #7947 For anyone landing here with the same question: in 5.1.0, findings from the Trivy analyzer show the NVD severity whenever the CVE already exists from the NVD mirror, so different severities compared to Trivy CLI on RHEL images are expected behavior. |
Uh oh!
There was an error while loading. Please reload this page.
Context
We have been scanning our RHEL-based container images (RHEL 8.10) with Trivy in our CI pipelines for a long time. We are now introducing Dependency-Track and use the Trivy analyzer (separate Trivy server container).
Observation
We scan the same SBOM with the same Trivy version (0.76.0). Trivy CLI and the Trivy analyzer find the same CVEs, but Dependency-Track shows a different severity than Trivy.
Trivy output (identical in both runs):
(columns: CVE, package,
Severity,SeveritySource)Dependency-Track shows the same CVEs as NVD records:
Our understanding
Trivy deliberately prefers the OS vendor's severity for OS packages, because the vendor knows how the package is built and configured (see Trivy docs, "Severity Selection"). Dependency-Track appears to display the severity of its own vulnerability record (NVD) instead of the severity selected by Trivy.
Questions
SeveritySource/VendorSeverity?Environment
Related
All reactions