dbcve.org
Script SecurityApplication · Jenkins

CVE-2023-24422

HIGH · 8.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 1229.v4880b_b_e905a_6 or later.
See remediation →
90/100
Remediation priority · Urgent
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 map constructors in Jenkins Script Security Plugin 1228.vd93135a_2fb_25 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 1228.vd93135a_2fb_25 and earlier contain a sandbox bypass vulnerability where map constructors can be exploited by users with permission to define and run sandboxed scripts (including Pipelines) to escape sandbox restrictions and execute arbitrary code on the Jenkins controller JVM.

MitigationUpdate Jenkins Script Security Plugin to the latest version. In the interim, restrict or revoke permissions for users who can define and run sandboxed scripts, and review existing Pipeline jobs for suspicious activity.

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:< 1229.v4880b_b_e905a_6

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 the installed version of Script Security Plugin
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the CLI: java -jar jenkins-cli.jar plugin-management -list or check the file $JENKINS_HOME/plugins/script-security/META-INF/MANIFEST.MF
    Affected if The installed version is 1228.vd93135a_2fb_25 or earlier, or any version below 1229.v4880b_b_e905a_6
  2. Confirm Script Security sandbox is in use
    Review Pipeline jobs or global scripts to determine if they use the @gremlin annotation or are configured to run in sandbox mode. Check Job > Configure > Pipeline Script > Use Groovy Sandbox, or inspect individual scripts for 'Groovy Sandbox' checkbox
    Affected if Sandboxed script execution is enabled and users have access to define or modify sandboxed scripts
  3. Identify users with script execution permissions
    Navigate to Jenkins > Manage Jenkins > Manage and Assign Roles, or check Under: Manage Jenkins > Configure Global Security > Authorization, identify users with Overall/Run Scripts, Job/Configure, or Job/Build permissions that can author or execute Pipelines
    Affected if There are users other than administrators who can define or run sandboxed scripts (Pipelines)

You are affected if the Script Security Plugin version is below 1229.v4880b_b_e905a_6 and untrusted users have permissions to define or execute sandboxed scripts.

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 1229.v4880b_b_e905a_6 or later
Fixed in 1229.v4880b_b_e905a_6
Interim mitigation

Update Jenkins Script Security Plugin to the latest version. In the interim, restrict or revoke permissions for users who can define and run sandboxed scripts, and review existing Pipeline jobs for suspicious activity.

Recommended fix High confidence

Script Security Plugin version 1229.v4880b_b_e905a_6 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Search for 'Script Security Plugin'
  4. 4. If an update is available, select the plugin and click 'Update'
  5. 5. Alternatively, download the fixed version (1229.v4880b_b_e905a_6 or later) from the Jenkins plugin repository
  6. 6. Restart Jenkins or wait for the plugin to load

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-2023-24422 — 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-24422 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