CVE-2020-2221 Stored XSS vulnerability in Jenkins upstream cause

Medium 5.4 Published Updated

Stored cross-site scripting in Jenkins allows attackers to execute arbitrary scripts via unescaped upstream job display names in build causes.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2020-2221?

CVE-2020-2221 is a medium-severity cross-site scripting vulnerability in Jenkins Jenkins, published on 15 Jul 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

Jenkins 2.244 and earlier, LTS 2.235.1 and earlier does not escape the upstream job's display name shown as part of a build cause, resulting in a stored cross-site scripting vulnerability.

Weakness: CWE-79

Which versions are affected by CVE-2020-2221?

5 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core and jenkins. It affects 1 product.

PackageAffectedFixed in
org.jenkins-ci.main:jenkins-core MavenAll versions2.235.2
org.jenkins-ci.main:jenkins-core MavenAll versions2.235.2
org.jenkins-ci.main:jenkins-core MavenFrom 2.2362.245
org.jenkins-ci.main:jenkins-core MavenFrom 2.2362.245
jenkins BitnamiAll versions2.244.1

Products include Jenkins Jenkins.

How do I fix CVE-2020-2221?

Upgrade org.jenkins-ci.main:jenkins-core to a fixed version for your release line: 2.235.2 or 2.245.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2020-2221 being exploited?

There is no known exploitation of CVE-2020-2221 in the wild and no public exploit code.

All Jenkins Jenkins vulnerabilities

Sources

Also known as BIT-jenkins-2020-2221, GHSA-g4j6-m3m3-crw8.

Is CVE-2020-2221 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free