CVE-2024-34144

Jenkins Script Security Plugin provides a sandbox feature that allows low privileged users to define scripts, including Pipelines, that are generally safe to execute. Calls to code defined inside a sandboxed script are intercepted, and various allowlists are checked to determine whether the call is to be allowed.

Multiple sandbox bypass vulnerabilities exist in Script Security Plugin 1335.vf07d9ce377a_e and earlier:

• Crafted constructor bodies that invoke other constructors can be used to construct any subclassable type via implicit casts.

• Sandbox-defined Groovy classes that shadow specific non-sandbox-defined classes can be used to construct any subclassable type.

These vulnerabilities allow attackers with permission to define and run sandboxed scripts, including Pipelines, to bypass the sandbox protection and execute arbitrary code in the context of the Jenkins controller JVM.

• These issues are caused by an incomplete fix of SECURITY-2824.

Script Security Plugin 1336.vf33a_a_9863911 has additional restrictions and sanity checks to ensure that super constructors cannot be constructed without being intercepted by the sandbox:

• Calls to to other constructors using this are now intercepted by the sandbox.

• Classes in packages that can be shadowed by Groovy-defined classes are no longer ignored by the sandbox when intercepting super constructor calls.

CVE-2024-34144 has a CVSS score of 8.8 (High). The vector is network-reachable, low 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 (1336.vf33a); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-34144? CVE-2024-34144 is a high-severity security vulnerability in org.jenkins-ci.plugins:script-security (maven), affecting versions < 1336.vf33a. It is fixed in 1336.vf33a.
2. How severe is CVE-2024-34144? CVE-2024-34144 has a CVSS score of 8.8 (High). 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:script-security are affected by CVE-2024-34144? org.jenkins-ci.plugins:script-security (maven) versions < 1336.vf33a is affected.
4. Is there a fix for CVE-2024-34144? Yes. CVE-2024-34144 is fixed in 1336.vf33a. Upgrade to this version or later.
5. Is CVE-2024-34144 exploitable, and should I be worried? Whether CVE-2024-34144 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-2024-34144 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-2024-34144? Upgrade org.jenkins-ci.plugins:script-security to 1336.vf33a or later.