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.

Attacks/Breaches

4/29/2019
06:50 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Docker Forces Password Reset for 190,000 Accounts After Breach

Organizations impacted by breach, which gave attackers illegal access to a database containing sensitive account information, need to check their container images.

The owners of some 190,000 Docker accounts will need to change their passwords and verify their container images haven't been tampered with as the result of a recent intrusion into a Docker Hub database.

Docker discovered the unauthorized access on April 25. It said it had already notified impacted users about the incident and sent them a password-reset link.

The company said it had also unlinked Docker Hub from GitHub and Bitbucket for those using these external repositories to automatically build — or autobuild — container images. Such users will need to relink their Docker Hub accounts to these repositories in order for autobuild to work properly.

Docker described the intrusion as something that gave attackers a "brief period" of illegal access to a database containing sensitive account information, including usernames and hashed passwords. Also exposed in the breach were tokens that some Docker Hub account owners used to access their repositories on GitHub and Bitbucket. It offered no details on when the breach might have occurred and how it was discovered.

Docker said the 190,000 accounts that had been impacted in the breach represented less than 5% of the overall number of users of its Hub cloud-based container image repository. "No Official Images have been compromised," the company said in a FAQ. Docker pointed to several additional security measures it has in place for protecting its Official Images, including GPG (GNU Privacy Guard) signatures and Notary signing for each image.

Docker Hub is a container image library that developers, software vendors, open source projects, and enterprise software teams use to store and share container images. Many organizations, including large enterprises, use images from the repository to build their containers.

Attacks on the developer pipeline can have a serious impact on application security, says Wei Lien Dang, vice president of product at container security vendor StackRox. "Tainted images can be difficult to detect, and the containers launched from them may even run as expected, except with a malicious process in the background," Lein says.

Since Docker has so far not provided a timeline for the incident, it is unclear how long the attackers might have had access to the compromised accounts, Wei says. To be safe, users need to go back and verify the integrity of any images they might have pushed out over the past several weeks.

Chris Wysopal, CTO of Veracode, says organizations that have been notified should be looking at their logs for signs of unauthorized access, especially if write access was performed. "In this instance, it is critical to review your GitHub logs if you integrated with DockerHub because you will have given DockerHub write access to your repos," he says.

In addition, importing production images to a private registry instead of pulling directly from a public registry can give enterprises more control and separation from events, such as the one involving Docker Hub, Wysopal says. "You can easily go and look at the timeline of the breach and see if you pulled an image during the period the public registry was compromised," he says.

Without any evidence of confirmed malicious tampering, the main takeaway from this breach for organizations is the need to include supply chain attacks in threat modeling exercises, says Tim Erlin, vice president of product management and strategy at Tripwire.

"Organizations that have considered this type of event in their response plan won't be panicking when an incident occurs," Erlin notes. "The key to incident response is to be prepared, and threat modeling allows an organization to identify and prepare for the most relevant threats."

Related Content:

 

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/29/2019 | 10:21:50 PM
And sent them a password-reset link....
The 'and sent them a password reset link....' sends the connotation that it was not a forced reset. Were the owners not allowed to log in unless they utilized this link or if they disregarded it could they still log in using their old passwords such as when a typical pw reset link is sent. 
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-1817
PUBLISHED: 2019-11-20
MediaWiki before 1.19.4 and 1.20.x before 1.20.3 contains an error in the api.php script which allows remote attackers to obtain sensitive information.
CVE-2013-2091
PUBLISHED: 2019-11-20
SQL injection vulnerability in Dolibarr ERP/CRM 3.3.1 allows remote attackers to execute arbitrary SQL commands via the 'pays' parameter in fiche.php.
CVE-2012-1257
PUBLISHED: 2019-11-20
Pidgin 2.10.0 uses DBUS for certain cleartext communication, which allows local users to obtain sensitive information via a dbus session monitor.
CVE-2013-1816
PUBLISHED: 2019-11-20
MediaWiki before 1.19.4 and 1.20.x before 1.20.3 allows remote attackers to cause a denial of service (application crash) by sending a specially crafted request.
CVE-2011-4455
PUBLISHED: 2019-11-20
Multiple cross-site scripting vulnerabilities in Tiki 7.2 and earlier allow remote attackers to inject arbitrary web script or HTML via the path info to (1) tiki-admin_system.php, (2) tiki-pagehistory.php, (3) tiki-removepage.php, or (4) tiki-rename_page.php.