Script SecurityApplication · Jenkins

CVE-2024-34145

HIGH · 8.8 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to after 1335.vf07d9ce377a_e or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 sandbox-defined classes that shadow specific non-sandbox-defined classes 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

This is a sandbox bypass vulnerability in Jenkins Script Security Plugin where sandbox-defined classes can shadow specific non-sandbox-defined classes. Attackers with permission to define and run sandboxed scripts (including Pipelines) can bypass sandbox protections and execute arbitrary code on the Jenkins controller JVM.

MitigationUpdate Jenkins Script Security Plugin to version 1336.vc_b_5f1a_3a_24 or later. Additionally, review and restrict permissions for who can define and run sandboxed scripts to minimize 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Script Security Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and locate the Script Security Plugin in the list. Note the version number displayed in the Version column.
    Affected if The installed version is 1335.vf07d9ce377a_e or lower.
  2. Confirm Script Security sandbox is in use
    Review Jenkins jobs and Pipelines to identify any that use the sandboxed script execution feature, typically indicated by use of the Groovy sandbox in Pipeline scripts.
    Affected if Sandboxed script execution is enabled and in use within the Jenkins environment.
  3. Identify users with script execution permissions
    Navigate to Manage Jenkins > Manage Users and review permissions, or check if any users or groups have the Overall/Run Scripts or Script/Execute permission grants.
    Affected if Any user or group has permission to define and run sandboxed scripts.

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

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

Update Jenkins Script Security Plugin to version 1336.vc_b_5f1a_3a_24 or later. Additionally, review and restrict permissions for who can define and run sandboxed scripts to minimize attack surface.

Recommended fix High confidence

Script Security Plugin version 1336.vf20b_333f0a_2 or later

  1. Identify the current version of the Script Security plugin in Jenkins Manage Plugins
  2. If running version 1335.vf07d9ce377a_e or earlier, navigate to Manage Jenkins > Manage Plugins
  3. Locate Script Security plugin and select 'Update'
  4. Restart Jenkins controller to apply the update
  5. Verify the updated version is 1336.vf20b_333f0a_2 or later

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

Fix this in Script Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,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 $4,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-34145 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