pnpm incorrectly parses tar archives relative to specification
pnpm
pnpm
7.33.48.6.8| @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 npm |
|
|
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.
From the CVE record · GitHub_M
pnpm parses tar archives differently from npm and the registry. If a user installs a crafted package with pnpm, they may receive a malicious version even though the package appears safe on the npm registry or when installed with npm.
Check installations of pnpm, @pnpm/exe, and the listed platform packages below 7.33.4 or from 8.0.0 to below 8.6.8, and @pnpm/cafs below 7.0.5.