CVE-2020-15776: CSRF
First published: Fri Sep 18 2020(Updated: )
An issue was discovered in Gradle Enterprise 2018.2 - 2020.2.4. The CSRF prevention token is stored in a request cookie that is not annotated as HttpOnly. An attacker with the ability to execute arbitrary code in a user's browser could impose an arbitrary value for this token, allowing them to perform cross-site request forgery.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Gradle Enterprise | >=2018.2<=2020.2.4 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-15776?
The severity of CVE-2020-15776 is high (8.8).
What is the impact of CVE-2020-15776?
CVE-2020-15776 allows an attacker to impose an arbitrary value for the CSRF prevention token, potentially leading to unauthorized actions.
Which version of Gradle Enterprise is affected by CVE-2020-15776?
Gradle Enterprise versions 2018.2 through 2020.2.4 are affected by CVE-2020-15776.
What is the Common Weakness Enumeration (CWE) ID for CVE-2020-15776?
The CWE ID for CVE-2020-15776 is CWE-352 and CWE-732.
How can I fix CVE-2020-15776?
To fix CVE-2020-15776, update Gradle Enterprise to a version higher than 2020.2.4.
- collector/nvd-index
- agent/severity
- agent/weakness
- agent/references
- agent/author
- agent/type
- agent/event
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/last-modified-date
- agent/tags
- collector/mitre-cve
- source/MITRE
- vendor/gradle
- canonical/gradle enterprise
- version/gradle enterprise/2018.2
- version/gradle enterprise/2020.2.4