JenkinsApplication
CVE-2020-2220
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 2.244 and earlier, LTS 2.235.1 and earlier does not escape the agent name in the build time trend page, resulting in a stored cross-site scripting vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJenkins versions 2.244 and earlier, LTS 2.235.1 and earlier fail to properly escape agent names when rendered on the build time trend page. This allows attackers with agent configuration permissions to inject malicious JavaScript code into the agent name, which executes when other users view the affected page, resulting in a stored cross-site scripting vulnerability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JenkinsApplication
<= 2.235.1<= 2.244CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Jenkins versionNavigate to Manage Jenkins > About Jenkins or run 'java -jar jenkins.war --version' if running from WAR. Check the version number against the affected ranges: 2.235.1 or earlier (LTS), or 2.244 or earlier.Affected if The installed version is 2.235.1 or earlier (LTS), or 2.244 or earlier.
-
Verify if any agents are configuredNavigate to Manage Jenkins > Manage Nodes. Check if any agents (permanent or cloud) have been added to the Jenkins instance.Affected if Any agents are configured in Jenkins.
-
Review agent configuration permissionsNavigate to Manage Jenkins > Manage Users, then check Configure Global Security or Matrix-based security to see which users or groups have the 'Administer' or 'Configure' permissions for agents.Affected if Any user or group with agent configuration permissions is untrusted or not an administrator.
-
Inspect agent names for suspicious contentNavigate to Manage Jenkins > Manage Nodes and examine each agent's name field. Look for unusual characters such as <, >, ", ', or JavaScript keywords like script, onerror, onload.Affected if Any agent name contains HTML, JavaScript, or special characters that could be used for XSS execution.
The environment is affected if the Jenkins version is 2.235.1 or earlier (LTS) or 2.244 or earlier, agents are configured, untrusted users have agent configuration permissions, AND any agent name contains suspicious characters that could execute as JavaScript.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins to version 2.245 or later (LTS 2.235.2 or later) which properly escapes agent names in the build time trend page. Alternatively, restrict agent configuration permissions to trusted users only until the upgrade can be performed.
Fix this in Jenkins
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2220 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data