Kubernetes up to 1.5.4 PodSecurityPolicy Admission Plugin PodSecurityPolicy Object access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Kubernetes 1.5.0/1.5.1/1.5.2/1.5.3/1.5.4 and classified as critical. This impacts an unknown function of the component PodSecurityPolicy Admission Plugin. Executing a manipulation as part of PodSecurityPolicy Object can lead to access control. This vulnerability appears as CVE-2017-1000056. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability classified as critical was found in Kubernetes 1.5.0/1.5.1/1.5.2/1.5.3/1.5.4 (Virtualization Software). This vulnerability affects an unknown code of the component PodSecurityPolicy Admission Plugin. The manipulation as part of a PodSecurityPolicy Object leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to make use of any existing PodSecurityPolicy object.
The bug was discovered 03/21/2017. The weakness was presented 07/17/2017 (GitHub Repository). The advisory is available at github.com. This vulnerability was named CVE-2017-1000056 since 07/10/2017. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 118 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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.3
VulDB Base Score: 7.3
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: Access controlCWE: CWE-264
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
03/21/2017 🔍07/10/2017 🔍
07/17/2017 🔍
07/17/2017 🔍
07/17/2017 🔍
12/12/2022 🔍
Sources
Product: github.comAdvisory: 43459
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-1000056 (🔍)
GCVE (CVE): GCVE-0-2017-1000056
GCVE (VulDB): GCVE-100-103618
Entry
Created: 07/17/2017 23:55Updated: 12/12/2022 14:35
Changes: 07/17/2017 23:55 (57), 10/26/2019 12:28 (2), 12/12/2022 14:35 (4)
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.