Pipeline\Application · Jenkins
CVE-2023-32977
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 Pipeline: Job Plugin does not escape the display name of the build that caused an earlier build to be aborted, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to set build display names immediately.
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 Pipeline: Job Plugin fails to properly escape the display name of a build that caused an earlier build to be aborted. When an attacker with the ability to set build display names configures a malicious display name containing script tags, this value is stored and later rendered without sanitization in the UI, allowing execution of arbitrary JavaScript in the context of other users viewing the build information.
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
Pipeline\Application
<= 1292.v27d8cc3e2602CVSS 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 the Pipeline: Job plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and locate 'Pipeline: Job' (or 'pipeline-jas雏' plugin file) to view the installed version numberAffected if The installed version is 1292.v27d8cc3e2602 or earlier
-
Identify builds with custom display namesReview build history for any builds where the display name differs from the default build number (e.g., custom names like '#1', '#2 - my build')Affected if Any builds exist with custom display names set by users with permission to do so
-
Check for builds aborted by later buildsIn Jenkins UI, examine build histories for instances where one build was aborted because a subsequent build started (this triggers the vulnerable code path that renders the aborted build's display name)Affected if There are builds that were aborted by newer builds and those aborted builds had custom display names containing HTML/script content
-
Review user permissions for build display name settingCheck Jenkins authorization matrix or project-based security settings to identify which users or groups have the 'Update build name' permission or ability to configure build display namesAffected if Users other than administrators have permission to set or modify build display names
You are affected if the Pipeline: Job plugin is version 1292.v27d8cc3e2602 or earlier AND users with permission to set build display names exist AND builds with custom display names were aborted by subsequent builds, causing the unsanitized display name to be rendered in the UI.
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 the Jenkins Pipeline: Job Plugin to the latest patched version that properly escapes build display names. Restrict or audit permissions for users able to set build display names until the update is applied.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32977 — 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-2023-32977 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