# CVE-2016-1905: Access Restriction Bypass in kubernetes

> Remote authenticated users can bypass admission control to access or modify additional resources via crafted patched objects.

- **Severity:** High 7.7 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **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:** 3 Feb 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xx8c-m748-xr4j, GO-2022-0893, MINI-3g6g-9q63-fr5q, MINI-3jxj-m8gc-3hh5, MINI-4q7g-6mcj-x68c, MINI-4whp-8wx7-qrjj, MINI-67wv-jmc8-x65w, MINI-7hxp-prx6-7rp6, MINI-cc6c-rg45-h9gh, MINI-h3c8-cqw6-8qqj, MINI-jj63-c5j8-2fqv, MINI-mgc4-2ccf-p6rr, MINI-qv5v-ggc5-9gj9, MINI-x8mp-pf5p-rc66

## What is CVE-2016-1905?

CVE-2016-1905 is a high-severity missing authorization vulnerability in Kubernetes Kubernetes, published on 3 Feb 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The API server in Kubernetes does not properly check admission control, which allows remote authenticated users to access additional resources via a crafted patched object.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-1905?

3 open source packages ship an affected version, including github.com/kubernetes/kubernetes. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kubernetes/kubernetes` | Go | All versions | 1.2.0-alpha.6 |
| `github.com/kubernetes/kubernetes` | Go | All versions | 1.2.0-alpha.6 |
| `github.com/kubernetes/kubernetes` | Go | All versions | 1.2.0-alpha.6 |

Products: Kubernetes Kubernetes.

## How do I fix CVE-2016-1905?

Upgrade github.com/kubernetes/kubernetes to 1.2.0-alpha.6 or later.

## Is CVE-2016-1905 being exploited?

There is no known exploitation of CVE-2016-1905 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-2016-1905 and fix it if it is affected.

What it is: CVE-2016-1905 is a high-severity missing authorization vulnerability in Kubernetes Kubernetes, published on 3 Feb 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1905 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kubernetes/kubernetes (Go): affected all versions; fixed in 1.2.0-alpha.6
- github.com/kubernetes/kubernetes (Go): affected all versions; fixed in 1.2.0-alpha.6
- github.com/kubernetes/kubernetes (Go): affected all versions; fixed in 1.2.0-alpha.6

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

## Sources

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

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