Skip to content

Exposure of Sensitive Information in Gradle publish plugin

Moderate severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

maven com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin (Maven)

Affected versions

< 0.11.0

Patched versions

0.11.0
maven com.gradle.publish:plugin-publish-plugin (Maven)
< 0.11.0
0.11.0

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.

References

Published by the National Vulnerability Database Mar 30, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Jul 27, 2022
Last updated Jan 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.074%
(33rd percentile)

Weaknesses

CVE ID

CVE-2020-7599

GHSA ID

GHSA-cv78-v957-jx34

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.