Trivy detects CVE in pom file even though the specific dependency has been upgraded to the fix version #8036
Closed
SemProvoost
started this conversation in
Bugs
Replies: 1 comment
-
Hello @SemProvoost I found a problem and create #8049 and #8050 Regards, Dmitriy |
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
Example pom:
When you run
trivy fs . --scanners vuln --debug
on this, Trivy will still detect the CVE. Even though we specifically setnetty-common
to version4.1.115.Final
:Desired Behavior
We would expect Trivy to mark the CVE as solved here.
Actual Behavior
Trivy still detects the CVE.
However:
If I set the
netty-handler
version instead ofnetty-common
-> Trivy doen't detect the CVE anymore.Reproduction Steps
Target
Git Repository
Scanner
Vulnerability
Output Format
None
Mode
Standalone
Debug Output
Operating System
macOS & Linux
Version
Checklist
trivy clean --all
Beta Was this translation helpful? Give feedback.
All reactions