CVE-2020-15769: An issue was discovered in Gradle Enterprise 2020.2 - 2020.2.4

Routine

MEDIUM 6.1UPGRADE

CVE-2020-15769 is a medium-severity flaw (CVSS 6.1) affecting enterprise. 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 2020.2 - 2020.2.4. An XSS issue exists via the request URL.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.7% (top 49%)
CISA exploited list	No
Weakness	CWE-79
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: >= 2020.2 and <= 2020.2.4

Fixed in: newer than 2020.2.4

Safe to downgrade to: a release before 2020.2

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 2020.2 (Debian / Ubuntu)

apt-cache madison enterprise sudo apt install enterprise=<VERSION_BEFORE_2020.2> 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_2020.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.

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-15769?

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

Is CVE-2020-15769 being exploited?

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

CVE-2020-15769 affects enterprise. Severity is medium (CVSS 6.1). An issue was discovered in Gradle Enterprise 2020.2 - 2020.2.4. An XSS issue exists via the request URL.

How urgent is CVE-2020-15769?

Priority 34/100. No elevated risk signals yet.

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