# CVE-2018-1002101: Kubernetes Arbitrary Command Injection

> Insecure handling of user input during volume mount setup on Windows nodes allows attackers to inject command line arguments, potentially leading to code execution.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wqwf-x5cj-rg56, GO-2022-0886

## What is CVE-2018-1002101?

CVE-2018-1002101 is a medium-severity command injection vulnerability in Kubernetes Kubernetes, published on 5 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Windows nodes, which could lead to command line argument injection.

## Which versions are affected by CVE-2018-1002101?

7 open source packages ship an affected version, including k8s.io/kubernetes. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/kubernetes` | Go | From 1.10.0 | 1.10.6 |
| `k8s.io/kubernetes` | Go | From 1.10.0 | 1.10.6 |
| `k8s.io/kubernetes` | Go | From 1.11.0 | 1.11.2 |
| `k8s.io/kubernetes` | Go | From 1.11.0 | 1.11.2 |
| `k8s.io/kubernetes` | Go | From 1.9.0 | 1.9.10, 1.10.6, 1.11.2 |
| `k8s.io/kubernetes` | Go | From 1.9.0 | 1.9.10 |
| `k8s.io/kubernetes` | Go | From 1.9.0 | 1.9.10 |

Products: Kubernetes Kubernetes.

## How do I fix CVE-2018-1002101?

Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.10.6, 1.11.2 or 1.9.10.

## Is CVE-2018-1002101 being exploited?

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

## Other vulnerabilities in Kubernetes Kubernetes

- [CVE-2018-1002105](https://insights.sbomify.com/CVE-2018-1002105/): Privilege Escalation in Kubernetes (critical 9.8)
- [CVE-2017-1000056](https://insights.sbomify.com/CVE-2017-1000056/): Kubernetes Privilege Escalation (critical 9.8)
- [CVE-2016-1906](https://insights.sbomify.com/CVE-2016-1906/): Authorization bypass in Openshift (critical 9.8)
- [CVE-2023-3676](https://insights.sbomify.com/CVE-2023-3676/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8)
- [CVE-2023-3955](https://insights.sbomify.com/CVE-2023-3955/): Kubernetes - Windows nodes - Insufficient input sanitization leads to privilege escalation (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1002101 and fix it if it is affected.

What it is: CVE-2018-1002101 is a medium-severity command injection vulnerability in Kubernetes Kubernetes, published on 5 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1002101 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/kubernetes (Go): affected from 1.10.0; fixed in 1.10.6
- k8s.io/kubernetes (Go): affected from 1.10.0; fixed in 1.10.6
- k8s.io/kubernetes (Go): affected from 1.11.0; fixed in 1.11.2
- k8s.io/kubernetes (Go): affected from 1.11.0; fixed in 1.11.2
- k8s.io/kubernetes (Go): affected from 1.9.0; fixed in 1.9.10, 1.10.6, 1.11.2
- k8s.io/kubernetes (Go): affected from 1.9.0; fixed in 1.9.10
- k8s.io/kubernetes (Go): affected from 1.9.0; fixed in 1.9.10

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

## Sources

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

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