# CVE-2017-1000096: Arbitrary code execution due to incomplete sandbox protection in Jenkins Pipeline

> Attackers with pipeline configuration permissions can execute arbitrary code due to incomplete sandbox protection in Jenkins Pipeline scripts.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mhwq-4mh7-fv7c

## What is CVE-2017-1000096?

CVE-2017-1000096 is a high-severity code injection vulnerability in n/a, published on 4 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Arbitrary code execution due to incomplete sandbox protection: Constructors, instance variable initializers, and instance initializers in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploited e.g. by regular Jenkins users with the permission to configure Pipelines in Jenkins, or by trusted committers to repositories containing Jenkinsfiles.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-1000096?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | All versions | 2.36.1 |
| `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | All versions | 2.36.1 |

Products: Jenkins Pipeline\.

## How do I fix CVE-2017-1000096?

Upgrade org.jenkins-ci.plugins.workflow:workflow-cps to 2.36.1 or later.

## Is CVE-2017-1000096 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-1003030](https://insights.sbomify.com/CVE-2019-1003030/): Jenkins Matrix Project Plugin Remote Code Execution (critical 9.9, exploited in the wild)
- [CVE-2022-43402](https://insights.sbomify.com/CVE-2022-43402/): Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution (critical 9.9)
- [CVE-2019-1003041](https://insights.sbomify.com/CVE-2019-1003041/): Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin (critical 9.8)
- [CVE-2022-43407](https://insights.sbomify.com/CVE-2022-43407/): CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin (high 8.8)
- [CVE-2022-25173](https://insights.sbomify.com/CVE-2022-25173/): Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000096 and fix it if it is affected.

What it is: CVE-2017-1000096 is a high-severity code injection vulnerability in n/a, published on 4 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1000096 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected all versions; fixed in 2.36.1
- org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected all versions; fixed in 2.36.1

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-2017-1000096/ (Markdown: https://insights.sbomify.com/CVE-2017-1000096/index.md)
```

## Sources

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

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