Vulnerabilities · 2020 · Gradle
CVE-2020-7599
Gradle Plugin Publishing vulnerability
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.
Affected products
Plugin Publishing. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Gradle Plugin Publishing runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- blog.gradle.org/plugin-portal-update · Vendor Advisory
- snyk.io/vuln/SNYK-JAVA-COMGRADLEPLUGINPUBLISH-559866 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-7599
- cve.org/CVERecord?id=CVE-2020-7599
More vulnerabilities in Gradle products
CVE-2023-49238CVE-2023-44387CVE-2023-42445CVE-2023-35947CVE-2023-35946CVE-2023-30853CVE-2023-26053CVE-2022-41575All 47
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.