Incorrect version dectection for cross-spawn node module #9822
Closed
shadows552
started this conversation in
False Detection
Replies: 2 comments 1 reply
-
|
In all honesty I'm a bit out of my depth so please be patient with my sub-optimal bug reporting skills. My apologies in advance if I ran into a fixable issue that isn't a bug. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hello @shadows552 Try scanning the image with the -f json flag and check the PkgPath field for this vulnerability. Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
IDs
CVE-2024-21538
Description
I have cross-spawn 7.0.6 in my package.json, though Trivy is detecting cross-spawn 7.0.3 as my installed version. (I tried to figure the stuff out about interlaced dependencies and as far as I can tell that isn't the issue here? but I'm not confident)
Also, .trivyignore only works for this vulnerability when running Trivy locally, though when using .trivyignore in GitHub actions, the .trivyignore is loaded, but ignored.
Reproduction Steps
Local: 1. run npm install 2. Build docker image without cache 3. run "trivy image --severity CRITICAL,HIGH --ignore-unfixed --scanners vuln bbf-backend:latest"Target
Container Image
Scanner
Vulnerability
Target OS
No response
Debug Output
Version
Checklist
-f jsonthat shows data sources and confirmed that the security advisory in data sources was correctBeta Was this translation helpful? Give feedback.
All reactions