CVE-2021-29429
lowpriority · track · 22EPSS 0.005 · 42 %ileEUUSEPSS · scored 2026-10-27
In Gradle before version 7.0, files created with open permissions in the system temporary directory can allow an attacker to access information downloaded by Gradle. Some builds could be vulnerable to a local information disclosure. Remote files accessed through TextResourceFactory are downloaded into the system temporary directory first. Sensitive information contained in these files can be exposed to other local users on the same system. If you do not use the `TextResourceFactory` API, you are not vulnerable. As of Gradle 7.0, uses of the system temporary directory have been moved to the Gradle User Home directory. By default, this directory is restricted to the user running the build. As a workaround, set a more restrictive umask that removes read access to other users. When files are created in the system temporary directory, they will not be accessible to other users. If you are unable to change your system's umask, you can move the Java temporary directory by setting the System Property `java.io.tmpdir`. The new path needs to limit permissions to the build user only.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 1.9–5.5
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- BIT-gradle-2021-29429Information disclosure through temporary directory permissions2024-03-06vendor · osvUS
In Gradle before version 7.0, files created with open permissions in the system temporary directory can allow an attacker to access information downloaded by Gradle. Some builds could be vulnerable to a local information disclosure. Remote files accessed through TextResourceFactory are downloaded into the system temporary directory first. Sensitive information contained in these files can be exposed to other local users on the same system. If you do not use the `TextResourceFactory` API, you are not vulnerable. As of Gradle 7.0, uses of the system temporary directory have been moved to the Gradle User Home directory. By default, this directory is restricted to the user running the build. As a workaround, set a more restrictive umask that removes read access to other users. When files are created in the system temporary directory, they will not be accessible to other users. If you are unable to change your system's umask, you can move the Java temporary directory by setting the System Property `java.io.tmpdir`. The new path needs to limit permissions to the build user only.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (12)
External citations — patches, advisories, analysis.
- https://docs.gradle.org/7.0/release-notes.html#security-advisoriescnnvd
- https://github.com/gradle/gradle/security/advisories/GHSA-89qm-pxvm-p336Patchcnnvd
- https://github.com/gradle/gradle/security/advisories/GHSA-fp8h-qmr5-j4c8cnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2021-29429cnnvd
- https://packetstormsecurity.com/files/167222/Red-Hat-Security-Advisory-2022-4623-01.htmlcnnvd
- https://vigilance.fr/vulnerability/Gradle-file-reading-via-System-Temporary-Directory-43976cnnvd
- https://www.auscert.org.au/bulletins/ESB-2021.3984cnnvd
- https://www.auscert.org.au/bulletins/ESB-2022.2471cnnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan