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

Vulnerability Leaves Container Images Without Passwords

A old vulnerability in Alpine Linux containers has spread and propagated to as much as 20% of the containers on the Docker Store.

Nearly one in five of the most popular containers available on the Docker store have no password for root access. That's the finding of researcher Jerry Gamblin, building on work by researchers at Cisco Talos. The result could easily be hundreds of thousands of containers deployed with no functional password at all.

The finding is important because containers, most frequently with Docker as the container manager, are becoming popular for deploying virtualized applications (as opposed to completed virtualized servers deployed with products like VMware or Microsoft Hyper-V). As Docker puts it, "A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries, and settings." 

In order to save time, developers will often put a container image into a repository for reuse, or they'll look at a public repository, like GitHub or the Docker Store, to find containers built by others that they can download and use. If those publicly available containers have vulnerabilities, they can quickly spread across the Internet.

According to the original Cisco Talos report, the vulnerability began with "null" passwords for the root user in Docker images for Alpine Linux, a lightweight, container-specific Linux distribution very popular in container development.

The vulnerability, now designated CVE-2019-5021, was first discovered in 2015 and patched — but then eight days later someone replaced a patched file with another file that enabled the vulnerability. A series of testing errors allowed the vulnerable files to be retained and distributed until May of this year. The original Alpine Linux images have been repatched, but Gamblin found that many containers remain with the vulnerability intact.

Gamblin, who is principal security engineer at Kenna Security, says the need for development speed — a need that has made containers a more popular deployment option — also means best practices aren't always followed.

"I think we're at the point in containers where they're becoming more useful locally and in small company situations, and you're seeing fewer best practices used," he says. "It's developers, it's system admins, and just people testing software and running it on their local machines that blow by best practices in the name of speed."

The good news for developers and security professionals is that the technology issue around this vulnerability has been solved. It's now up to processes and practices to ensure secure containers are pulled from repositories and deployed.

Gamblin says he sees this as an issue security teams should be aware of but not lose sleep over. "It's a weakness, but it's not a structural weakness," he says.

As he pointed out in a blog post he wrote about the vulnerability: "Deploying containers that allow users to authenticate as root should be avoided at all costs, because authenticating as root is already outside the scope of 'best practices' for secure containers or generally in system."

Related Content:

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
6/1/2019 | 4:09:42 PM
CIS Benchmarks and Image Shell Scripts
Years ago I started creating custom ISO images for deployment.  They were built to interact only with our internal SUSE YaST server hosting handpicked packages, controlled updates, etc.  We needed this level of control and security because we were spinning VMs for a highly monitored and audited ESX ecosystem.  In the early days of the CIS (Center for Internet Security) [1]  they released benchmarks for a handful of operating systems that identified areas of vulnerability and provided base scripts for hardening these OS's.  I took the SUSE Linux benchmark shell scripts and created a hardening master script that was automatically run during the ISO install of every VM we deployed.  This addressed issues like root access, open ports and so forth.  Older VMs of mine installed from this infrastructure of curated images still purr with maximum security.  Sure enough, years later, I see the CIS is still developing useful benchmarks and Docker is one of them [2].  Taken together with other benchmarks with security recommendations for OS and other IoT areas by CIS, issues like the one described could have been avoided, I believe.  This is why we have standards and are in desperate need of well-read, actively auditing and "real-time" InfoSec analysts and managers to execute them and oversee their execution.  I have never used Alpine Linux, but I would expect to see such practices at the heart of any "security-oriented, lightweight Linux distribution" development and deployment process, at a minimum.  Even when issues with packages like BusyBox and use of shadow exist, having automated scripts that exercise hardening and post-hardening tests on Docker images BEFORE ever getting released will ensure images like the ones discussed here are never downloaded by users.    

[1] CIS - Center for Internet Security:  https://cisecurity.org

[2] CIS Benchmarks: https://www.cisecurity.org/cis-benchmarks/

 

 
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9349
PUBLISHED: 2020-04-02
The CACAGOO Cloud Storage Intelligent Camera TV-288ZD-2MP with firmware 3.4.2.0919 allows access to the RTSP service without a password.
CVE-2020-11100
PUBLISHED: 2020-04-02
In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes around a certain location on the heap via a crafted HTTP/2 request, possibly causing remote code execution.
CVE-2020-11450
PUBLISHED: 2020-04-02
Microstrategy Web 10.4 exposes the JVM configuration, CPU architecture, installation folder, and other information through the URL /MicroStrategyWS/happyaxis.jsp. An attacker could use this vulnerability to learn more about the environment the application is running in.
CVE-2020-11451
PUBLISHED: 2020-04-02
The Upload Visualization plugin in the Microstrategy Web 10.4 admin panel allows an administrator to upload a ZIP archive containing files with arbitrary extensions and data. (This is also exploitable via SSRF.)
CVE-2020-11454
PUBLISHED: 2020-04-02
Microstrategy Web 10.4 is vulnerable to Stored XSS in the HTML Container and Insert Text features in the window, allowing for the creation of a new dashboard. In order to exploit this vulnerability, a user needs to get access to a shared dashboard or have the ability to create a dashboard on the app...