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
 

Recommended Reading:

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/

 

 
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Why Cybersecurity's Silence Matters to Black Lives
Tiffany Ricks, CEO, HacWare,  7/8/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15105
PUBLISHED: 2020-07-10
Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authenticati...
CVE-2020-11061
PUBLISHED: 2020-07-10
In Bareos Director less than or equal to 16.2.10, 17.2.9, 18.2.8, and 19.2.7, a heap overflow allows a malicious client to corrupt the director's memory via oversized digest strings sent during initialization of a verify job. Disabling verify jobs mitigates the problem. This issue is also patched in...
CVE-2020-4042
PUBLISHED: 2020-07-10
Bareos before version 19.2.8 and earlier allows a malicious client to communicate with the director without knowledge of the shared secret if the director allows client initiated connection and connects to the client itself. The malicious client can replay the Bareos director's cram-md5 challenge to...
CVE-2020-11081
PUBLISHED: 2020-07-10
osquery before version 4.4.0 enables a priviledge escalation vulnerability. If a Window system is configured with a PATH that contains a user-writable directory then a local user may write a zlib1.dll DLL, which osquery will attempt to load. Since osquery runs with elevated privileges this enables l...
CVE-2020-6114
PUBLISHED: 2020-07-10
An exploitable SQL injection vulnerability exists in the Admin Reports functionality of Glacies IceHRM v26.6.0.OS (Commit bb274de1751ffb9d09482fd2538f9950a94c510a) . A specially crafted HTTP request can cause SQL injection. An attacker can make an authenticated HTTP request to trigger this vulnerabi...