# CVE-2023-24422: Sandbox bypass in Jenkins Script Security Plugin

> Attackers with script definition permissions can bypass sandbox restrictions to execute arbitrary code on the Jenkins controller.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-76qj-9gwh-pvv3

## What is CVE-2023-24422?

CVE-2023-24422 is a high-severity code injection vulnerability in Jenkins Script Security Plugin, published on 24 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2023-24422?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:script-security. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:script-security` | Maven | All versions | 1229.v4880b |
| `org.jenkins-ci.plugins:script-security` | Maven | All versions | 1229.v4880b |

Products: Jenkins Script Security.

## How do I fix CVE-2023-24422?

Upgrade org.jenkins-ci.plugins:script-security to 1229.v4880b or later.

## Is CVE-2023-24422 being exploited?

There is no known exploitation of CVE-2023-24422 in the wild and no public exploit code.

Public exploit code:

- https://github.com/shoucheng3/jenkinsci__script-security-plugin_CVE-2023-24422_1228.vd93135a_2fb_25 (github_poc): https://github.com/shoucheng3/jenkinsci__script-security-plugin_CVE-2023-24422_1228.vd93135a_2fb_25

## Other vulnerabilities in Jenkins Script Security Plugin

- [CVE-2019-1003029](https://insights.sbomify.com/CVE-2019-1003029/): Jenkins Script Security Plugin Sandbox Bypass (critical 9.9, exploited in the wild)
- [CVE-2022-43401](https://insights.sbomify.com/CVE-2022-43401/): Sandbox bypass vulnerabilities in Jenkins Script Security Plugin and in Pipeline: Groovy Plugin (critical 9.9)
- [CVE-2022-43403](https://insights.sbomify.com/CVE-2022-43403/): Jenkins Script Security Plugin sandbox bypass vulnerability (critical 9.9)
- [CVE-2022-43404](https://insights.sbomify.com/CVE-2022-43404/): Sandbox bypass vulnerabilities in Jenkins Script Security Plugin and in Pipeline: Groovy Plugin (critical 9.9)
- [CVE-2020-2279](https://insights.sbomify.com/CVE-2020-2279/): Sandbox bypass vulnerability in Jenkins Script Security Plugin (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24422 and fix it if it is affected.

What it is: CVE-2023-24422 is a high-severity code injection vulnerability in Jenkins Script Security Plugin, published on 24 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-24422 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:script-security (Maven): affected all versions; fixed in 1229.v4880b
- org.jenkins-ci.plugins:script-security (Maven): affected all versions; fixed in 1229.v4880b

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-24422/ (Markdown: https://insights.sbomify.com/CVE-2023-24422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-24422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-24422
- OSV: https://osv.dev/vulnerability/CVE-2023-24422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-24422/
Summaries are generated and may contain mistakes; the official description above is the record.