CVE-2023-24429

Agent-to-controller security bypass in Jenkins Semantic Versioning Plugin

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.

An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.

CVE-2023-24429 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.15); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2023-24429? CVE-2023-24429 is a critical-severity XML external entity injection (XXE) vulnerability in org.jenkins-ci.plugins:semantic-versioning-plugin (maven), affecting versions < 1.15. It is fixed in 1.15. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
2. How severe is CVE-2023-24429? CVE-2023-24429 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.jenkins-ci.plugins:semantic-versioning-plugin are affected by CVE-2023-24429? org.jenkins-ci.plugins:semantic-versioning-plugin (maven) versions < 1.15 is affected.
4. Is there a fix for CVE-2023-24429? Yes. CVE-2023-24429 is fixed in 1.15. Upgrade to this version or later.
5. Is CVE-2023-24429 exploitable, and should I be worried? Whether CVE-2023-24429 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-24429 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-24429? Upgrade org.jenkins-ci.plugins:semantic-versioning-plugin to 1.15 or later.

Other vulnerabilities in org.jenkins-ci.plugins:semantic-versioning-plugin