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
Newest First  |  Oldest First  |  Threaded View
News
US Formally Attributes SolarWinds Attack to Russian Intelligence Agency
Jai Vijayan, Contributing Writer,  4/15/2021
News
Dependency Problems Increase for Open Source Components
Robert Lemos, Contributing Writer,  4/14/2021
News
FBI Operation Remotely Removes Web Shells From Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-22893
PUBLISHED: 2021-04-23
Pulse Connect Secure 9.0R3/9.1R1 and higher is vulnerable to an authentication bypass vulnerability exposed by the Windows File Share Browser and Pulse Secure Collaboration features of Pulse Connect Secure that can allow an unauthenticated user to perform remote arbitrary code execution on the Pulse...
CVE-2021-31408
PUBLISHED: 2021-04-23
Authentication.logout() helper in com.vaadin:flow-client versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after t...
CVE-2021-31410
PUBLISHED: 2021-04-23
Overly relaxed configuration of frontend resources server in Vaadin Designer versions 4.3.0 through 4.6.3 allows remote attackers to access project sources via crafted HTTP request.
CVE-2021-31539
PUBLISHED: 2021-04-23
Wowza Streaming Engine through 4.8.5 (in a default installation) has cleartext passwords stored in the conf/admin.password file. A regular local user is able to read usernames and passwords.
CVE-2021-31540
PUBLISHED: 2021-04-23
Wowza Streaming Engine through 4.8.5 (in a default installation) has incorrect file permissions of configuration files in the conf/ directory. A regular local user is able to read and write to all the configuration files, e.g., modify the application server configuration.