LiveActive security incident?Get immediate response
CVE Record

CVE-2019-1002100: In all Kubernetes versions prior to v1.11.8, v1.12.6, and v1.13.4, users that are authorized to make patch...

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-1002100 is a Kubernetes API server denial-of-service issue. A user who already has permission to send patch requests could cause excessive API server resource consumption, potentially disrupting cluster management and workloads that depend on API availability.

Executive priority

Treat as a moderate operational risk. It is not described as data theft or code execution, but API server denial of service can disrupt cluster operations and incident response. Remediate old clusters and reduce excessive patch privileges.

Technical view

Kubernetes versions before v1.11.8, v1.12.6, and v1.13.4 mishandled specially crafted JSON Patch requests. The flaw requires network access to the API server and low-privileged authorization to make patch requests. Impact is availability only, with CVSS 6.5.

Likely exposure

Exposure is most likely in old self-managed or vendor-packaged Kubernetes clusters below the fixed versions, especially where broad RBAC grants allow patch operations. Modern supported clusters should be checked by version and vendor advisory status.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. Abuse requires an authenticated principal authorized to patch Kubernetes resources, so compromised service accounts or overbroad RBAC could matter.

Researcher notes

The key exposure condition is authorized patch access to the API server. Sources identify JSON Patch processing as the resource exhaustion path, but do not provide evidence of public exploitation in this bundle. Avoid assuming unauthenticated impact.

Mitigation direction

  • Upgrade affected control planes to v1.11.8, v1.12.6, v1.13.4, or later supported releases.
  • Review Kubernetes distribution advisories for vendor-specific fixed packages.
  • Restrict patch permissions to least-privileged users and service accounts.
  • Monitor API server CPU, memory, latency, and error-rate anomalies.
  • Prioritize remediation for internet-exposed or broadly accessible API servers.

Validation and detection

  • Inventory Kubernetes control-plane versions across all clusters.
  • Identify users and service accounts with patch permissions.
  • Confirm vendor package status against Red Hat, NetApp, or Kubernetes advisories.
  • Review API server telemetry for unusual resource saturation.
  • Check whether affected clusters are externally reachable or tightly network-restricted.
Prepared
Confidence
high
Sources
7

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-2019-1002100 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
Medium
CVSS
6.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
6Source 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
6.5CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

6.5Medium
CVSS 3.0 vector shape for CVE-2019-1002100Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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, v1.10.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.