Remote code execution via anonymous cache writes
Published Mar 17, 2022 · Updated Aug 3, 2024
Incorrect authorization in Gradle Enterprise before 2021.4.2 allows remote attackers to execute code through the built-in build cache. The default access-control configuration grants anonymous write access, enabling manipulated cache entries to replace build outputs with malicious content. Exploitation requires network access, an unchanged default configuration, and a later build that consumes the poisoned entry; remote cache nodes are unaffected.
Summary
What happened
Incorrect authorization in Gradle Enterprise before 2021.4.2 allows remote attackers to execute code through the built-in build cache. The default access-control configuration grants anonymous write access, enabling manipulated cache entries to replace build outputs with malicious content. Exploitation requires network access, an unchanged default configuration, and a later build that consumes the poisoned entry; remote cache nodes are unaffected.
The record
- CVE
- CVE-2022-25364
- Published
- Mar 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, T1195.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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