CVE-2020-7599
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAll 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Gradle plugin-publish component (com.gradle.plugin-publish versions before 0.11.0) logs AWS pre-signed URLs at INFO log level during plugin publishing. When the --info flag is used during publishing, these pre-signed URLs are written to build logs. If these logs are publicly accessible (common in public CI systems like TravisCI), attackers can extract the URL and upload malicious plugin versions to replace the legitimate ones.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Gradle plugin-publish is in useSearch build configuration files (build.gradle, build.gradle.kts, settings.gradle, settings.gradle.kts) for the string 'com.gradle.plugin-publish' or 'plugin-publish'Affected if The plugin is present in the project dependencies or buildscript classpath
-
Determine the installed version of com.gradle.plugin-publishLocate where the plugin version is declared (typically in buildscript dependencies, plugins block, or gradle.properties with 'plugin-publish' version property) and note the version numberAffected if The version is below 0.11.0 (e.g., 0.10.0, 0.9.0, etc.)
-
Check if publishing uses the --info flagReview CI/CD configuration files (e.g., .travis.yml, GitHub Actions workflows, Jenkinsfile) for gradle publish commands that include the --info or --info flagAffected if The plugin publishing command includes --info or --logging=INFO flag
-
Determine if build logs are publicly exposedReview CI system settings to verify whether build logs for this repository are publicly accessible (common in public CI systems like TravisCI with default settings)Affected if Build logs are publicly accessible on the internet without authentication
You are affected if you use com.gradle.plugin-publish version below 0.11.0, publish with the --info flag enabled, and have publicly accessible CI build logs where the pre-signed URLs could be exposed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.11.0
Upgrade com.gradle.plugin-publish to version 0.11.0 or later, and ensure build logs are not publicly exposed in CI systems.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7599 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-7599 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data