Skip to content
Noroxi
NVD / CVE Program· CNA kubernetes

CVE-2018-1002105: 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

Noroxi assessment

Priority: This week (action score 65/100)

  • Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 86.9% (FIRST EPSS); higher than 99.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: kubernetes (Debian:12) 1.17.4-1; github.com/kubernetes/kubernetes (Go) 1.11.5, 1.12.3, 1.10.11; cri-o (openSUSE:Leap 15.1) 1.17.1-lp151.2.2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Don’t wait for the next maintenance window. Upgrade to kubernetes (Debian:12) 1.17.4-1; github.com/kubernetes/kubernetes (Go) 1.11.5, 1.12.3, 1.10.11; cri-o (openSUSE:Leap 15.1) 1.17.1-lp151.2.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.0—Proof of concept Fix available
Published
Dec 5, 2018
Updated
Jun 16, 2026
EPSS
86.9% · 99th percentile

Report tools

JSON

Action score

65

This week

Don’t wait for the next maintenance window.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
26 / 30 · 86.9%

CNA vs NVD score

NVD
9.8
CNA · kubernetes
9.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-1002105

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
kuberneteskubernetes
redhatopenshift container platform
netapptrident

Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)

Watch new CVEs for kubernetes

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • kubernetes kubernetes1.0.0 and later · up to 1.9.11 inclusive
  • kubernetes kubernetes1.10.0 and later · up to 1.10.10 inclusive
  • kubernetes kubernetes1.11.0 and later · up to 1.11.4 inclusive
  • kubernetes kubernetes1.12.0 and later · up to 1.12.2 inclusive
  • kubernetes kubernetes1.9.12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.

  • Kubernetes Kubernetes

    • v1.0.x, v1.1.x, v1.2.x, v1.3.x, v1.4.x, v1.5.x, v1.6.x, v1.7.x, v1.8.x, v1.9.xaffected
    • unspecified and later · before v1.10.11affected
    • unspecified and later · before v1.11.5affected
    • unspecified and later · before v1.12.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12kubernetesbefore 1.17.4-11.17.4-1
Gogithub.com/kubernetes/kubernetesfrom 1.11.0 · before 1.11.51.11.5
Gogithub.com/kubernetes/kubernetesfrom 1.12.0 · before 1.12.31.12.3
Gogithub.com/kubernetes/kubernetesbefore 1.10.111.10.11
openSUSE:Leap 15.1cri-obefore 1.17.1-lp151.2.21.17.1-lp151.2.2
openSUSE:Leap 15.1cri-toolsbefore 1.18.0-lp151.2.11.18.0-lp151.2.1
openSUSE:Leap 15.1go1.14before 1.14-lp151.6.11.14-lp151.6.1
openSUSE:Leap 15.1kubernetesbefore 1.18.0-lp151.5.11.18.0-lp151.5.1
Red Hat:openshift:3.10::el7atomic-enterprise-service-catalogbefore 1:3.10.72-1.git.1450.7d3f435.el71:3.10.72-1.git.1450.7d3f435.el7
Red Hat:openshift:3.10::el7atomic-enterprise-service-catalog-svcatbefore 1:3.10.72-1.git.1450.7d3f435.el71:3.10.72-1.git.1450.7d3f435.el7
Red Hat:openshift:3.10::el7atomic-openshiftbefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-clientsbefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-clients-redistributablebefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-deschedulerbefore 0:3.10.72-1.git.299.953c1c8.el70:3.10.72-1.git.299.953c1c8.el7
Red Hat:openshift:3.10::el7atomic-openshift-docker-excluderbefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-dockerregistrybefore 0:3.10.72-1.git.390.186ec4f.el70:3.10.72-1.git.390.186ec4f.el7
Red Hat:openshift:3.10::el7atomic-openshift-excluderbefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-hyperkubebefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-hypershiftbefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-masterbefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-nodebefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-node-problem-detectorbefore 0:3.10.72-1.git.252.fa9e8ae.el70:3.10.72-1.git.252.fa9e8ae.el7
Red Hat:openshift:3.10::el7atomic-openshift-podbefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7
Red Hat:openshift:3.10::el7atomic-openshift-sdn-ovsbefore 0:3.10.72-1.git.0.3cb2fdc.el70:3.10.72-1.git.0.3cb2fdc.el7

+96

Other highest-scoring records for the same primary product.

  • CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port
    55Plan
  • CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with
    42Plan
  • CVE-2018-1002101In 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 Wi
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2018-1002100Jun 1, 2018 · In Kubernetes versions 1.5.x, 1.6.x, 1.7.x, 1.8.x, and prior to version 1.9.6, the kubectl cp command insecurely handles tar data returned f
    23Monitor
  • ← EarlierCVE-2016-7075Sep 10, 2018 · It was found that Kubernetes as used by Openshift Enterprise 3 did not correctly validate X.509 client intermediate certificate host name fi
    32Monitor
  • Later →CVE-2019-1002100Apr 1, 2019 · In all Kubernetes versions prior to v1.11.8, v1.12.6, and v1.13.4, users that are authorized to make patch requests to the Kubernetes API Se
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:kubernetes1.17.4-1 · Debian:12Package registry (OSV)
Go:github.com/kubernetes/kubernetes1.10.11Package registry (OSV)
Go:github.com/kubernetes/kubernetes1.11.5Package registry (OSV)
Go:github.com/kubernetes/kubernetes1.12.3Package registry (OSV)
opensuse:cri-o1.17.1-lp151.2.2 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:cri-tools1.18.0-lp151.2.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:go1.141.14-lp151.6.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:kubernetes1.18.0-lp151.5.1 · openSUSE:Leap 15.1Package registry (OSV)
red hat:atomic-openshift0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-clients0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-clients-redistributable0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-cluster-capacity0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-docker-excluder0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-dockerregistry0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-excluder0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-federation-services0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-master0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-node0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-pod0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)
red hat:atomic-openshift-sdn-ovs0:3.7.72-1.git.0.925b9cd.el7 · Red Hat:openshift:3.7::el7Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×2
  • Proof-of-concept repository on GitHub ×5

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entryremote2018-12-10
Exploit-DB entryremote2018-12-10
Proof-of-concept repository on GitHubstars:1912018-12-05
Proof-of-concept repository on GitHubstars:2232018-12-06
Proof-of-concept repository on GitHubstars:42018-12-10
Proof-of-concept repository on GitHubstars:12019-04-30
Proof-of-concept repository on GitHubstars:12022-04-06

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-1 d
  2. Published
  3. TodayNov 2, 2026+2888 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-388 · 7PK - Errors

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records