CVE-2020-15768: An issue was discovered in Gradle Enterprise 2017.3 - 2020.2.4 and Gradle Enterprise Build Cache Node 1.0 - 9.

This month

HIGH 7.5REMOTEUPGRADEUPGRADE

CVE-2020-15768 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 2017.3 - 2020.2.4 and Gradle Enterprise Build Cache Node 1.0 - 9.2. Unrestricted HTTP header reflection in Gradle Enterprise allows remote attackers to obtain authentication cookies, if they are able to discover a separate XSS vulnerability. This potentially allows an attacker to impersonate another user. Gradle Enterprise affected application request paths:/info/headers, /cache-info/headers, /admin-in

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 23%)
CISA exploited list	No
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 UPGRADE

Affected: >= 2017.3 and <= 2020.2.4

Fixed in: newer than 2020.2.4

Safe to downgrade to: a release before 2017.3

1. Check installed version

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

2. UPGRADE to newer than 2020.2.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade enterprise

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade enterprise

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2017.3 (Debian / Ubuntu)

apt-cache madison enterprise sudo apt install enterprise=<VERSION_BEFORE_2017.3> sudo apt-mark hold enterprise

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list enterprise sudo dnf downgrade enterprise-<VERSION_BEFORE_2017.3> 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 UPGRADE

Affected: >= 1.0 and <= 9.2

Fixed in: newer than 9.2

Safe to downgrade to: a release before 1.0

1. Check installed version

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

2. UPGRADE to newer than 9.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade enterprise-cache-node

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade enterprise-cache-node

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison enterprise-cache-node sudo apt install enterprise-cache-node=<VERSION_BEFORE_1.0> sudo apt-mark hold enterprise-cache-node

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list enterprise-cache-node sudo dnf downgrade enterprise-cache-node-<VERSION_BEFORE_1.0> 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-15768?

enterprise: upgrade to newer than 2020.2.4; enterprise cache node: upgrade to newer than 9.2. Exact commands for each OS are on this page.

Is CVE-2020-15768 being exploited?

CVE-2020-15768 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-15768 affect?

CVE-2020-15768 affects enterprise, enterprise cache node. Severity is high (CVSS 7.5). An issue was discovered in Gradle Enterprise 2017.3 - 2020.2.4 and Gradle Enterprise Build Cache Node 1.0 - 9.2. Unrestricted HTTP header reflection in Gradle Enterprise allows remote attackers to obtain authentication cookies, if they are

How urgent is CVE-2020-15768?

Priority 50/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