CVE-2020-7599: Exposure of Sensitive Information in Gradle publish plugin
Summary
CVE-2020-7599: Exposure of Sensitive Information in Gradle publish plugin. Affects com.gradle.publish:plugin-publish-plugin versions < 0.11.0. Fixed in 0.11.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Gradle publish plugin is a popular tool used for publishing Gradle plugins. It allows plugin authors to publish their plugins to various repositories. The plugin-publish plugin is a dependency of the Gradle publish plugin and is used to define the publication of the plugin. The vulnerability in com.gradle.plugin-publish allows for the exposure of sensitive information when publishing a Gradle plugin.
Vulnerability Detail
The vulnerability in com.gradle.plugin-publish before version 0.11.0 allows for the insertion of sensitive information into a 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, such as in popular public CI systems like TravisCI, a malicious actor could use the AWS pre-signed URL to replace a recently uploaded plugin with their own. This could lead to the distribution of malicious code to users who install the compromised plugin.
How To Fix
Minimum fixed version
0.11.0
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. Upgrading to the fixed version is the recommended solution.
Conclusion
The vulnerability in com.gradle.plugin-publish before version 0.11.0 allows for the exposure of sensitive information, potentially leading to the distribution of malicious code. It is recommended to upgrade to the fixed version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for com.gradle.publish:plugin-publish-plugin →
FAQ
The vulnerability allows a malicious actor to replace a recently uploaded Gradle plugin with their own, potentially distributing malicious code to users who install the compromised plugin.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your pom.xml file and Vulert will analyze it in real-time for open-source vulnerabilities.
Yes, all versions of com.gradle.plugin-publish before 0.11.0 are affected by this vulnerability.
Yes, upgrading to version 0.11.0 or later of the com.gradle.plugin-publish plugin fixes this vulnerability.
Yes, ensure that your build logs are not publicly accessible. This will prevent malicious actors from obtaining the AWS pre-signed URL.
