First published: Wed Oct 27 2021(Updated: )
In Gradle Enterprise before 2021.3 (and Enterprise Build Cache Node before 10.0), there is potential cache poisoning and remote code execution when running the build cache node with its default configuration. This configuration allows anonymous access to the configuration user interface and anonymous write access to the build cache. If access control to the build cache is not changed from the default open configuration, a malicious actor with network access can populate the cache with manipulated entries that may execute malicious code as part of a build process. This applies to the build cache provided with Gradle Enterprise and the separate build cache node service if used. If access control to the user interface is not changed from the default open configuration, a malicious actor can undo build cache access control in order to populate the cache with manipulated entries that may execute malicious code as part of a build process. This does not apply to the build cache provided with Gradle Enterprise, but does apply to the separate build cache node service if used.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Gradle Build Cache Node | <10.0 | |
Gradle Enterprise | <2021.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this issue is CVE-2021-41589.
The severity of CVE-2021-41589 is critical with a score of 9.8.
Gradle Build Cache Node versions up to exclusive 10.0 and Gradle Enterprise versions up to exclusive 2021.3 are affected by CVE-2021-41589.
This vulnerability can be exploited to perform cache poisoning and remote code execution when running the build cache node with its default configuration.
To fix CVE-2021-41589, it is recommended to upgrade to the latest version of Gradle Enterprise (2021.3 or later) or Gradle Build Cache Node (10.0 or later).