Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2018-1002105

CRITICAL

Privilege Escalation in Kubernetes

Also known asGHSA-579h-mv94-g4gpGO-2022-0792
Published
Dec 5, 2018
Updated
Jul 8, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
13 known

EPSS Exploitation Probability

via FIRST.org ↗
87.0%probability of exploitation in next 30 days
Very High Risk100th percentile0.00%
85.8%87.9%89.9%91.9%89.9%87.0%Jan 26May 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected
🐹github.com/kubernetes/kubernetes🐹github.com/kubernetes/kubernetes🐹github.com/kubernetes/kubernetes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kubernetes/kubernetesall versions1.10.11
🐹Gogithub.com/kubernetes/kubernetes1.11.0&&< 1.11.51.11.5
🐹Gogithub.com/kubernetes/kubernetes1.12.0&&< 1.12.31.12.3
Exploits & PoCs
13

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46052remotemultiple

Kubernetes - (Unauthenticated) Arbitrary Requests

by evict · Dec 10, 2018

EDB-46053remotemultiple

Kubernetes - (Authenticated) Arbitrary Requests

by evict · Dec 10, 2018

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kubernetes/kubernetes. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/kubernetes/kubernetes to 1.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1002105 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2018-1002105 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2018-1002105. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.
O3 Security · Impact-Aware SCA

Is CVE-2018-1002105 in your dependencies?

O3 detects CVE-2018-1002105 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.