Kubernetes up to 1.13.0 rest.AnonymousClientConfig Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Kubernetes up to 1.13.0. This impacts the function rest.AnonymousClientConfig. Performing a manipulation results in credentials management (Credentials).
This vulnerability was named CVE-2019-11243. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as problematic, was found in Kubernetes up to 1.13.0 (Virtualization Software). This affects the function rest.AnonymousClientConfig. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:
In Kubernetes v1.12.0-v1.12.4 and v1.13.0, the rest.AnonymousClientConfig() method returns a copy of the provided config, with credentials removed (bearer token, username/password, and client certificate/key data). In the affected versions, rest.AnonymousClientConfig() did not effectively clear service account credentials loaded using rest.InClusterConfig()
The bug was discovered 04/18/2019. The weakness was presented 04/22/2019 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2019-11243 since 04/17/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-133924 for similar entry. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔍
CNA Base Score: 3.1
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
Name: CredentialsClass: Credentials management / Credentials
CWE: CWE-255
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/17/2019 🔍04/18/2019 🔍
04/22/2019 🔍
04/23/2019 🔍
09/06/2023 🔍
Sources
Advisory: 76797⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-11243 (🔍)
GCVE (CVE): GCVE-0-2019-11243
GCVE (VulDB): GCVE-100-133923
SecurityFocus: 108053
See also: 🔍
Entry
Created: 04/23/2019 08:42Updated: 09/06/2023 10:03
Changes: 04/23/2019 08:42 (57), 06/01/2020 09:32 (3), 09/06/2023 09:58 (4), 09/06/2023 10:03 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.