Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud Security

End of Bibblio RCM includes -->
12/4/2018
10:50 AM
Larry Loeb
Larry Loeb
Larry Loeb

Kubernetes Vulnerability Can Turn Containers Into Zombies

For years, Kubernetes was considered secure. However, a newly published vulnerability can turn enterprise containers into zombies without proper patching.

Over the past several years, Kubernetes has become the leading cloud container orchestration system. It groups data containers that make up an application into logical units for easy management.

Additionally, Kuberneteshas benefited from 15 years of on-the-job training at Google, and is considered to be an underpinning of cloud computing.

Except one guy found a way to make it roll over and turn into a zombie. While it is the first major vulnerability to be discovered in the container system, it's a corker. (See Kubernetes & Containers Stir Security Concerns in the Cloud.)

Darren Shepherd, the co-founder of Rancher Labs and its chief architect, found the vulnerability, which is tracked as CVE-2018-1002105. It has been assigned a CVSS score of 9.8 out of 10, and it is considered critical.

Affected versions of Kubernetes include, Kubernetes v1.0.x-1.9.x, Kubernetes v1.10.0-1.10.10, Kubernetes v1.11.0-1.11.4, and Kubernetes v1.12.0-1.12.2.

(Source: Pixabay)
(Source: Pixabay)

Specifically, this vulnerability allows an attacker to escalate privileges within a system when specially crafted requests are sent to the targeted server.

Jordan Liggitt, who is part of the Kubernetes security team, describes the vulnerability in his blog:

With a specially crafted request, users that are authorized to establish a connection through the Kubernetes API server to a backend server can then send arbitrary requests over the same connection directly to that backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.

That's geekspeak for making it a zombie sock-puppet.

It gets worse. The problem affects configurations that should not let users near the backend servers. Liggett wrote that affected configurations include clusters that run extension API servers -- such as the metrics server -- that are directly accessible from the Kubernetes API server's network, as well as clusters that grant pod exec/attach/portforward permissions to users who are not expected to have full access to kubelet APIs.

Indeed, in default configurations, all users -- authenticated and unauthenticated -- are allowed to perform discovery API calls that pave the way for the escalation to occur.

You can't even detect in a system if this vulnerability has been exploited.

Since the unauthorized requests are made over an established legitimate connection, they won't appear in the Kubernetes API server audit logs or server log. The requests may appear in other logs, but they are indistinguishable from the correctly authorized and proxied requests that come in through the Kubernetes API server.

While there are some mitigations, such as removing all anonymous access to all aggregated APIs, including discovery permissions granted by the default discovery role bindings, many of these are likely to be disruptive, and upgrading to a fixed version is strongly recommended by the security team.

The way out of this one is to patch. It may be a pain and difficult to get everything patched, but it is also absolutely necessary.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-1678
PUBLISHED: 2022-05-25
An issue was discovered in the Linux Kernel from 4.18 to 4.19, an improper update of sock reference in TCP pacing can lead to memory/netns leak, which can be used by remote clients.
CVE-2021-32966
PUBLISHED: 2022-05-25
Philips Interoperability Solution XDS versions 2.5 through 3.11 and 2018-1 through 2021-1 are vulnerable to clear text transmission of sensitive information when configured to use LDAP via TLS and where the domain controller returns LDAP referrals, which may allow an attacker to remotely read LDAP s...
CVE-2021-32989
PUBLISHED: 2022-05-25
When a non-existent resource is requested, the LCDS LAquis SCADA application (version 4.3.1.1011 and prior) returns error messages which may allow reflected cross-site scripting.
CVE-2021-32997
PUBLISHED: 2022-05-25
The affected Baker Hughes Bentley Nevada products (3500 System 1 6.x, Part No. 3060/00 versions 6.98 and prior, 3500 System 1, Part No. 3071/xx & 3072/xx versions 21.1 HF1 and prior, 3500 Rack Configuration, Part No. 129133-01 versions 6.4 and prior, and 3500/22M Firmware, Part No. 288055-01 ver...
CVE-2021-35487
PUBLISHED: 2022-05-25
Nokia Broadcast Message Center through 11.1.0 allows an authenticated user to perform a Boolean Blind SQL Injection attack on the endpoint /owui/block/send-receive-updates (for the Manage Alerts page) via the extIdentifier HTTP POST parameter. This allows an attacker to obtain the database user, dat...