Fix critical tar-stream CVE-2024-53391 security vulnerability #10421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses a critical security vulnerability (CVE-2024-53391) in the
tar-stream
package that could allow directory traversal attacks during tar file extraction operations.Vulnerability Details
Fix Applied
Added a package resolution to force all dependencies to use the patched version:
This ensures that both direct and nested dependencies (via
tar-fs
andarchiver
packages) use the secure version of tar-stream.Verification
yarn list tar-stream
showed both v2.2.0 (vulnerable) and v3.1.7Impact
This fix follows the established security vulnerability resolution patterns documented in our SECURITY.md and aligns with recent CVE fixes in the project changelog.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
api.osv.dev
curl -s REDACTED -d {"package":{"name":"tar-stream","ecosystem":"npm"},"version":"2.2.0"}
(dns block)download.cypress.io
googlechromelabs.github.io
/usr/local/bin/node install.mjs
(dns block)https://storage.googleapis.com/chrome-for-testing-public/121.0.6167.184/linux64/chromedriver-linux64.zip
/usr/local/bin/node install.js
(http block)https://storage.googleapis.com/chrome-for-testing-public/138.0.7204.157/linux64/chrome-headless-shell-linux64.zip
/usr/local/bin/node install.mjs
(http block)https://storage.googleapis.com/chrome-for-testing-public/138.0.7204.157/linux64/chrome-linux64.zip
/usr/local/bin/node install.mjs
(http block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.