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
vex documents from the --vex flag do get processed or applied to the output correctly #1836
Labels
bug
Something isn't working
Comments
Hi @willejs, thank you for the report, we've reproduced this issue on the latest Grype, 0.77.2: Without vex (CVE-2023-1255 shows up):
With vex (CVE-2023-1255 shows up):
On Grype 0.74.7, the CVE was filtered out as expected. We will take a look and see where the regression occurred. Thanks again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
When following the example here using the vex document specified, the vulnerability is rendered in the outputted report. This happens in any format.
vex.json
command
vexctl filter works
What you expected to happen:
I do not expect the vulnerability to be reported.
Maybe I am missing something here?
How to reproduce it (as minimally and precisely as possible):
see above
Anything else we need to know?:
Environment:
grype version
: 0.77.1cat /etc/os-release
or similar): mac/linux - tested bothThe text was updated successfully, but these errors were encountered: