-
Notifications
You must be signed in to change notification settings - Fork 30.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2021-3807 and CVE-2021-3918 findings for NodeJS 12.22.7 #41039
Comments
UPDATE: I think I see what this is about now. (See next comment.) |
(Maybe this is scanning modules used by the |
Yeah, that seems to be it. Node.js 12.22.7 ships with npm 6.14.15 which ships with [email protected] and [email protected] . Updating to the latest version of The relevant issue for this in the I don't think there's anything for Node.js to do except wait for /ping @nodejs/npm in case they have additional information to share. |
Yeah, you have the right of it, @Trott. Apologies for not following the open-source dependency chain down far enough (github-actions --> NodeJS --> npm). Thank you for filling in the gaps. |
@MylesBorins, @darcyclarke adding you, I assume it's already on your radar. |
I went though all the latest node docker releases with the following
And here are my results
|
Version
12.22.7
Platform
linux
Subsystem
No response
What steps will reproduce the bug?
Run a trivy scan against an image that uses NodeJS 12.22.7 and 3 HIGH and 1 CRITICAL vulnerabilities are reported.
How often does it reproduce? Is there a required condition?
Every time.
What is the expected behavior?
No HIGH or CRITICAL vulnerabilities.
What do you see instead?
Additional information
NodeJS 12 is being used for the self-hosted GitHub Actions images.
The text was updated successfully, but these errors were encountered: