| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Kubernetes. The affected element is an unknown function of the component API Server. The manipulation results in access control. This vulnerability is known as CVE-2016-1906. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Kubernetes (Virtualization Software) (the affected version unknown). It has been classified as very critical. Affected is an unknown part of the component API Server. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
The API server in Kubernetes might allow remote attackers to gain privileges by editing a build configuration to use a restricted strategy.
The weakness was published 02/03/2016 (Website). The advisory is available at github.com. This vulnerability is traded as CVE-2016-1906 since 01/14/2016. 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. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 07/07/2022). This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entry is available at VDB-80789. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.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: 🔍
Patch: github.com
Timeline
01/14/2016 🔍02/03/2016 🔍
02/03/2016 🔍
02/05/2016 🔍
07/07/2022 🔍
Sources
Advisory: RHSA-2016:0070Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-1906 (🔍)
GCVE (CVE): GCVE-0-2016-1906
GCVE (VulDB): GCVE-100-80790
See also: 🔍
Entry
Created: 02/05/2016 09:47Updated: 07/07/2022 06:36
Changes: 02/05/2016 09:47 (48), 07/16/2018 09:10 (8), 07/07/2022 06:36 (3)
Complete: 🔍
Cache ID: 216:DE2:103
No comments yet. Languages: en.
Please log in to comment.