New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2020-8558: Node setting allows for neighboring hosts to bypass localhost boundary #92315
Comments
|
For insecure port removal: #91506 |
|
The original announcement contained an error. The announcement makes it sound like upgrading kube-proxy will address the issue, but that is incorrect. I have edited the issue summary to add the following paragraph in the "Fixed Versions" section:
Additionally, I have changed the components in listed versions to say kubelet/kube-proxy instead of kube-proxy. |
|
Could you add numerical CVSS scores to these? "High" is too vague, frequently varies from vendor to vendor. I can calculate a score from the vector myself, but adding the score would save us some work... |
|
Edited. Also, the vector scores are clickable and will show the CVSS scores too. |
|
To be clear, this is fixed in v1.18.4+, v1.17.7+, and v1.16.11+ correct? |
|
Right. Sorry if the extra paragraph in "Fixed Versions" made that unclear. |
|
Got it. Thank you! |
So just to be sure, this wouldn't be a problem in an EKS cluster running in its own VPC, right? (assuming no untrusted hosts on the same VPC) |
|
Are all the conditions listed under |
Edit: after more testing, I think |
The attack can be done from any pod with @joelsmith a more accurate title: "Node setting allows to bypass localhost boundary" |
|
We believe that of the four conditions, you might be affected if (1 and (2 or 3) and 4) are true for your cluster. Sorry that it's not super clear from the text. Trying and failing to convey info concisely and with precision makes me glad that I'm in software, not law. |
|
Isn't this broadly fixed by #91569 ? We're discussing better answers and options for deployment, too, but I am curious what the close-condition for this bug is? |
|
@thockin I made a typo in the issue description saying that this is addressed by 81569 instead of 91569. I'll edit it now. Sorry about that. Yes, this is mostly fixed by #91569. I marked this as closed due to that PR fixing the majority of security issues caused by the |
|
Sorry, folks. I thought that this issue was already closed. Maybe that makes my response above to @thockin less confusing. |
|
Yes, this being open was one of the major points of confusion for us. Appreciate the clarification @thockin @joelsmith |
|
/label official-cve-feed (Related to kubernetes/sig-security#1) |
CVSS Rating:
In typical clusters: medium (5.4) CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
In clusters where API server insecure port has not been disabled: high (8.8) CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
A security issue was discovered in
kube-proxywhich allows adjacent hosts to reach TCP and UDP services bound to127.0.0.1running 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 on127.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 port1234required 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.The Kubernetes API Server's default insecure port setting causes the API server to listen on
127.0.0.1:8080where it will accept requests without authentication. Many Kubernetes installers explicitly disable the API Server's insecure port, but in clusters where it is not disabled, an attacker with access to another system on the same LAN or with control of a container running on the master may be able to reach the API server and execute arbitrary API requests on the cluster. This port is deprecated, and will be removed in Kubernetes v1.20.Am I vulnerable?
You may be vulnerable if:
You are running a vulnerable version (see below)
Your cluster nodes run in an environment where untrusted hosts share the same layer 2 domain (i.e. same LAN) as nodes
Your cluster allows untrusted pods to run containers with
CAP_NET_RAW(the Kubernetes default is to allow this capability).Your nodes (or hostnetwork pods) run any localhost-only services which do not require any further authentication. To list services that are potentially affected, run the following commands on nodes:
-
lsof +c 15 -P -n -i4TCP@127.0.0.1 -sTCP:LISTEN-
lsof +c 15 -P -n -i4UDP@127.0.0.1On a master node, an lsof entry like this indicates that the API server may be listening with an insecure port:
Affected Versions
How do I mitigate this vulnerability?
Prior to upgrading, this vulnerability can be mitigated by manually adding an iptables rule on nodes. This rule will reject traffic to 127.0.0.1 which does not originate on the node.
iptables -I INPUT --dst 127.0.0.0/8 ! --src 127.0.0.0/8 -m conntrack ! --ctstate RELATED,ESTABLISHED,DNAT -j DROPAdditionally, if your cluster does not already have the API Server insecure port disabled, we strongly suggest that you disable it. Add the following flag to your kubernetes API server command line:
--insecure-port=0Detection
Packets on the wire with an IPv4 destination in the range 127.0.0.0/8 and a layer-2 destination MAC address of a node may indicate that an attack is targeting this vulnerability.
Fixed Versions
Although the issue is caused by
kube-proxy, the current fix for the issue is inkubelet(although future versions may have the fix inkube-proxyinstead). We recommend updating bothkubeletandkube-proxyto be sure the issue is addressed.The following versions contain the fix:
To upgrade, refer to the documentation: https://kubernetes.io/docs/tasks/administer-cluster/cluster-management/#upgrading-a-cluster
Additional Details
This issue was originally raised in issue #90259 which details how the
kube-proxysetsnet.ipv4.conf.all.route_localnet=1which causes the system not to reject traffic to localhost which originates on other hosts.IPv6-only services that bind to a
localhostaddress are not affected.There may be additional attack vectors possible in addition to those fixed by #91569 and its cherry-picks. For those attacks to succeed, the target service would need to be UDP and the attack could only rely upon sending UDP datagrams since it wouldn't receive any replies. Finally, the target node would need to have reverse-path filtering disabled for an attack to have any effect. Work is ongoing to determine whether and how this issue should be fixed. See #91666 for up-to-date status on this issue.
Acknowledgements
This vulnerability was reported by János Kövér, Ericsson with additional impacts reported by Rory McCune, NCC Group and Yuval Avrahami and Ariel Zelivansky, Palo Alto Networks.
/area security
/kind bug
/committee product-security
/sig network
/sig node
/area kubelet
The text was updated successfully, but these errors were encountered: