# CVE-2019-10417: Incorrect Authorization in Jenkins Kubernetes :: Pipeline :: Kubernetes Steps Plugin

> Attackers can bypass Jenkins script security sandbox to invoke arbitrary methods, leading to potential code execution.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ccxh-j7hg-m5mr

## What is CVE-2019-10417?

CVE-2019-10417 is a critical vulnerability in Jenkins Kubernetes :: Pipeline :: Kubernetes Steps Plugin, published on 25 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Kubernetes :: Pipeline :: Kubernetes Steps Plugin provides a custom whitelist for script security that allowed attackers to invoke arbitrary methods, bypassing typical sandbox protection.

## Which versions are affected by CVE-2019-10417?

2 open source packages ship an affected version, including io.fabric8.pipeline:kubernetes-pipeline-steps. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.fabric8.pipeline:kubernetes-pipeline-steps` | Maven | All versions to 1.6 | None |
| `io.fabric8.pipeline:kubernetes-pipeline-steps` | Maven | All versions to 1.6 | None |

Products: Jenkins Kubernetes Pipeline.

## How do I fix CVE-2019-10417?

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

## Is CVE-2019-10417 being exploited?

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

## Other vulnerabilities in Jenkins Kubernetes :: Pipeline :: Kubernetes Steps Plugin

- [CVE-2019-10418](https://insights.sbomify.com/CVE-2019-10418/): Incorrect Authorization in Jenkins Kubernetes :: Pipeline :: Arquillian Steps Plugin (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10417 and fix it if it is affected.

What it is: CVE-2019-10417 is a critical vulnerability in Jenkins Kubernetes :: Pipeline :: Kubernetes Steps Plugin, published on 25 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10417 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.fabric8.pipeline:kubernetes-pipeline-steps (Maven): affected all versions up to 1.6; no fix listed
- io.fabric8.pipeline:kubernetes-pipeline-steps (Maven): affected all versions up to 1.6; 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-2019-10417/ (Markdown: https://insights.sbomify.com/CVE-2019-10417/index.md)
```

## Sources

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

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