First published: Wed Apr 14 2021(Updated: )
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. Reference: <a href="https://github.com/gradle/gradle/security/advisories/GHSA-fp8h-qmr5-j4c8">https://github.com/gradle/gradle/security/advisories/GHSA-fp8h-qmr5-j4c8</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Gradle | <7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1949636 is considered important due to the potential for local information disclosure.
To fix REDHAT-BUG-1949636, upgrade Gradle to version 7.0 or higher.
REDHAT-BUG-1949636 is classified as a local information disclosure vulnerability.
Gradle versions prior to 7.0 are affected by REDHAT-BUG-1949636.
No, REDHAT-BUG-1949636 requires local access to exploit the vulnerability.