Script SecurityApplication · Jenkins
CVE-2020-2190
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 Script Security Plugin 1.72 and earlier does not correctly escape pending or approved classpath entries on the In-process Script Approval 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 confidenceThe Jenkins Script Security Plugin versions 1.72 and earlier fails to properly escape pending or approved classpath entries when rendering the In-process Script Approval page. This allows stored XSS attacks where malicious classpath entries execute in the browsers of users viewing this page.
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
Script SecurityApplication
<= 1.72CVSS 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.
-
Verify Script Security Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or check $JENKINS_HOME/plugins for the script-security folderAffected if The plugin is present in the plugins directory or plugin manager
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, find Script Security Plugin and note the Version column, or inspect the plugin's manifest (MANIFEST.MF or .jpl file)Affected if The version is 1.72 or earlier (e.g., 1.72, 1.71, 1.70, etc.)
-
Verify access to Script Approval pageNavigate to Manage Jenkins > In-process Script Approval (requires Overall/Administer permission or specific Script Approval permissions)Affected if The page is accessible and the user can view pending or approved script approvals
-
Inspect for pending or approved classpath entriesOn the Script Approval page, review the Classpath Entries section for any entries. Entries can be viewed in the configuration file at $JENKINS_HOME/scriptApproval.xmlAffected if Any classpath entries exist (either pending or approved) in the scriptApproval.xml configuration file
The environment is affected if the Script Security Plugin version is 1.72 or earlier AND the Script Approval page contains any pending or approved classpath entries that could be exploited for stored XSS.
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 dataUpdate Jenkins Script Security Plugin to version 1.73 or later, which includes proper HTML escaping of classpath entries on the Script Approval page.
Fix this in Script Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2190 — 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-2190 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