dbcve.org
Script SecurityApplication · Jenkins

CVE-2024-34144

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to after 1335.vf07d9ce377a_e 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
A sandbox bypass vulnerability involving crafted constructor bodies in Jenkins Script Security Plugin 1335.vf07d9ce377a_e and earlier allows 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.

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 Script Security Plugin versions 1335.vf07d9ce377a_e and earlier contains a sandbox bypass vulnerability where attackers with permission to define and run sandboxed scripts (including Pipelines) can use specially crafted constructor bodies to escape sandbox restrictions and execute arbitrary code on the Jenkins controller JVM.

MitigationUpgrade Jenkins Script Security Plugin to version 1336.v864f5b_04c952 or later. Additionally, review and restrict permissions for who can create/edit sandboxed scripts and Pipelines to limit attack surface.

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
Script SecurityApplication
Affected:<= 1335.vf07d9ce377a_e

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. Identify Script Security Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and locate 'Script Security' plugin, or check the $JENKINS_HOME/plugins/script-security/META-INF/MANIFEST.MF file for the version attribute
    Affected if The installed version is 1335.vf07d9ce377a_e or earlier
  2. Confirm Script Security plugin is active
    Check that the Script Security plugin is listed as 'Enabled' in Manage Jenkins > Manage Plugins > Installed, or verify the plugin is loaded by accessing the Jenkins script console at /script and confirming the sandbox is active
    Affected if The Script Security plugin is installed and active in the Jenkins environment
  3. Identify users with sandbox script permissions
    Review Jenkins authorization settings at Manage Jenkins > Configure Global Security and check which users or groups have the 'Run Scripts' or 'Pipeline: Declarative Agent' permissions, or review Job-specific permissions for Pipeline jobs
    Affected if Any user or group has permission to define or run sandboxed scripts (including Pipelines) on the controller
  4. Check for existing sandboxed scripts or Pipelines
    Search the Jenkins home directory for Pipeline job definitions in $JENKINS_HOME/jobs/*/builds/*/pipeline.script or review job configurations that use the 'Use Groovy Sandbox' option enabled in Pipeline steps
    Affected if Sandboxed scripts or Pipelines exist in the environment that could leverage the vulnerability

The environment is affected if the Script Security Plugin version is 1335.vf07d9ce377a_e or earlier and users with permission to run sandboxed scripts exist in Jenkins.

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 1335.vf07d9ce377a_e
Interim mitigation

Upgrade Jenkins Script Security Plugin to version 1336.v864f5b_04c952 or later. Additionally, review and restrict permissions for who can create/edit sandboxed scripts and Pipelines to limit attack surface.

Recommended fix High confidence

1336.vb_b_3a_5b_24a_43f or later

  1. 1. Go to Manage Jenkins > Manage Plugins
  2. 2. Navigate to the 'Updates' tab
  3. 3. Locate 'Script Security Plugin' in the list of available updates
  4. 4. Select the checkbox next to the plugin
  5. 5. Click 'Download now and install after restart' or 'Update' button
  6. 6. Wait for the plugin to download and install
  7. 7. Restart Jenkins (or restart after the update completes if using 'Download now and install after restart')
  8. 8. Verify the new version is installed by checking Manage Plugins > Installed tab

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

Fix this in Script Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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