False positive for commons-io #7673
Replies: 4 comments 3 replies
-
Bump. Having the same false positive. It got thoroughly checked that the image has commons-io version 2.15.1 and no sign of anything with 2.8.0, however the report says the same thing as author's - 2.8.0. |
Beta Was this translation helpful? Give feedback.
-
We are seeing an FP as well, but our tooling is not Trivy, so I suspect the problem is upstream somewhere - like a bad CPE. In our case |
Beta Was this translation helpful? Give feedback.
-
Trivy relies on
Also, a
|
Beta Was this translation helpful? Give feedback.
-
I confirm upgrading velocity-engine-core to 2.4 fixes the problem. My main source of confusion was, that we did neither see a finding using So all is fine, trivy is not in fault, I'm closing the report. Thanks again for the help! Best, Jan |
Beta Was this translation helpful? Give feedback.
-
IDs
CVE-2024-47554
Description
A scan of a containerised java applications having commons-io-2.16.1 as a dependency results is a finding claiming there is a vulnerable commons-io version 2.8.0; the issue being fixed in 2.14.0. Doing a fs scan of the sourcecode (we use gradle lockfiles) does not show this issue.
Here's the output of
trivy -f json
:Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Target OS
Alpine 3.19
Debug Output
Version
Checklist
-f json
that shows data sources and confirmed that the security advisory in data sources was correctBeta Was this translation helpful? Give feedback.
All reactions