https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 02:16:16 +0000 https://vulnerability.circl.lu/vuln/cve-2023-37478 <p><strong>Affected:</strong> pnpm</p> <p>pnpm is a package manager. It is possible to construct a tarball that, when installed via npm or parsed by the registry is safe, but when installed via pnpm is malicious, due to how pnpm parses tar archives. This can result in a package that appears safe on the npm registry or when installed via npm being replaced with a compromised or malicious version when installed via pnpm. This issue has been patched in version(s) 7.33.4 and 8.6.8.</p> <p><strong>Affected:</strong> pnpm</p> <p>pnpm is a package manager. It is possible to construct a tarball that, when installed via npm or parsed by the registry is safe, but when installed via pnpm is malicious, due to how pnpm parses tar archives. This can result in a package that appears safe on the npm registry or when installed via npm being replaced with a compromised or malicious version when installed via pnpm. This issue has been patched in version(s) 7.33.4 and 8.6.8.</p> https://vulnerability.circl.lu/vuln/cve-2023-37478 https://vulnerability.circl.lu/vuln/ghsa-5r98-f33j-g8h7 <p><strong>Affected:</strong> npm: pnpm, npm: @pnpm/exe, npm: @pnpm/linux-arm64, npm: @pnpm/linux-x64, npm: @pnpm/linuxstatic-arm64, npm: @pnpm/macos-arm64, npm: @pnpm/macos-x64, npm: @pnpm/win-x64, npm: @pnpm/cafs</p> <p>### Summary It is possible to construct a tarball that, when installed via npm or parsed by the registry is safe, but when installed via pnpm is malicious, due to how pnpm parses tar archives.</p> <p>### Details The TAR format is an append-only archive format, and as such, the specification for how to update a file is to add a new record to the end with the updated version of the file. This means that it is completely valid for an archive to contain multiple copies of, say, `package.json`, and the expected behavior when extracting is that all versions other than the last get ignored.</p> <p>This is further complicated by that during tarball extraction, all package managers are configured to drop the first path component, so collisions can be created simply by using multiple root folders in the archive, even without performing updates.</p> <p>When pnpm extracts a tar archive via tar-stream, it appears to extract only the _first_ file of a given name and discards all subsequent files with the same name.</p> <p>### PoC Create a root folder with the following layout: - `a/package.json` - `package/package.json` - `z/package.json`</p> <p>File contents: #### a/package.json ```json { &#34;name&#34;: &#34;test-package&#34;, &#34;version&#34;: &#34;0.1.0&#34;, &#34;description&#34;: &#34;This is a bad version of a test package&#34;, &#34;dependencies&#34;: { &#34;react&#34;: &#34;^15&#34; } } ``` #### package/package.json ```json { &#34;name&#34;: &#34;test-package&#34;, &#34;version&#34;: &#34;0.1.0&#34;, &#34;description&#34;: &#34;This is a bad version of a test package&#34;, &#34;dependen…</p> <p><strong>Affected:</strong> npm: pnpm, npm: @pnpm/exe, npm: @pnpm/linux-arm64, npm: @pnpm/linux-x64, npm: @pnpm/linuxstatic-arm64, npm: @pnpm/macos-arm64, npm: @pnpm/macos-x64, npm: @pnpm/win-x64, npm: @pnpm/cafs</p> <p>### Summary It is possible to construct a tarball that, when installed via npm or parsed by the registry is safe, but when installed via pnpm is malicious, due to how pnpm parses tar archives.</p> <p>### Details The TAR format is an append-only archive format, and as such, the specification for how to update a file is to add a new record to the end with the updated version of the file. This means that it is completely valid for an archive to contain multiple copies of, say, `package.json`, and the expected behavior when extracting is that all versions other than the last get ignored.</p> <p>This is further complicated by that during tarball extraction, all package managers are configured to drop the first path component, so collisions can be created simply by using multiple root folders in the archive, even without performing updates.</p> <p>When pnpm extracts a tar archive via tar-stream, it appears to extract only the _first_ file of a given name and discards all subsequent files with the same name.</p> <p>### PoC Create a root folder with the following layout: - `a/package.json` - `package/package.json` - `z/package.json`</p> <p>File contents: #### a/package.json ```json { &#34;name&#34;: &#34;test-package&#34;, &#34;version&#34;: &#34;0.1.0&#34;, &#34;description&#34;: &#34;This is a bad version of a test package&#34;, &#34;dependencies&#34;: { &#34;react&#34;: &#34;^15&#34; } } ``` #### package/package.json ```json { &#34;name&#34;: &#34;test-package&#34;, &#34;version&#34;: &#34;0.1.0&#34;, &#34;description&#34;: &#34;This is a bad version of a test package&#34;, &#34;dependen…</p> https://vulnerability.circl.lu/vuln/ghsa-5r98-f33j-g8h7