JenkinsApplication
CVE-2023-43495
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.423 and earlier, LTS 2.414.1 and earlier does not escape the value of the 'caption' constructor parameter of 'ExpandableDetailsNote', resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control this parameter.
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 · moderate confidenceJenkins core contains a stored cross-site scripting (XSS) vulnerability in the ExpandableDetailsNote component. The 'caption' constructor parameter is not properly escaped before rendering, allowing attackers who can control this parameter to inject malicious JavaScript that executes in the browsers of users viewing the affected 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
JenkinsApplication
< 2.414.2< 2.424CVSS 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 your Jenkins versionNavigate to Manage Jenkins > About Jenkins or access /api/json?tree=version to retrieve the installed version numberAffected if The version is below 2.414.2 (LTS) or below 2.424 (weekly)
-
Identify ExpandableDetailsNote usageSearch configuration files, job XML definitions, and plugin source code for calls to ExpandableDetailsNote constructor with a caption parameterAffected if The caption parameter is populated with user-supplied input from job descriptions, build parameters, or other user-controllable fields
-
Review job and build descriptionsInspect job configuration XML files and build history for any ExpandableDetailsNote entries where the caption field contains special characters (<, >, ', ", javascript:)Affected if User-accessible job or build description fields contain unsanitized content rendered through ExpandableDetailsNote
-
Check for stored XSS payloadsReview your Jenkins logs and audit trails for any existing entries containing script tags or javascript: protocols in fields that might render as ExpandableDetailsNote captionsAffected if Malicious JavaScript payloads are found stored in any caption-related fields
You are affected if your Jenkins version is below 2.414.2 (LTS) or below 2.424 AND any user can control content rendered through the ExpandableDetailsNote component caption parameter.
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 · scoped2.414.22.424
Upgrade Jenkins to a version newer than 2.423 (LTS newer than 2.414.1) which includes proper output encoding for the ExpandableDetailsNote caption parameter. Until then, restrict access to features that allow controlling this parameter.
Jenkins 2.424 (weekly release) or Jenkins LTS 2.414.2
- Backup the current Jenkins installation, including $JENKINS_HOME and configuration
- Stop the Jenkins service
- Download the appropriate Jenkins WAR file for the target version
- Replace the existing jenkins.war file in the Jenkins installation directory with the new version
- Start the Jenkins service
- Verify the upgrade by accessing the Jenkins UI and checking the version at: Manage Jenkins > About Jenkins
- Test critical job configurations and plugins to ensure compatibility
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43495 — 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-43495 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