Arbitrary node_modules Directory Deletion in Google zx
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| zx | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Zx | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w87r-vg9q-crqm | zx Uses Incorrectly-Resolved Name or Reference |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.091% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google zx |
|
| Vendors & Products |
Google
Google zx |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When zx is invoked with --prefer-local=<path>, the CLI creates a symlink named ./node_modules pointing to <path>/node_modules. Due to a logic error in src/cli.ts (linkNodeModules / cleanup), the function returns the target path instead of the alias (symlink path). The later cleanup routine removes what it received, which deletes the target directory itself. Result: zx can delete an external <path>/node_modules outside the current working directory. | |
| Title | Arbitrary node_modules Directory Deletion in Google zx | |
| Weaknesses | CWE-706 | |
| References |
| |
| Metrics |
cvssV4_0
|