NaginatorApplication · Jenkins
CVE-2022-45382
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 Naginator Plugin 1.18.1 and earlier does not escape display names of source builds in builds that were triggered via Retry action, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to edit build display names.
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 Naginator Plugin versions 1.18.1 and earlier fails to escape display names of source builds in builds triggered via the Retry action, allowing stored XSS injection through maliciously crafted build display names.
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
NaginatorApplication
< 1.18.2CVSS 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 Naginator Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the JENKINS_HOME/plugins directory for the naginator plugin folderAffected if Naginator Plugin is not installed in Jenkins
-
Check installed Naginator Plugin versionGo to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate Naginator Plugin, and note the version number displayedAffected if Version is 1.18.1 or earlier (versions below 1.18.2)
-
Identify builds triggered via Retry actionReview build history in Jenkins jobs that use Naginator; check if any builds were triggered using the Retry/Retry Build action provided by NaginatorAffected if Builds exist that were triggered via the Naginator Retry action
-
Inspect build display names for potential XSS payloadsGo to build history, click on each build, and examine the Display Name field in the build information. Look for unusual characters, HTML tags, or script patterns in display namesAffected if Any build display name contains unescaped HTML, script tags, or JavaScript code patterns
User is affected if Naginator Plugin version 1.18.1 or earlier is installed AND builds have been triggered via the Retry action with maliciously crafted display names.
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 · scoped1.18.2
Update Naginator Plugin to version newer than 1.18.1, or restrict permissions to prevent untrusted users from editing build display names.
Naginator plugin version 1.18.2
- 1. In Jenkins, go to 'Manage Jenkins' > 'Manage Plugins'
- 2. Click on the 'Installed' tab to view installed plugins
- 3. Locate the 'Naginator' plugin in the list
- 4. If an update is available, click 'Update' next to the Naginator plugin
- 5. After the update completes, restart Jenkins (or check 'Restart Jenkins' if prompted)
- 6. Verify the installed version is 1.18.2 or later by returning to the Installed plugins list
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Naginator
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45382 — 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-45382 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