dbcve.org
Semantic VersioningApplication · Jenkins

CVE-2023-24430

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 1.15 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Semantic Versioning Plugin 1.14 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

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

The Jenkins Semantic Versioning Plugin versions 1.14 and earlier contains an XML External Entity (XXE) vulnerability due to its XML parser not being configured to disable external entity processing. This allows attackers to craft malicious XML input that can potentially read local files or perform server-side request forgery (SSRF) attacks.

MitigationUpdate the Jenkins Semantic Versioning Plugin to a patched version that properly configures the XML parser to prevent XXE attacks by disabling external entity processing.

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
Semantic VersioningApplication
Affected:< 1.15

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Verify Jenkins is installed
    Access the Jenkins web UI and check the version at /jenkins/ or run 'java -jar jenkins.war --version' if you have CLI access. Alternatively, check for /var/lib/jenkins/ or C:\Program Files\Jenkins directories.
    Affected if Jenkins is running and the Semantic Versioning Plugin is installed
  2. Check if Semantic Versioning Plugin is installed
    In Jenkins web UI, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Semantic Versioning' in the list, or inspect the plugin directory at $JENKINS_HOME/plugins/ for a folder named 'semantic-versioning-plugin' or similar.
    Affected if The Semantic Versioning Plugin is present in the plugins directory
  3. Determine the installed plugin version
    In the Jenkins web UI plugin list (Manage Jenkins > Manage Plugins > Installed), find the Semantic Versioning Plugin and note the Version column. If using CLI, inspect the plugin's manifest file: $JENKINS_HOME/plugins/semantic-versioning-plugin/META-INF/MANIFEST.MF for the Implementation-Version attribute.
    Affected if The installed version is 1.14 or earlier (versions prior to 1.15)
  4. Verify if XML processing is in use
    Review Jenkins job configurations that use the Semantic Versioning Plugin. Check for build steps, publishers, or configuration files (.xml) that invoke the plugin's parsing functionality. Look for job config.xml files in $JENKINS_HOME/jobs/<jobname>/config.xml that reference semantic versioning parsing.
    Affected if Jobs are configured to use the Semantic Versioning Plugin's XML parsing features on untrusted input

You are affected if Jenkins is running with Semantic Versioning Plugin version 1.14 or earlier and jobs are configured to process XML files through the plugin.

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 1.15 or later
Fixed in 1.15
Interim mitigation

Update the Jenkins Semantic Versioning Plugin to a patched version that properly configures the XML parser to prevent XXE attacks by disabling external entity processing.

Recommended fix High confidence

1.15

  1. Navigate to the Jenkins dashboard
  2. Go to 'Manage Jenkins'
  3. Click on 'Manage Plugins'
  4. Select the 'Updates' tab
  5. Locate the 'Semantic Versioning Plugin' in the list
  6. Check for available updates and select the plugin
  7. Click 'Download now and install after restart' or 'Update'
  8. Wait for the plugin to update to version 1.15

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

Fix this in Semantic Versioning Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24430 — 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-24430 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