CVE-2020-15771: An issue was discovered in Gradle Enterprise 2018.2 and Gradle Enterprise Build Cache Node 4.1

This month

HIGH 7.5REMOTEDOWNGRADEDOWNGRADE

CVE-2020-15771 is a high-severity flaw (CVSS 7.5) affecting enterprise, enterprise cache node. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An 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.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 36%)
CISA exploited list	No
Weakness	CWE-311
Published	2020-09-18
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: gradle

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-09-18 14:15 UTCPublished CVE record published
2026-06-17 02:57 UTCUpdated Record last modified

gradle enterprise DOWNGRADE

Affected: 2018.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2018.2

1. Check installed version

apt-cache policy enterprise || rpm -q enterprise || enterprise --version

2. No fixed release: DOWNGRADE to a release before 2018.2 (Debian / Ubuntu)

apt-cache madison enterprise sudo apt install enterprise=<VERSION_BEFORE_2018.2> sudo apt-mark hold enterprise

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list enterprise sudo dnf downgrade enterprise-<VERSION_BEFORE_2018.2> sudo dnf versionlock add enterprise

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

gradle enterprise cache node DOWNGRADE

Affected: 4.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.1

1. Check installed version

apt-cache policy enterprise-cache-node || rpm -q enterprise-cache-node || enterprise-cache-node --version

2. No fixed release: DOWNGRADE to a release before 4.1 (Debian / Ubuntu)

apt-cache madison enterprise-cache-node sudo apt install enterprise-cache-node=<VERSION_BEFORE_4.1> sudo apt-mark hold enterprise-cache-node

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list enterprise-cache-node sudo dnf downgrade enterprise-cache-node-<VERSION_BEFORE_4.1> sudo dnf versionlock add enterprise-cache-node

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-15771?

enterprise: downgrade or apply the listed mitigation; enterprise cache node: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-15771 being exploited?

CVE-2020-15771 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-15771 affect?

CVE-2020-15771 affects enterprise, enterprise cache node. Severity is high (CVSS 7.5). An 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.

How urgent is CVE-2020-15771?

Priority 47/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2023-49238 CRITICAL 9.8 UPGRADE In Gradle Enterprise before 2023.1, a remote attacker may be able to gain access to a new installation (in cer
CVE-2022-41575 HIGH 7.5 UPGRADE A credential-exposure vulnerability in the support-bundle mechanism in Gradle Enterprise 2022.3 through 2022.3
CVE-2022-41574 HIGH 7.5 UPGRADE An access-control vulnerability in Gradle Enterprise 2022.4 through 2022.3.1 allows remote attackers to preven
CVE-2022-27919 CRITICAL 9.8 UPGRADE Gradle Enterprise before 2022.1 allows remote code execution if the installation process did not specify an in
CVE-2022-27225 MEDIUM 6.5 UPGRADE Gradle Enterprise before 2021.4.3 relies on cleartext data transmission in some situations

References

← Back to latest CVEs