# CVE-2017-2650: Jenkins Pipeline Classpath Step plugin allowed Script Security sandbox bypass

> Attackers with SCM or configure permissions can bypass the Script Security sandbox to execute arbitrary code.

- **Severity:** High 8.5 (`CVSS:3.0/AV:N/AC:H/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r5c7-qcc9-5v7m

## What is CVE-2017-2650?

CVE-2017-2650 is a high-severity vulnerability in Pipeline: Classpath Step Jenkins plugin, published on 27 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

It was found that the use of Pipeline: Classpath Step Jenkins plugin enables a bypass of the Script Security sandbox for users with SCM commit access, as well as users with e.g. Job/Configure permission in Jenkins.

Weakness: CWE-592 (DEPRECATED: Authentication Bypass Issues)

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

2 open source packages ship an affected version, including cprice404:pipeline-classpath. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cprice404:pipeline-classpath` | Maven | All versions | None |
| `cprice404:pipeline-classpath` | Maven | All versions | None |

Products: Jenkins Pipeline Classpath Step.

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

No fix has been published for CVE-2017-2650 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-2650 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2650 is a high-severity vulnerability in Pipeline: Classpath Step Jenkins plugin, published on 27 Jul 2018. 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-2650 in the wild and no public exploit code.

Affected packages and fixed versions:
- cprice404:pipeline-classpath (Maven): affected all versions; no fix listed
- cprice404:pipeline-classpath (Maven): affected all versions; no fix listed

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

## Sources

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

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