Replies: 1 comment
-
Thanks for reporting. We're working on it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
I have an image, that contains a go binary (Prometheus 3.0.1). The go binary has made use of a package (x/[email protected]) with a reported vulnerability.
In Trivy 0.57.1 in prior, an OpenVEX document like the following would correctly suppress the vulnerability:
Trivy 0.57.1 output:
In Trivy 0.58.0, this is no longer being suppressed.
The commit which has introduced the change in behavior is 0627992.
In the
NotAffected
check, in Trivy 0.57.1, the product wasprometheus
, and the subcomponent wasx/crypto
. In Trivy 0.58.0, the product is nowx/crypto
and the subcomponent isnil
.I believe you want to keep the fidelity of product and subcomponent. I may have 2 go binaries in the image, both making use of
x/[email protected]
. One may make use of the vulnerable method, and the other may not. So I want the fidelity to say that one binary is not affected while the other is.Desired Behavior
Vulnerability is marked as suppressed.
Actual Behavior
Vulnerability is no longer marked as suppressed.
Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Output Format
None
Mode
Standalone
Debug Output
Operating System
Linux RedHat 8
Version
Checklist
trivy clean --all
Beta Was this translation helpful? Give feedback.
All reactions