pnpm vulnerable to no-script global cache poisoning via overrides / `ignore-scripts` evasion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pnpm | pnpm | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Pnpm | Pnpm | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-3510 | The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one workspace leak into npm metadata saved in global cache; npm metadata from global cache affects other workspaces; and installs by default don't revalidate the data (including on first lockfile generation). This can make workspace A (even running with `ignore-scripts=true`) posion global cache and execute scripts in workspace B. Users generally expect `ignore-scripts` to be sufficient to prevent immediate code execution on install (e.g. when the tree is just repacked/bundled without executing it). Here, that expectation is broken. Global state integrity is lost via operations that one would expect to be secure, enabling subsequently running arbitrary code execution on installs. Version 9.15.0 fixes the issue. As a work-around, use separate cache and store dirs in each workspace. |
Github GHSA |
GHSA-vm32-9rqf-rh3r | pnpm no-script global cache poisoning via overrides / `ignore-scripts` evasion |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.977% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | pnom vulnerable to no-script global cache poisoning via overrides / `ignore-scripts` evasion | pnpm vulnerable to no-script global cache poisoning via overrides / `ignore-scripts` evasion |
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:pnpm:pnpm:*:*:*:*:*:*:node.js:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The package manager pnpm prior to version 9.15.0 seems to mishandle overrides and global cache: Overrides from one workspace leak into npm metadata saved in global cache; npm metadata from global cache affects other workspaces; and installs by default don't revalidate the data (including on first lockfile generation). This can make workspace A (even running with `ignore-scripts=true`) posion global cache and execute scripts in workspace B. Users generally expect `ignore-scripts` to be sufficient to prevent immediate code execution on install (e.g. when the tree is just repacked/bundled without executing it). Here, that expectation is broken. Global state integrity is lost via operations that one would expect to be secure, enabling subsequently running arbitrary code execution on installs. Version 9.15.0 fixes the issue. As a work-around, use separate cache and store dirs in each workspace. | |
| Title | pnom vulnerable to no-script global cache poisoning via overrides / `ignore-scripts` evasion | |
| Weaknesses | CWE-426 | |
| References |
| |
| Metrics |
cvssV4_0
|