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 //

IaaS

3/26/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Cybercriminals Using Kubernetes, Docker to Bitcoin Mine

Supposedly safe and secure Docker containers and the Kubernetes orchestration system can actually be manipulated to mine Bitcoin and other cryptocurrencies, researchers have found.

Cybercriminals have been running cryptocurrency attacks on hijacked machines for some time, finding it more profitable than ransomware. Now however, malware authors have found a new way to take their nefarious actions into the cloud and bypass the need for hijacking individual computers.

Reports have surfaced of attempts to run mining activities on Docker and Kubernetes systems. At the start of 2018, Sysdig researchers found that the Kubernetes instances on their honeypot servers were being attacked, with the aim of creating Docker containers that would mine Bitcoin.

Sysdig saw that the attacker created a container that mounted /etc/ from the host filesystem to /mnt/etc/ inside the container.

(Source: Pixabay)
(Source: Pixabay)

Then, by writing to files below /mnt/etc/ inside the container, they can write to files below /etc on the host. They were writing to /etc/crontab, which then downloaded a file every minute and then ran as a bash script. That script would kill any competing mining programs and install its own Bitcoin miner which used all of the host machine's available cores.

A similar attack scheme was noted by Aqua Security and explained on its blog. The effective difference between the two events was Aqua noted Monero mining occurring on net-exposed Docker containers that were not bounded by Kubernetes.

The unanswered question in all of this was how a Kubernetes instance -- such as Sysdig had running -- could be breached to allow the mining to happen.

It took Alexander Urcioli, senior security engineer at Handy HQ, to connect the dots.

Urcioli discovered that on a co-worker's machine an attacker ran commands on a Kubernetes instance without authentication, something that should not have happened. He wrote on Medium that he discovered a misconfiguration in how Kubernetes was deployed that had startling effects.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth annual Big Communications Event. There's still time to register and communications service providers get in free!

Specifically, Urcioli knew the Kubernetes api-server was publicly exposed to the Internet but was protected with certificate authentication. He realized that:

Unless you specify some flags on Kubelet, it's default mode of operation is to accept unauthenticated API requests. Keep in mind that in order for master -> node communication to work, the Kubernetes API server must be able to talk to kubelet on your nodes.

The co-worker's server had mistakenly been configured to allow the public exposing of the kubelet ports (tcp 10250, tcp 10255) to the net. That meant the attacker could access them as use the kubelet API as a backdoor into the cluster.

And now the reason the attack worked at all seems far less mysterious. The kubelet has to be locked down, or it will let almost anything get in. This has to be done explicitly, because it doesn't happen by default.

Configuration issues are being realized as a major security issue of late. Recent configuration problems in Amazon S3 containers have left private information publicly accessible, for example. Security professionals will need to pay attention to the details of configuration or pay the price in Monero.

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
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-4172
PUBLISHED: 2022-01-22
Cross-site Scripting (XSS) - Stored in GitHub repository star7th/showdoc prior to 2.10.2.
CVE-2022-23807
PUBLISHED: 2022-01-22
An issue was discovered in phpMyAdmin 4.9 before 4.9.8 and 5.1 before 5.1.2. A valid user who is already authenticated to phpMyAdmin can manipulate their account to bypass two-factor authentication for future login instances.
CVE-2022-23808
PUBLISHED: 2022-01-22
An issue was discovered in phpMyAdmin 5.1 before 5.1.2. An attacker can inject malicious code into aspects of the setup script, which can allow XSS or HTML injection.
CVE-2022-21707
PUBLISHED: 2022-01-21
wasmCloud Host Runtime is a server process that securely hosts and provides dispatch for web assembly (WASM) actors and capability providers. In versions prior to 0.52.2 actors can bypass capability authorization. Actors are normally required to declare their capabilities for inbound invocations, bu...
CVE-2022-21708
PUBLISHED: 2022-01-21
graphql-go is a GraphQL server with a focus on ease of use. In versions prior to 1.3.0 there exists a DoS vulnerability that is possible due to a bug in the library that would allow an attacker with specifically designed queries to cause stack overflow panics. Any user with access to the GraphQL han...