Unauthenticated data disclosure via Ajax header bypass
Published Sep 24, 2021 · Updated Aug 4, 2024
Access-control bypass in Gradle Enterprise 2020.4 through 2021.1.1 allows remote attackers to read protected build and configuration data. When the application receives a GET request bearing the X-Gradle-Enterprise-Ajax-Request header, it returns the protected resource body even though it sets HTTP status 401. No authentication or user interaction is required; the bypass is read-only and cannot expose credentials stored for SMTP or LDAP connections.
Summary
What happened
Access-control bypass in Gradle Enterprise 2020.4 through 2021.1.1 allows remote attackers to read protected build and configuration data. When the application receives a GET request bearing the X-Gradle-Enterprise-Ajax-Request header, it returns the protected resource body even though it sets HTTP status 401. No authentication or user interaction is required; the bypass is read-only and cannot expose credentials stored for SMTP or LDAP connections.
The record
- CVE
- CVE-2021-41584
- Published
- Sep 24, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 24, 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.
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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