dbcve.org
KubernetesApplication

CVE-2019-1002100

MEDIUM · 6.5 CVSS v3.1 Published 2019-04-01
Fix available
A fix is available. Upgrade to 1.11.8 / 1.12.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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.11.8, v1.12.6, and v1.13.4, users that are authorized to make patch requests to the Kubernetes API Server can send a specially crafted patch of type "json-patch" (e.g. `kubectl patch --type json` or `"Content-Type: application/json-patch+json"`) that consumes excessive resources while processing, causing a Denial of Service on the API Server.

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 · high confidence

In Kubernetes versions prior to v1.11.8, v1.12.6, and v1.13.4, authenticated users authorized to make patch requests can send specially crafted JSON-patch type requests (via kubectl patch --type json or Content-Type: application/json-patch+json) that consume excessive server resources, leading to API Server denial of service.

MitigationUpgrade Kubernetes to version v1.11.8, v1.12.6, v1.13.4 or later to patch the resource exhaustion vulnerability in JSON-patch processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.11.8>= 1.12.0, < 1.12.6>= 1.13.0, < 1.13.4
Openshift Container PlatformApplication
Affected:= 3.10= 3.11

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Kubernetes API Server version
    Run `kubectl version --short` or check the API Server pod/version directly via `kubectl get pods -n kube-system` and inspect the kube-apiserver container image, or check the output of `kubectl get nodes` and server version
    Affected if The reported server version is prior to v1.11.8, between v1.12.0-v1.12.5, or between v1.13.0-v1.13.3
  2. Identify OpenShift Container Platform version
    Run `oc version` or `oc get clusterversion` to obtain the OpenShift version
    Affected if The OpenShift version is 3.10 or 3.11 (these correspond to the affected Kubernetes versions)
  3. Confirm JSON-patch endpoint is accessible
    Verify the API Server accepts patch requests: attempt a JSON-patch request using `kubectl patch <resource> <name> --type json -p='[...]'` or check for API groups supporting application/json-patch+json via `kubectl api-resources --api-group=` and review API discovery
    Affected if The API Server is reachable and patch-type JSON operations are permitted (this is enabled by default in unpatched versions)

You are affected if your Kubernetes API Server version is below v1.11.8, between v1.12.0-v1.12.5, or between v1.13.0-v1.13.3, or if you run OpenShift Container Platform 3.10 or 3.11.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 1.11.8 / 1.12.6 / 1.13.4 or later
Fixed in 1.11.81.12.61.13.4
Interim mitigation

Upgrade Kubernetes to version v1.11.8, v1.12.6, v1.13.4 or later to patch the resource exhaustion vulnerability in JSON-patch processing.

Fix this in Kubernetes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1002100 — 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-2019-1002100 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