CVE-2021-41587
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 · uneditedIn Gradle Enterprise before 2021.1.3, an attacker with the ability to perform SSRF attacks can potentially discover credentials for other resources.
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 confidenceGradle Enterprise before version 2021.1.3 contains a Server-Side Request Forgery (SSRF) vulnerability that allows an attacker to make the application perform requests to internal or external resources, potentially exposing credentials stored for other services or integrations.
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>= 2017.6, < 2021.1.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.
-
Confirm product is Gradle EnterpriseIdentify if the deployed product is Gradle Enterprise (the commercial/enterprise offering) and not the open-source Gradle build tool. Gradle Enterprise is typically accessed via a web admin console at a specific URL.Affected if The product is Gradle Enterprise
-
Locate the installed versionFind the installed version through the admin interface, typically in an 'About' or 'System Information' section, or check installation scripts, configuration files, or deployment metadata where the version was recorded.Affected if Unable to determine the version
-
Compare version against affected rangeCompare the installed version to the affected range: versions 2017.6 through 2021.1.2 are vulnerable. Version 2021.1.3 and later are patched.Affected if Version is greater than or equal to 2017.6 AND less than 2021.1.3
The environment is affected if Gradle Enterprise is running version 2017.6 or higher but lower than 2021.1.3.
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 · scoped2021.1.3
Upgrade Gradle Enterprise to version 2021.1.3 or later. Additionally, implement network segmentation and restrict outbound network access from the application server to minimize the impact of SSRF attacks.
Gradle Enterprise 2021.1.3 or later (recommended: latest stable 2021.x release)
- 1. Identify the current Gradle Enterprise version by checking the administration console or system information
- 2. Review the Gradle Enterprise 2021.1.3 release notes for upgrade considerations
- 3. Perform a full backup of the Gradle Enterprise instance including configuration and database
- 4. Schedule a maintenance window for the upgrade
- 5. Upgrade Gradle Enterprise to version 2021.1.3 or later (the latest stable 2021.x release is recommended)
- 6. After upgrade, verify the SSRF vulnerability is resolved by reviewing security settings
- 7. Confirm all previously accessible features and integrations function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41587 — 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-2021-41587 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