Kubernetes up to 1.16.1 API Server JSON Payload input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Kubernetes up to 1.0-1.12/1.13.11/1.14.7/1.15.4/1.16.1. This vulnerability affects unknown code of the component API Server. The manipulation as part of JSON Payload results in input validation. This vulnerability is known as CVE-2019-11253. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in Kubernetes up to 1.0-1.12/1.13.11/1.14.7/1.15.4/1.16.1 (Virtualization Software). Affected is an unknown function of the component API Server. The manipulation as part of a JSON Payload leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on availability. CVE summarizes:
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.
The weakness was published 10/17/2019 (Website). The advisory is available at groups.google.com. This vulnerability is traded as CVE-2019-11253 since 04/17/2019. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.
Upgrading to version 1.13.12, 1.14.8, 1.15.5 or 1.16.2 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
- 1.0-1.0
- 1.0-1.1
- 1.0-1.2
- 1.0-1.3
- 1.0-1.4
- 1.0-1.5
- 1.0-1.6
- 1.0-1.7
- 1.0-1.8
- 1.0-1.9
- 1.0-1.10
- 1.0-1.11
- 1.0-1.12
- 1.13.0
- 1.13.1
- 1.13.2
- 1.13.3
- 1.13.4
- 1.13.5
- 1.13.6
- 1.13.7
- 1.13.8
- 1.13.9
- 1.13.10
- 1.13.11
- 1.14.0
- 1.14.1
- 1.14.2
- 1.14.3
- 1.14.4
- 1.14.5
- 1.14.6
- 1.14.7
- 1.15.0
- 1.15.1
- 1.15.2
- 1.15.3
- 1.15.4
- 1.16.0
- 1.16.1
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 7.5
CNA Vector (Kubernetes): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kubernetes 1.13.12/1.14.8/1.15.5/1.16.2
Timeline
04/17/2019 🔍10/17/2019 🔍
10/18/2019 🔍
02/24/2026 🔍
Sources
Product: github.comAdvisory: RHSA-2019:3239
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-11253 (🔍)
GCVE (CVE): GCVE-0-2019-11253
GCVE (VulDB): GCVE-100-143850
Entry
Created: 10/18/2019 10:20Updated: 02/24/2026 23:20
Changes: 10/18/2019 10:20 (40), 10/18/2019 10:25 (18), 01/16/2024 11:45 (4), 01/16/2024 11:54 (12), 02/24/2026 23:20 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.