CVE-2022-41574: High severity Gradle Enterprise vulnerability
An access-control vulnerability in Gradle Enterprise 2022.4 through 2022.3.1 allows remote attackers to prevent backups from occurring, and send emails with arbitrary text content to the configured installation-administrator contact address, via HTTP access to an accidentally exposed internal endpoint. This is fixed in 2022.3.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Gradle Enterpriseto a version that resolves this vulnerability.Fixed in 2022.3.2
Event History
Frequently Asked Questions
What is CVE-2022-41574?
CVE-2022-41574 is an access-control vulnerability in Gradle Enterprise 2022.4 through 2022.3.1.
How does CVE-2022-41574 allow remote attackers to exploit it?
CVE-2022-41574 allows remote attackers to prevent backups from occurring and send emails with arbitrary text content to the installation-administrator contact address by accessing an accidentally exposed internal endpoint via HTTP.
What is the severity level of CVE-2022-41574?
CVE-2022-41574 has a severity level of 7.5 (high).
Which software versions are affected by CVE-2022-41574?
CVE-2022-41574 affects Gradle Enterprise versions 2022.4 through 2022.3.1.
How can I fix CVE-2022-41574?
To fix CVE-2022-41574, upgrade to a version newer than 2022.3.1 of Gradle Enterprise.