Vulnerabilities > CVE-2023-30853 - Cleartext Storage of Sensitive Information vulnerability in Gradle Build Action

CVSS 6.5 - MEDIUM

Attack vector

NETWORK

Attack complexity

LOW

Privileges required

LOW

Confidentiality impact

HIGH

Integrity impact

NONE

Availability impact

NONE

network

low complexity

gradle

CWE-312

NVD

Published: 2023-04-28

Updated: 2024-11-21

Summary

Gradle Build Action allows users to execute a Gradle Build in their GitHub Actions workflow. A vulnerability impacts GitHub workflows using the Gradle Build Action prior to version 2.4.2 that have executed the Gradle Build Tool with the configuration cache enabled, potentially exposing secrets configured for the repository. Secrets configured for GitHub Actions are normally passed to the Gradle Build Tool via environment variables. Due to the way that the Gradle Build Tool records these environment variables, they may be persisted into an entry in the GitHub Actions cache. This data stored in the GitHub Actions cache can be read by a GitHub Actions workflow running in an untrusted context, such as that running for a Pull Request submitted by a developer via a repository fork. This vulnerability was discovered internally through code review, and we have not seen any evidence of it being exploited in the wild. However, in addition to upgrading the Gradle Build Action, affected users should delete any potentially vulnerable cache entries and may choose to rotate any potentially affected secrets. Gradle Build Action v2.4.2 and newer no longer saves this sensitive data for later use, preventing ongoing leakage of secrets via the GitHub Actions Cache. While upgrading to the latest version of the Gradle Build Action will prevent leakage of secrets going forward, additional actions may be required due to current or previous GitHub Actions Cache entries containing this information. Current cache entries will remain vulnerable until they are forcibly deleted or they expire naturally after 7 days of not being used. Potentially vulnerable entries can be easily identified in the GitHub UI by searching for a cache entry with key matching `configuration-cache-*`. The maintainers recommend that users of the Gradle Build Action inspect their list of cache entries and manually delete any that match this pattern. While maintainers have not seen any evidence of this vulnerability being exploited, they recommend cycling any repository secrets if you cannot be certain that these have not been compromised. Compromise could occur if a user runs a GitHub Actions workflow for a pull request attempting to exploit this data. Warning signs to look for in a pull request include: - Making changes to GitHub Actions workflow files in a way that may attempt to read/extract data from the Gradle User Home or `<project-root>/.gradle` directories. - Making changes to Gradle build files or other executable files that may be invoked by a GitHub Actions workflow, in a way that may attempt to read/extract information from these locations. Some workarounds to limit the impact of this vulnerability are available: - If the Gradle project does not opt-in to using the configuration cache, then it is not vulnerable. - If the Gradle project does opt-in to using the configuration-cache by default, then the `--no-configuration-cache` command-line argument can be used to disable this feature in a GitHub Actions workflow. In any case, we recommend that users carefully inspect any pull request before approving the execution of GitHub Actions workflows. It may be prudent to require approval for all PRs from external contributors.

Vulnerable Configurations

Part	Description	Count
Application	Gradle Gradle Build Action - Gradle Build Action 1.0.0 Gradle Build Action 1.0.1 Gradle Build Action 1.0.2 Gradle Build Action 1.1.0 Gradle Build Action 1.2.0 Gradle Build Action 1.2.1 Gradle Build Action 1.3.0 Gradle Build Action 1.3.1 Gradle Build Action 1.3.2 Gradle Build Action 1.3.3 Gradle Build Action 1.4.0 Gradle Build Action 1.4.1 Gradle Build Action 1.5.0 Gradle Build Action 1.5.1 Gradle Build Action 2.0.0 Gradle Build Action 2.0.1 Gradle Build Action 2.1.0 Gradle Build Action 2.1.1 Gradle Build Action 2.1.2 Gradle Build Action 2.1.3 Gradle Build Action 2.1.4 Gradle Build Action 2.1.5 Gradle Build Action 2.1.6 Gradle Build Action 2.1.7 Gradle Build Action 2.2.0 Gradle Build Action 2.2.1 Gradle Build Action 2.2.2 Gradle Build Action 2.2.3 Gradle Build Action 2.2.4 Gradle Build Action 2.2.5 Gradle Build Action 2.3.0 Gradle Build Action 2.3.1 Gradle Build Action 2.3.2 Gradle Build Action 2.3.3 Gradle Build Action 2.4.0 Gradle Build Action 2.4.1	51

Common Weakness Enumeration (CWE)

CWE-312 - Cleartext Storage of Sensitive Information

Common Attack Pattern Enumeration and Classification (CAPEC)

Footprinting
An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
Lifting Data Embedded in Client Distributions
An attacker can resort to stealing data embedded in client distributions or client code in order to gain certain information. This information can reveal confidential contents, such as account numbers, or can be used as an intermediate step in a larger attack (such as by stealing keys/credentials).

Summary

Vulnerable Configurations

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

References