Kubernetes kubelet/kube-proxy up to 1.16.10/1.17.6/1.18.3 Localhost Boundary unprotected alternate channel
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Kubernetes kubelet and kube-proxy up to 1.16.10/1.17.6/1.18.3. This vulnerability affects unknown code of the component Localhost Boundary Handler. Such manipulation leads to unprotected alternate channel. This vulnerability is traded as CVE-2020-8558. Access to the local network is required for this attack to succeed. There is no exploit available.
Details
A vulnerability, which was classified as critical, has been found in Kubernetes kubelet and kube-proxy up to 1.16.10/1.17.6/1.18.3 (Virtualization Software). Affected by this issue is an unknown code block of the component Localhost Boundary Handler. The manipulation with an unknown input leads to a unprotected alternate channel vulnerability. Using CWE to declare the problem leads to CWE-420. The product protects a primary channel, but it does not use the same level of protection for an alternate channel. Impacted is confidentiality, integrity, and availability. CVE summarizes:
The Kubelet and kube-proxy components in versions 1.1.0-1.16.10, 1.17.0-1.17.6, and 1.18.0-1.18.3 were found to contain a security issue which allows adjacent hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace. Such a service is generally thought to be reachable only by other processes on the same host, but due to this defeect, could be reachable by other hosts on the same LAN as the node, or by containers running on the same node as the service.
The weakness was shared 07/09/2020 (Website). The advisory is shared for download at blog.alcide.io. This vulnerability is handled as CVE-2020-8558. Access to the local network is required for this attack. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The advisory points out:
A security issue was discovered in kube-proxy which allows adjacent nodes/hosts to reach TCP and UDP services bound to 127.0.0.1 running on the node or in the node's network namespace (host network). This breaks security assumptions made by services listening on localhost.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
aws.amazon.com is providing further details. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 1.16.0
- 1.16.1
- 1.16.2
- 1.16.3
- 1.16.4
- 1.16.5
- 1.16.6
- 1.16.7
- 1.16.8
- 1.16.9
- 1.16.10
- 1.17.0
- 1.17.1
- 1.17.2
- 1.17.3
- 1.17.4
- 1.17.5
- 1.17.6
- 1.18.0
- 1.18.1
- 1.18.2
- 1.18.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
Researcher Base Score: 5.4
Researcher Vector: 🔍
NVD Base Score: 5.4
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: 🔍
Exploiting
Class: Unprotected alternate channelCWE: CWE-420 / CWE-419
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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
02/03/2020 🔍07/09/2020 🔍
07/17/2020 🔍
11/04/2020 🔍
Sources
Advisory: blog.alcide.ioStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-8558 (🔍)
GCVE (CVE): GCVE-0-2020-8558
GCVE (VulDB): GCVE-100-158744
Misc.: 🔍
Entry
Created: 07/17/2020 12:43Updated: 11/04/2020 14:09
Changes: 07/17/2020 12:43 (50), 07/17/2020 12:48 (11), 11/04/2020 14:00 (1), 11/04/2020 14:09 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.