Remote code execution via anonymous cache writes
Published Oct 27, 2021 · Updated Aug 4, 2024
Cache poisoning in Gradle Enterprise before 2021.3 and Build Cache Node before 10.0 allows remote attackers to execute code during builds. The default configuration grants anonymous access to the configuration interface and anonymous write access to the cache, so manipulated entries are consumed as trusted build inputs. Network reachability is sufficient while either the cache remains open or, for the separate node service, its anonymously accessible interface can restore open cache access.
Summary
What happened
Cache poisoning in Gradle Enterprise before 2021.3 and Build Cache Node before 10.0 allows remote attackers to execute code during builds. The default configuration grants anonymous access to the configuration interface and anonymous write access to the cache, so manipulated entries are consumed as trusted build inputs. Network reachability is sufficient while either the cache remains open or, for the separate node service, its anonymously accessible interface can restore open cache access.
The record
- CVE
- CVE-2021-41589
- Published
- Oct 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-732, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo