Build Failure AnalyzerApplication · Jenkins
CVE-2023-43499
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 Build Failure Analyzer Plugin 2.4.1 and earlier does not escape Failure Cause names in build logs, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create or update Failure Causes.
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 confidenceJenkins Build Failure Analyzer Plugin 2.4.1 and earlier fails to escape Failure Cause names when displaying them in build logs, resulting in a stored cross-site scripting (XSS) vulnerability. Attackers with permission to create or update Failure Causes can inject malicious JavaScript code that executes when users view affected build logs.
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
Build Failure AnalyzerApplication
< 2.4.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 Build Failure Analyzer plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i "build-failure"Affected if Plugin is not listed in installed plugins, then the vulnerability does not apply
-
Check the installed plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find 'Build Failure Analyzer' and compare the version number to 2.4.2Affected if Installed version is lower than 2.4.2 (e.g., 2.4.1, 2.4.0, etc.)
-
Identify if custom Failure Causes existNavigate to Jenkins > Build Failure Analyzer (or access via job configuration). Review the list of configured Failure Causes. Alternatively, check the Jenkins script console: Jenkins.instance.getPlugin("build-failure-analyzer")?.getFailureCauses()Affected if There are zero custom Failure Causes configured, the exploit surface is minimal but the XSS vulnerability in the rendering code still exists in older versions
-
Check user permissions for Failure Cause managementNavigate to Jenkins > Manage Jenkins > Configure Global Security. Review Matrix Authorization Strategy or Project-based Matrix Authorization permissions. Specifically check 'Build Failure Analyzer' permissions: Create Cause, Update CauseAffected if Users with untrusted or broad access have Create/Update permissions for Failure Causes, they could inject malicious content
-
Confirm if builds display Failure Cause names in logsRun a build on a job configured to use Build Failure Analyzer. Examine the build console output or build failure analysis for any displayed Failure Cause namesAffected if Build logs or build pages display Failure Cause names from the plugin, exposing the XSS vector when names are rendered without escaping
User is affected if Build Failure Analyzer plugin version is below 2.4.2 AND custom Failure Causes exist that could contain malicious script AND users with permission to create/update those causes exist in the environment.
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.4.2
Update Build Failure Analyzer Plugin to version 2.4.2 or later. Until patched, restrict permissions so only trusted users can create or update Failure Causes, and implement Content Security Policy headers in Jenkins.
2.4.2
- Log in to Jenkins as an administrator
- Navigate to 'Manage Jenkins'
- Click on 'Manage Plugins'
- Select the 'Updates' tab
- Locate 'Build Failure Analyzer' in the list of available updates
- Select the checkbox next to the plugin
- Click 'Download now and install after restart' or 'Update'
- Wait for the plugin to download and install
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Build Failure Analyzer
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43499 — 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-43499 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