-
Notifications
You must be signed in to change notification settings - Fork 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
cross-spawn 7.0.3 issue #2164
Comments
That is likely a dependency of NPM, and we do not update the image with a version of NPM except for the one shipped by Node.js. You can see if it is addressed upstream and if it will be in an upcoming Node.js release |
For other travellers npm/cli#7902 |
NPM has released the new version to fix this. so, do we have any plan to rebuild and release our base image to include this fix. |
For scanned images where npm is needed, I can update to a version of npm where this is fixed in my Dockerfile at references a published docker-node image: FROM node:18-alpine
RUN npm install -g npm@10.9.1 For scanned images where npm is not needed (i.e. not part of a build process), I would just remove npm (and yarn): FROM node:18-alpine
RUN npm uninstall npm -g \
&& rm -rf /opt/yarn-v$YARN_VERSION/ \
&& rm /usr/local/bin/yarn \
&& rm /usr/local/bin/yarnpkg \ |
Environment
Expected Behavior
High Vulnerability due to cross-spawn@7.0.3
Current Behavior
T
Possible Solution
update cross-spawn to version 7.0.5
update cross-spawn to version 7.0.5
Steps to Reproduce
Additional Information
The text was updated successfully, but these errors were encountered: