CVE-2022-41574
First published: Fri Oct 07 2022(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Gradle Enterprise | >=2020.4<2022.3.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
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.
- collector/nvd-index
- agent/weakness
- agent/references
- agent/severity
- agent/author
- agent/type
- agent/tags
- agent/event
- agent/description
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- vendor/gradle
- canonical/gradle enterprise
- version/gradle enterprise/2020.4