CVE-2020-15771
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 · uneditedAn issue was discovered in Gradle Enterprise 2018.2 and Gradle Enterprise Build Cache Node 4.1. Cross-site transmission of cookie containing CSRF token allows remote attacker to bypass CSRF mitigation.
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 confidenceThe CSRF token is stored in a cookie without the SameSite attribute, allowing cross-site transmission. This enables an attacker on a malicious site to make authenticated requests to the vulnerable Gradle Enterprise application, bypassing the CSRF protection mechanism.
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= 2018.2= 4.1CVSS 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 versionLog into the Gradle Enterprise admin interface and navigate to the 'About' or 'System Information' page to view the installed version numberAffected if The version is 2018.2 or earlier (any version prior to the fix)
-
Identify Gradle Enterprise Cache Node versionAccess the Cache Node admin interface (typically at https://<cache-node-host>:8091) and check the version in the system information or about pageAffected if The version is 4.1 or earlier (any version prior to the fix)
-
Inspect CSRF cookie in browserOpen browser developer tools (F12), go to Application tab, expand Cookies section, and locate the cookie named 'GRADLE_ANALYTICS_SESSION' or similar CSRF-related cookieAffected if The cookie exists but the SameSite attribute is missing, set to 'None', or not present in the Set-Cookie header
-
Capture HTTP response headersUse browser network tab or a tool like curl to make a request to the Gradle Enterprise login endpoint and inspect the Set-Cookie response headers for the CSRF token cookieAffected if The Set-Cookie header for the CSRF cookie does not include 'SameSite=Strict' or 'SameSite=Lax'
-
Verify cookie attributes via command lineRun curl -v https://<gradle-enterprise-host>/<endpoint> 2>&1 | grep -i set-cookie to capture cookie headers and check for SameSite attributeAffected if The SameSite attribute is absent or set to 'None' in the Set-Cookie header
You are affected if you run Gradle Enterprise 2018.2 or earlier or Gradle Enterprise Cache Node 4.1 or earlier, and the CSRF token cookie lacks a SameSite attribute or has it set to 'None'.
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.
From vendor dataConfigure the CSRF token cookie with SameSite=Strict or SameSite=Lax, add the Secure flag, and implement SameSite cookie attributes throughout the application.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15771 — 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-2020-15771 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