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.

Application Security //

Database

End of Bibblio RCM includes -->
3/28/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb

Researcher Finds etcd Servers Leak Passwords Like a Sieve

Security researchers find that etcd servers, an essential part of Kubernetes, as well as other database system, have been leaking passwords for a long time.

Kubernetes is an open source system for automating deployment, scaling and management of containerized applications in the cloud. First developed by Google, the orchestration software has had some serious security problems show up lately.

Now, there's another problem coming to light, but it's due to one of Kubernetes components: etcd. (See Cybercriminals Using Kubernetes, Docker to Bitcoin Mine.)

etcd is an open source distributed key value store written in the Google Go language that provides a "reliable" way to store data across a cluster of machines. One can read and write values with curl and other HTTP libraries. It's sort of like an expandable database that changes with how the clusters that are in use change.

(Source: Geralt via Pixabay)

Security researcher Giovanni Collazo got curious when he saw in some etcd documentation that:

etcd before 2.1 was a completely open system; anyone with access to the API could change keys. In order to preserve backward compatibility and upgradability, this feature is off by default.

This made him wonder if the kind of problems that had been affecting MongoDB --misconfiguration that could stop authentication -- was in play here. It was.

As he wrote in his blog on the issue, Collazo did a simple Shodan search and found 2,284 etcd servers on the open Internet. From these servers he was able to download "passwords for databases of all kinds, AWS secret keys, and API keys and secrets for a bunch of services. Also came across a few certificates, you name it."

The data included the passwords and keys required for cms_admin, mysql_root and postgres server infrastructure.

So, in conclusion, etcd can be easily misconfigured and then leak secrets like a sieve.

But -- and this ties the whole thing together -- etcd is used as Kubernetes' backing store for all cluster data. Usually that data in the backing store will include secrets encoded as base64 strings. An attacker can get into one of these poorly configured servers and come back with stuff that will compromised the entire Kubernetes cluster.

Using the etcd API, an attacker could also write to the database. This might invalidate the cluster data stored in it, or serve as a way to hide data that was taken in another attack.

In an email to Security Now, Zohar Alon, CEO of security company Dome9, wrote:

There were two levels of security failure here -- one, no password protection for the service by default, and two, servers with ports exposed to the whole world when they should have been locked down.

Kubernetes dependency upon etcd is a non-obvious vulnerability, but a serious one. If this kind of system is deployed by an organization, they would do well to ascertain that it has been locked down by them before someone gets the idea to attack it.

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
Newest First  |  Oldest 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-25878
PUBLISHED: 2022-05-27
The package protobufjs before 6.11.3 are vulnerable to Prototype Pollution which can allow an attacker to add/modify properties of the Object.prototype. This vulnerability can occur in multiple ways: 1. by providing untrusted user input to util.setProperty or to ReflectionObject.setParsedOption ...
CVE-2021-27780
PUBLISHED: 2022-05-27
The software may be vulnerable to both Un-Auth XML interaction and unauthenticated device enrollment.
CVE-2021-27781
PUBLISHED: 2022-05-27
The Master operator may be able to embed script tag in HTML with alert pop-up display cookie.
CVE-2022-1897
PUBLISHED: 2022-05-27
Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
CVE-2022-20666
PUBLISHED: 2022-05-27
Multiple vulnerabilities in the web-based management interface of Cisco Common Services Platform Collector (CSPC) Software could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface. These vulnerabilities are due to insufficient va...