dbcve.org
Semantic VersioningApplication · Jenkins

CVE-2023-24429

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 restrict execution of an controller/agent message to agents, and implements no limitations about the file path that can be parsed, allowing attackers able to control agent processes to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.

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 Semantic Versioning Plugin versions 1.14 and earlier contains a critical vulnerability where agent messages are not restricted to agents and file path parsing has no limitations. Attackers who compromise agent processes can trigger XML external entity (XXE) injection by having the Jenkins controller parse crafted files, enabling extraction of secrets from the controller filesystem and SSRF attacks.

MitigationUpgrade to the patched version of the Semantic Versioning Plugin when available, and restrict agent-to-controller message handling in the interim. Additionally, disable external entity processing in XML parsers used by the plugin.

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 Semantic Versioning Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed and search for 'Semantic Versioning' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list.
  2. Identify the installed plugin version
    In the plugin details view, note the version number displayed next to the Semantic Versioning Plugin name.
    Affected if The installed version is 1.14 or earlier, or the version field shows a version number less than 1.15.
  3. Check for active agent connections
    Go to Manage Jenkins > Manage Nodes and review the list of connected agents. Note whether any agents are online and communicating with the controller.
    Affected if Any agents are connected to the Jenkins controller, as the vulnerability can be exploited through compromised agent processes.
  4. Identify jobs using the plugin
    Review job configurations that utilize the Semantic Versioning Plugin for versioning or build metadata processing.
    Affected if Any Jenkins jobs are configured to use the Semantic Versioning Plugin functionality.

A user is affected if the Semantic Versioning Plugin version 1.14 or earlier is installed, any agents are connected, and jobs use the plugin's parsing functionality.

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

Upgrade to the patched version of the Semantic Versioning Plugin when available, and restrict agent-to-controller message handling in the interim. Additionally, disable external entity processing in XML parsers used by the plugin.

Recommended fix High confidence

Semantic Versioning Plugin 1.15

  1. Check the currently installed version of the Semantic Versioning Plugin in Jenkins under Manage Jenkins > Manage Plugins > Installed tab
  2. Navigate to the available updates or the Semantic Versioning Plugin page and upgrade to version 1.15 or later
  3. Restart Jenkins to apply the plugin update
  4. Verify the plugin shows version 1.15 or later in the installed plugins list

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

Fix this in Semantic Versioning Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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