CVE-2022-41575
First published: Fri Oct 21 2022(Updated: )
A credential-exposure vulnerability in the support-bundle mechanism in Gradle Enterprise 2022.3 through 2022.3.3 allows remote attackers to access a subset of application data (e.g., cleartext credentials). This is fixed in 2022.3.3.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Gradle Enterprise | >=2022.3<2022.3.3 |
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 the vulnerability ID?
The vulnerability ID is CVE-2022-41575.
What is the severity of CVE-2022-41575?
The severity of CVE-2022-41575 is high with a CVSS score of 7.5.
Which software versions are affected by CVE-2022-41575?
Versions of Gradle Enterprise 2022.3 through 2022.3.3 are affected by CVE-2022-41575.
How can remote attackers exploit CVE-2022-41575?
Remote attackers can exploit CVE-2022-41575 by accessing a subset of application data, such as cleartext credentials, through the support-bundle mechanism in Gradle Enterprise.
How do I fix CVE-2022-41575?
To fix CVE-2022-41575, upgrade to version 2022.3.3 of Gradle Enterprise.
- collector/nvd-index
- agent/weakness
- agent/references
- agent/severity
- agent/author
- agent/tags
- agent/type
- 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/2022.3