Trivy incorrectly reports vulnerability for non-affected version of logj4j-core CVE-2020-9488 #6061
Closed
levinebw
started this conversation in
False Detection
Replies: 2 comments 3 replies
-
Hello @levinebw We stopped using GitLab database for Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi @DmitriyLewen , does this DB update also apply to Aqua Enterprise Platform? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
[email protected] is not affected by CVE-2020-9488 however Trivy incorrectly reports a vulnerability finding.
The NVD states Fixed in Apache Log4j 2.12.3, however Trivy and Aquasec are reporing a vulnerability for Log4j 2.12.4
This was reported as fixed here (#3884), however it is not fixed. Evidence included shows there is still a bug.
Desired Behavior
There should be no finding reported for CVE-2020-9488 for [email protected]
Actual Behavior
Reproduction example
Reproduction Steps
Target
SBOM
Scanner
Vulnerability
Output Format
Table
Mode
Standalone
Debug Output
Checklist
trivy image --reset
Beta Was this translation helpful? Give feedback.
All reactions