Unauthenticated code execution via build-cache poisoning
Published Mar 25, 2022 · Updated Aug 3, 2024
Improper access control in Gradle Enterprise 2020.4 through 2021.4.3 allows remote attackers to execute code through build-cache administration. The default setup created without an initial configuration file grants anonymous users build-cache administration and Export API access, allowing access controls to be changed so malicious software can be stored in the cache. Exploitation requires an installation created without that file and can compromise code executed from the poisoned cache.
Summary
What happened
Improper access control in Gradle Enterprise 2020.4 through 2021.4.3 allows remote attackers to execute code through build-cache administration. The default setup created without an initial configuration file grants anonymous users build-cache administration and Export API access, allowing access controls to be changed so malicious software can be stored in the cache. Exploitation requires an installation created without that file and can compromise code executed from the poisoned cache.
The record
- CVE
- CVE-2022-27919
- Published
- Mar 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 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