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 requests to the Kubernetes API…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 16.9% (FIRST EPSS); higher than 97.1% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kubernetes (Debian:12) 1.17.4-1; k8s.io/kubernetes (Go) 1.11.8, 1.12.6, 1.13.4; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250807T150727-1.1.
Low priority for now. Upgrade to kubernetes (Debian:12) 1.17.4-1; k8s.io/kubernetes (Go) 1.11.8, 1.12.6, 1.13.4; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250807T150727-1.1 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.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.
- Published
- Apr 1, 2019
- Updated
- Jun 16, 2026
- EPSS
- 16.9% · 97th percentile
- CWE
- CWE-770
Report tools
Action score
31
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 16.9%
CNA vs NVD score
- NVD
- 6.5
- CNA · dwf
- 6.5
- agree
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| kubernetes | kubernetes | cpe:2.3:a:kubernetes:kubernetes |
| redhat | openshift container platform | cpe:2.3:a:redhat:openshift_container_platform |
Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (dwf). 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.x, v1.10.xaffected
- unspecified and later · before v1.11.8affected
- unspecified and later · before v1.12.6affected
- unspecified and later · before v1.13.4affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kubernetes kubernetesbefore 1.11.8
- kubernetes kubernetes1.12.0 and later · before 1.12.6
- kubernetes kubernetes1.13.0 and later · before 1.13.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | kubernetes | before 1.17.4-1 | 1.17.4-1 |
| Go | k8s.io/kubernetes | from 1.0.0 · up to and including 1.10.14 | — |
| Go | k8s.io/kubernetes | from 1.0.0 · before 1.11.8 | 1.11.8 |
| Go | k8s.io/kubernetes | from 1.11.0 · before 1.11.8 | 1.11.8 |
| Go | k8s.io/kubernetes | from 1.12.0 · before 1.12.6 | 1.12.6 |
| Go | k8s.io/kubernetes | from 1.13.0 · before 1.13.4 | 1.13.4 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250807T150727-1.1 | 0.0.20250807T150727-1.1 |
| Red Hat:openshift:3.10::el7 | atomic-openshift | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-clients | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-clients-redistributable | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-docker-excluder | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-excluder | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-hyperkube | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-hypershift | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-master | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-node | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-pod | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-sdn-ovs | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-template-service-broker | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.10::el7 | atomic-openshift-tests | before 0:3.10.181-1.git.0.3ab4b3d.el7 | 0:3.10.181-1.git.0.3ab4b3d.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift | before 0:3.11.129-1.git.0.bd4f2d5.el7 | 0:3.11.129-1.git.0.bd4f2d5.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients | before 0:3.11.129-1.git.0.bd4f2d5.el7 | 0:3.11.129-1.git.0.bd4f2d5.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.129-1.git.0.bd4f2d5.el7 | 0:3.11.129-1.git.0.bd4f2d5.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.129-1.git.0.bd4f2d5.el7 | 0:3.11.129-1.git.0.bd4f2d5.el7 |
+10
Same product
kubernetes: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1002105In 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…65This week
- CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port55Plan
- 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
Published before and after this one in the same product
- ← 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…32Monitor
- ← EarlierCVE-2018-1002101Dec 5, 2018 · In 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…40Plan
- Later →CVE-2019-1002101Apr 1, 2019 · kubectl cp path traversal26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:kubernetes | 1.17.4-1 · Debian:12 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.11.8 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.12.6 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.13.4 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250807T150727-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:atomic-openshift | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients-redistributable | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-docker-excluder | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-excluder | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hyperkube | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hypershift | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-master | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-node | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-pod | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-sdn-ovs | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-template-service-broker | 0:3.11.129-1.git.0.bd4f2d5.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: patch commit or PR link · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.