dbcve.org
JenkinsApplication

CVE-2023-39151

MEDIUM · 5.4 CVSS v3.1 Published 2023-07-26
Fix available
A fix is available. Upgrade to after 2.415 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Jenkins 2.415 and earlier, LTS 2.401.2 and earlier does not sanitize or properly encode URLs in build logs when transforming them into hyperlinks, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control build log contents.

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 confidence

Jenkins versions 2.415 and earlier, LTS 2.401.2 and earlier fail to sanitize or properly encode URLs in build logs before transforming them into clickable hyperlinks, resulting in a stored cross-site scripting (XSS) vulnerability. Attackers who can control build log contents can inject malicious scripts that execute in the browsers of users viewing build logs.

MitigationUpgrade to Jenkins 2.415+, LTS 2.401.3+, or later versions which properly encode URLs in build logs before rendering them as hyperlinks.

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
Affected:<= 2.415<= 2.401.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins, or run `java -jar jenkins.war --version` from the server console, or check the version displayed on the login page
    Affected if The version is 2.415 or earlier, or LTS 2.401.2 or earlier
  2. Determine if Jenkins is running the LTS release
    Check if the version string contains an LTS indicator (such as 'LTS' or a date-based version like 2.401.x) in the About Jenkins page or startup logs
    Affected if Running LTS version 2.401.2 or earlier
  3. Confirm build log viewing is enabled
    Verify that the build log viewer is accessible by navigating to any completed build and clicking the 'Console Output' or 'Build Logs' link. This feature is enabled by default in standard installations
    Affected if Build logs can be viewed by users (this is the default state in Jenkins)
  4. Check for custom log formatters or plugins affecting URL handling
    Review installed plugins under Manage Jenkins > Plugins, particularly any related to log formatting, output parsing, or hyperlink handling. Check jenkins.model.Jenkins location for custom log handlers
    Affected if Custom plugins or configurations that process URLs in build logs are present

You are affected if your Jenkins version is 2.415 or earlier (or LTS 2.401.2 or earlier) and users can view build logs, as the URL encoding vulnerability exists in the hyperlink transformation of build log output.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.415
Interim mitigation

Upgrade to Jenkins 2.415+, LTS 2.401.3+, or later versions which properly encode URLs in build logs before rendering them as hyperlinks.

Recommended fix High confidence

Jenkins LTS 2.401.3 or Jenkins 2.416+

  1. Back up your Jenkins instance, including JENKINS_HOME directory, configuration, jobs, and plugins
  2. Review the Jenkins LTS upgrade guide for 2.401.3 at https://www.jenkins.io/doc/upgrade-guide/
  3. Schedule a maintenance window for the upgrade
  4. Upgrade Jenkins to version 2.401.3 LTS (or 2.416+ for weekly releases) using your package manager or direct WAR file replacement
  5. After upgrade, verify that build logs render URLs correctly without the XSS vulnerability
  6. Test critical pipelines and jobs to ensure functionality is not affected
Caveat Review the LTS upgrade guide for any plugin compatibility notes; major plugin updates may be required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39151 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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