JunitApplication · Jenkins
CVE-2022-45380
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 JUnit Plugin 1159.v0b_396e1e07dd and earlier converts HTTP(S) URLs in test report output to clickable links in an unsafe manner, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
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 JUnit Plugin versions 1159.v0b_396e1e07dd and earlier insecurely converts HTTP(S) URLs found in test report output into clickable links. This unsafe link generation allows stored XSS because the plugin does not properly sanitize or escape the URL content before rendering it as a clickable element in the web UI. Attackers with Item/Configure permission can inject malicious scripts via specially crafted URLs in test report content.
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
JunitApplication
< 1160.vf1f01a_a_ea_b_7fCVSS 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.
-
Identify JUnit Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, locate 'JUnit' plugin, and note the version number. Alternatively, check the plugin manifest file at $JENKINS_HOME/plugins/junit/WEB-INF/lib/junit-plugin.jar or the plugin's manifest.xml.Affected if The installed version is 1159.v0b_396e1e07dd or earlier (any version before 1160.vf1f01a_a_ea_b_7f)
-
Confirm test report processing is activeCheck if any Jenkins jobs are configured to publish JUnit test results. Look for the 'Publish JUnit test result report' post-build action in job configurations, or check for .xml test result files in build directories.Affected if Test result reports are being published and displayed in Jenkins (the vulnerable feature is in use)
-
Verify URL content rendering in test resultsView a published JUnit test result report in the Jenkins web UI. Inspect whether any URLs from test output appear as clickable links in the test report view.Affected if Clickable links are rendered from test report content (indicates the vulnerability is exploitable in your environment)
-
Assess permission configurationReview which users or groups have Item/Configure permission in Jenkins. Navigate to Manage Jenkins > Manage and Assign Roles > Assign Roles, or check matrix authorization settings.Affected if Untrusted users have Item/Configure permission and can configure jobs that produce test reports
You are affected if the JUnit Plugin version is below 1160.vf1f01a_a_ea_b_7f, test result reports are being published, and untrusted users have Item/Configure permission.
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.
dbcve · scoped1160.vf1f01a_a_ea_b_7f
Upgrade the Jenkins JUnit Plugin to version 1160.v6f_4a_3a_8c_a_c or later, which contains the security fix for proper URL sanitization. Until patched, restrict Item/Configure permission to trusted users only.
1160.vf1f01a_a_ea_b_7f
- Identify the Jenkins instance running the JUnit Plugin
- Navigate to Manage Jenkins > Manage Plugins
- Locate the JUnit Plugin in the Installed tab
- Check the current version - if it is earlier than 1160.vf1f01a_a_ea_b_7f, an update is required
- Update the JUnit Plugin to version 1160.vf1f01a_a_ea_b_7f or later
- Restart Jenkins if required for the plugin update to take effect
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Junit
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45380 — 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-2022-45380 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