CVE-2022-41575
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA credential-exposure vulnerability in the support-bundle mechanism of Gradle Enterprise versions 2022.3 through 2022.3.3 allows remote unauthenticated attackers to access a subset of application data, including cleartext credentials, due to improper access controls on the support-bundle endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2022.3, < 2022.3.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Gradle Enterprise installationLocate the Gradle Enterprise installation directory or running service. Check for the presence of Gradle Enterprise software and its associated configuration files.Affected if Gradle Enterprise is not installed, this CVE does not apply.
-
Determine installed Gradle Enterprise versionAccess the Gradle Enterprise admin interface or check version files in the installation directory to identify the exact version number.Affected if The version falls within the range 2022.3 through 2022.3.3, the environment is potentially affected.
-
Verify support-bundle functionality is accessibleCheck if the /support-bundle endpoint or related support-bundle functionality is enabled and reachable on the Gradle Enterprise server.Affected if The support-bundle endpoint is accessible without authentication, the vulnerability can be exploited.
-
Assess network exposure of support-bundle endpointDetermine if the support-bundle endpoint is exposed to untrusted networks or the public internet by reviewing network configuration, firewall rules, and reverse proxy settings.Affected if The endpoint is reachable from untrusted networks, remote unauthenticated attackers could exploit this flaw.
The environment is affected if Gradle Enterprise version 2022.3 through 2022.3.3 is installed with the support-bundle endpoint accessible to unauthenticated remote attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2022.3.3
Upgrade to Gradle Enterprise 2022.3.3 or later which contains the fix. If immediate patching is not feasible, implement network-level restrictions to limit external access to the support-bundle functionality.
2022.3.3
- Upgrade Gradle Enterprise from any version >= 2022.3 and < 2022.3.3 to version 2022.3.3 to remediate the credential-exposure vulnerability in the support-bundle mechanism
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41575 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data