# CVE-2020-7599: Exposure of Sensitive Information in Gradle publish plugin

> Attackers can replace published plugins by exploiting AWS pre-signed URLs leaked in logs when using the info log level.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cv78-v957-jx34

## What is CVE-2020-7599?

CVE-2020-7599 is a medium-severity vulnerability in com.gradle.plugin-publish, published on 30 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

All versions of com.gradle.plugin-publish before 0.11.0 are vulnerable to Insertion of Sensitive Information into Log File. When a plugin author publishes a Gradle plugin while running Gradle with the --info log level flag, the Gradle Logger logs an AWS pre-signed URL. If this build log is publicly visible (as it is in many popular public CI systems like TravisCI) this AWS pre-signed URL would allow a malicious actor to replace a recently uploaded plugin with their own.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2020-7599?

4 open source packages ship an affected version, including com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin and com.gradle.publish:plugin-publish-plugin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin` | Maven | All versions | 0.11.0 |
| `com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin` | Maven | All versions | 0.11.0 |
| `com.gradle.publish:plugin-publish-plugin` | Maven | All versions | 0.11.0 |
| `com.gradle.publish:plugin-publish-plugin` | Maven | All versions | 0.11.0 |

Products: Gradle Plugin Publishing.

## How do I fix CVE-2020-7599?

Upgrade com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin to 0.11.0 or later.

## Is CVE-2020-7599 being exploited?

There is no known exploitation of CVE-2020-7599 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7599 and fix it if it is affected.

What it is: CVE-2020-7599 is a medium-severity vulnerability in com.gradle.plugin-publish, published on 30 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7599 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin (Maven): affected all versions; fixed in 0.11.0
- com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin (Maven): affected all versions; fixed in 0.11.0
- com.gradle.publish:plugin-publish-plugin (Maven): affected all versions; fixed in 0.11.0
- com.gradle.publish:plugin-publish-plugin (Maven): affected all versions; fixed in 0.11.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-7599/ (Markdown: https://insights.sbomify.com/CVE-2020-7599/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-7599
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-7599
- OSV: https://osv.dev/vulnerability/CVE-2020-7599

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-7599/
Summaries are generated and may contain mistakes; the official description above is the record.