@wakaru/cli arbitrary file write during bundle unpack
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pionxzh | wakaru | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pionxzh | Wakaru |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-7wpj-vvmv-pgm8 | @wakaru/cli arbitrary file write during bundle unpack |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.197% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pionxzh
Pionxzh wakaru |
|
| Vendors & Products |
Pionxzh
Pionxzh wakaru |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | wakaru is a JavaScript decompiler and unminifier toolkit. From 1.0.0 until 1.4.0, @wakaru/cli sanitizes bundle-controlled module filenames only once before writing extracted modules, so a crafted filename containing overlapping traversal sequences such as ....// collapses to ../ after sanitization and lets the final output path escape the selected output directory, allowing an attacker who can cause a user to run wakaru --unpack on a malicious bundle to write files outside that directory and, depending on the target path and environment, potentially achieve code execution. This issue is fixed in @wakaru/cli 1.4.0. | |
| Title | @wakaru/cli arbitrary file write during bundle unpack | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|