Kubernetes API Server JSON/YAML parsing vulnerable to resource exhaustion attack
Noroxi assessment
Priority: Monitor (action score 38/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 25.9% (FIRST EPSS); higher than 97.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. 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.13.12, 1.14.8, 1.15.5; 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.13.12, 1.14.8, 1.15.5; 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
Improper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility.
- Published
- Oct 17, 2019
- Updated
- Jun 16, 2026
- EPSS
- 25.9% · 98th percentile
- CWE
- CWE-20
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 8 / 30 · 25.9%
CNA vs NVD score
- NVD
- 7.5
- CNA · kubernetes
- 7.5
- agree
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
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kubernetes kubernetes1.1.0 and later · up to 1.12.10 inclusive
- kubernetes kubernetes1.13.0 and later · before 1.13.12
- kubernetes kubernetes1.14.0 and later · before 1.14.8
- kubernetes kubernetes1.15.0 and later · before 1.15.5
- kubernetes kubernetes1.16.0 and later · before 1.16.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.
Kubernetes Kubernetes
- prior to 1.13.12, prior to 1.14.8, prior to 1.15.5, prior to 1.16.2, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8 … (+4)affected
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 · before 1.13.12 | 1.13.12 |
| Go | k8s.io/kubernetes | from 1.14.0 · before 1.14.8 | 1.14.8 |
| Go | k8s.io/kubernetes | from 1.15.0 · before 1.15.5 | 1.15.5 |
| Go | k8s.io/kubernetes | from 1.16.0 · before 1.16.2 | 1.16.2 |
| 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.154-1.git.0.7a097ad.el7 | 0:3.11.154-1.git.0.7a097ad.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients | before 0:3.11.154-1.git.0.7a097ad.el7 | 0:3.11.154-1.git.0.7a097ad.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.154-1.git.0.7a097ad.el7 | 0:3.11.154-1.git.0.7a097ad.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.154-1.git.0.7a097ad.el7 | 0:3.11.154-1.git.0.7a097ad.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-excluder | before 0:3.11.154-1.git.0.7a097ad.el7 | 0:3.11.154-1.git.0.7a097ad.el7 |
+56
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 the65This 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
- CVE-2018-1002101In 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 Wi40Plan
- CVE-2017-1000056Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to40Plan
- CVE-2016-1906Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that 40Plan
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.13.12 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.14.8 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.15.5 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.16.2 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250807T150727-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:jaeger | 0:v1.13.1.redhat5-1.el7 · Red Hat:service_mesh:1.0::el7 | Package registry (OSV) |
| red hat:jaeger-operator | 0:v1.13.1.redhat8-1.el7 · Red Hat:service_mesh:1.0::el7 | Package registry (OSV) |
| red hat:kiali | 0:v1.0.7.redhat1-1.el7 · Red Hat:service_mesh:1.0::el7 | Package registry (OSV) |
| red hat:servicemesh | 0:1.0.2-3.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
| red hat:servicemesh-citadel | 0:1.0.2-3.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
| red hat:servicemesh-cni | 0:1.0.2-3.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
| red hat:servicemesh-galley | 0:1.0.2-3.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
| red hat:servicemesh-grafana | 0:6.2.2-24.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
| red hat:servicemesh-grafana-prometheus | 0:6.2.2-24.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
| red hat:servicemesh-istioctl | 0:1.0.2-3.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
| red hat:servicemesh-mixc | 0:1.0.2-3.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
| red hat:servicemesh-mixs | 0:1.0.2-3.el8 · Red Hat:service_mesh:1.0::el8 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Nuclei detection template ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2019-11253 | — |
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).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.