Skip to content

Improper Authentication in Kubernetes

High severity GitHub Reviewed Published Jul 13, 2020 in bottlerocket-os/bottlerocket • Updated Jan 30, 2023

Package

gomod k8s.io/kubernetes (Go)

Affected versions

>= 1.18.0, < 1.18.4
>= 1.17.0, < 1.17.7
< 1.16.11

Patched versions

1.18.4
1.17.7
1.16.11

Description

A security issue was discovered in the Kubelet and kube-proxy components of Kubernetes 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. For example, if a cluster administrator runs a TCP service on a node that listens on 127.0.0.1:1234, because of this bug, that service would be potentially reachable by other hosts on the same LAN as the node, or by containers running on the same node as the service. If the example service on port 1234 required no additional authentication (because it assumed that only other localhost processes could reach it), then it could be vulnerable to attacks that make use of this bug.

References

@tjkirch tjkirch published to bottlerocket-os/bottlerocket Jul 13, 2020
Published by the National Vulnerability Database Jul 27, 2020
Reviewed May 24, 2021
Published to the GitHub Advisory Database Feb 15, 2022
Last updated Jan 30, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.119%
(47th percentile)

Weaknesses

CVE ID

CVE-2020-8558

GHSA ID

GHSA-wqv3-8cm6-h6wg

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.