Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 731802 (CVE-2020-8558) - [Tracker] Kubernetes: Vulnerabilities in kubelet and kube-proxy (CVE-2020-8558)
Summary: [Tracker] Kubernetes: Vulnerabilities in kubelet and kube-proxy (CVE-2020-8558)
Status: RESOLVED FIXED
Alias: CVE-2020-8558
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo Security
URL: https://github.com/kubernetes/kuberne...
Whiteboard:
Keywords:
Depends on: 731800 731804
Blocks:
  Show dependency tree
 
Reported: 2020-07-09 00:57 UTC by John Helmert III
Modified: 2021-01-06 08:39 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Helmert III archtester Gentoo Infrastructure gentoo-dev Security 2020-07-09 00:57:14 UTC
CVE-2020-8558:

A security issue was discovered in kube-proxy 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.

Fixed versions:

Although the issue is caused by kube-proxy, the current fix for the issue is in kubelet (although future versions may have the fix in kube-proxy instead). We recommend updating both kubelet and kube-proxy to be sure the issue is addressed.

The following versions contain the fix:

    kubelet/kube-proxy master - fixed by #91569
    kubelet/kube-proxy v1.18.4+ - fixed by #92038
    kubelet/kube-proxy v1.17.7+ - fixed by #92039
    kubelet/kube-proxy v1.16.11+ - fixed by #92040