LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1002105: In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses t...

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.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This Kubernetes flaw let unauthenticated attackers use the API server as a trusted bridge to backend services. Successful abuse could bypass normal authorization and affect confidentiality, integrity, and availability of cluster resources.

Executive priority

Treat as urgent for any legacy Kubernetes estate. The issue is critical, remotely reachable, and can turn API server trust into backend access. Modern supported clusters should verify patch status rather than assume immunity.

Technical view

kube-apiserver incorrectly handled error responses for proxied upgrade requests. In affected versions, crafted requests could keep a backend connection open and send arbitrary requests authenticated with the API server's TLS credentials.

Likely exposure

Exposure is likely for Kubernetes control planes before v1.10.11, v1.11.5, or v1.12.3, including earlier v1.0-v1.9 lines and downstream vendor builds not updated through their advisories.

Exploitation context

The provided bundle lists public Exploit-DB entries and a public PoC reference, so exploitation knowledge is public. The bundle marks KEV as false and does not prove active exploitation.

Researcher notes

Avoid overclaiming current exploitation from this bundle. Focus validation on kube-apiserver version provenance, vendor packaging state, and audit evidence around proxied upgrade behavior. Public exploit references increase operational risk.

Mitigation direction

  • Upgrade Kubernetes to v1.10.11, v1.11.5, v1.12.3, or later supported releases.
  • Apply relevant downstream vendor fixes, including Red Hat or other platform advisories.
  • Prioritize externally reachable or shared Kubernetes API servers first.
  • Review vendor guidance for any product-specific hardening or compensating controls.

Validation and detection

  • Inventory all Kubernetes API server versions across production, staging, and managed platforms.
  • Confirm vendor distributions include fixes for CVE-2018-1002105.
  • Review API server audit logs for unusual proxied upgrade or backend request patterns.
  • Check vulnerability scanners and SBOM data for affected Kubernetes versions.
Prepared
Confidence
high
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-1002105 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
16Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.0CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

9.8Critical
CVSS 3.0 vector shape for CVE-2018-1002105Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KubernetesKubernetesv1.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.x, unspecified, unspecified, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.