feat(vex): add support for OWASP Risk Ratings in VEX documents#10193
Open
fahedouch wants to merge 2 commits intoaquasecurity:mainfrom
Open
feat(vex): add support for OWASP Risk Ratings in VEX documents#10193fahedouch wants to merge 2 commits intoaquasecurity:mainfrom
fahedouch wants to merge 2 commits intoaquasecurity:mainfrom
Conversation
Signed-off-by: Fahed Dorgaa <fahed.dorgaa@gmail.com>
…re specified Signed-off-by: Fahed Dorgaa <fahed.dorgaa@gmail.com>
📊 API Changes DetectedSemver impact: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this change?
The CycloneDX spec now recommends that tools consider ratings when prioritizing vulnerabilities (spec PR #722):
This PR lets Trivy use context-aware OWASP Risk Ratings from CycloneDX VEX documents. These ratings are generated by tools like vens (available in the Trivy plugin index) and provide context-specific risk scores based on factors like network exposure, data sensitivity, etc.
What's changed
OWASPRatingfield toDetectedVulnerability(optional withomitempty)ratingsblocksExample output
{ "VulnerabilityID": "CVE-2011-3374", "Severity": "LOW", "OWASPRating": { "score": 27.5, "severity": "medium", "vector": "SL:7/M:7/O:7/S:7/ED:4/EE:4/A:4/ID:5/LC:5/LI:5/LAV:5/LAC:5/FD:5/RD:5/NC:5/PV:5" } }Why this matters
This brings context-aware vulnerability prioritization to Trivy. The same CVE can have different risk scores depending on how and where it's deployed. For example, a vulnerability in an internet-facing service is way more critical than the same one buried in an isolated internal component.
This complements the generic CVSS approach with environment-specific assessment, which aligns with what the CycloneDX spec now recommends. And it's fully backward compatible, so existing workflows won't be affected.
Remove this section if you don't have related PRs.
Checklist