Gradle Shadow: Zip Slip path traversal in ShadowCopyAction — no independent entry-name sanitization
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| GradleUp | shadow | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Gradleup | Shadow |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-rr8v-fxxf-c986 | Gradle Shadow: Zip Slip path traversal in ShadowCopyAction — no independent entry-name sanitization |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.140% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gradleup
Gradleup shadow |
|
| Vendors & Products |
Gradleup
Gradleup shadow |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Gradle Shadow plugin creates fat or uber JARs and supports file transformation and package relocation. Prior to version 9.6.0, Shadow does not independently validate ZIP entry names before writing them to its output archive. A malicious dependency can cause traversal entry names to be preserved when the applicable archive-processing path does not reject them. Some affected Shadow implementations process dependency archives directly, so upgrading Gradle alone does not universally prevent this behavior. If the resulting archive is extracted without path traversal protection, attacker-controlled files can be written outside the intended destination. This issue is fixed in version 9.6.0. | |
| Title | Gradle Shadow: Zip Slip path traversal in ShadowCopyAction — no independent entry-name sanitization | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|