dbcve.org
KubernetesApplication

CVE-2018-1002105

CRITICAL · 9.8 CVSS v3.0 Published 2018-12-05
Fix available
A fix is available. Upgrade to after 1.12.2 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KubernetesApplication
Affected:>= 1.0.0, <= 1.9.11>= 1.10.0, <= 1.10.10>= 1.11.0, <= 1.11.4>= 1.12.0, <= 1.12.2= 1.9.12
Openshift Container PlatformApplication
Affected:= 3.2= 3.3= 3.4= 3.5= 3.6= 3.8= 3.10= 3.11
TridentApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.12.2
Vendor patch github.com →
Recommended fix High confidence

Kubernetes: v1.10.11, v1.11.5, or v1.12.3 (or later stable releases); OpenShift: 3.10+; Trident: contact vendor

  1. Identify your current Kubernetes version using: kubectl version --short or cat /etc/kubernetes/kubelet.conf
  2. Determine which affected version range your cluster falls into (1.0.0-1.9.11, 1.10.0-1.10.10, 1.11.0-1.11.4, or 1.12.0-1.12.2)
  3. For Kubernetes 1.10.x: Upgrade to Kubernetes v1.10.11 or later (recommended: v1.10.12 or latest 1.10 stable)
  4. For Kubernetes 1.11.x: Upgrade to Kubernetes v1.11.5 or later (recommended: v1.11.10 or latest 1.11 stable)
  5. For Kubernetes 1.12.x: Upgrade to Kubernetes v1.12.3 or later (recommended: v1.12.10 or latest 1.12 stable)
  6. For Kubernetes 1.9.x or earlier: Upgrade to a minimum of v1.10.11 (recommended: upgrade to a more recent stable branch like 1.13+, 1.14+, or latest stable)
  7. For OpenShift Container Platform 3.2-3.5: Contact Red Hat for specific patch guidance or upgrade to OpenShift 3.10+ which includes the fix
  8. For Trident: Contact NetApp for specific patch guidance
Caveat Upgrading Kubernetes across major versions (e.g., 1.9 to 1.12) may introduce API deprecations; review Kubernetes changelists for breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1002105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1002105 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data