feat: PURL matching with qualifiers in OpenVEX #5061
Merged
Conversation
This file contains 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
| } | ||
| return true | ||
| // Take the effective statement | ||
| stmt := stmts[len(stmts)-1] |
There was a problem hiding this comment.
Can you specify why we need get only last matched element?
If i understand correctly if we swap statements in example - we will not filter CVE-2021-44228.
But i am not sure that we need filter this CVE in this case.
Co-authored-by: DmitriyLewen <91113035+DmitriyLewen@users.noreply.github.com>
6 tasks
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.
Description
Trivy supports the exact match for PURL and BOM-Ref in OpenVEX.
https://aquasecurity.github.io/trivy/v0.44/docs/supply-chain/vex/#openvex
This PR uses PURL matching with qualifiers, as discussed here. Also, it bumps the OpenVEX spec to v0.2.0, including some breaking changes.
Related issues
Checklist