Attacks/Breaches

7/5/2018
07:06 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Weak Admin Password Enabled Gentoo GitHub Breach

Had the attacker been quieter, breach may not have been discovered immediately maintainers of popular Linux distribution said.

A weak administrator password allowed an unknown attacker to gain access to the Gentoo Linux distribution's GitHub account and lock developers out of it, the maintainers of the popular open source software said this week.

In the June 28 attack, the intruders also modified the content of Gentoo's repositories and added malicious code to it that among other things was apparently designed to wipe end user content. But various technical safeguards in place would have prevented that particular eventuality, Gentoo maintainers said in a report summarizing findings from their investigation of the incident.

The attack prompted Gentoo to declare all of its code on GitHub as being compromised and resulted in its developers being unable to use GitHub for about five days. Gentoo has since regained control of the Gentoo GitHub Organization, reverted all bad code commits to a known good state and corrected defaced content, the report noted.

Gentoo's investigation shows that the intruder or intruders gained access to an administrator password and used that to take control.

Gentoo's GitHub repository is only a backup of its code. The main repositories are stored on Gentoo hosted infrastructure and do not appear to have been impacted or at risk from the attack, the report said. The primary key that Gentoo uses to digitally sign code changes in the main repository also appears to have been untouched. So future digital signatures with the key can be trusted, the Gentoo administrators said.

Paul Ducklin, senior technologist at Sophos, points to at least three big takeaways from the Gentoo breach.

"The first is that a prompt notification goes an awful long way," he says. "Gentoo didn't beat around the bush or waste time trying to work a marketing spin into the initial report." Instead by fully disclosing what it knew and did not know about the incident up front, the breach got considerable attention and community help quickly.

Secondly, the breach is another reminder of the well-documented risks of using weak, default and easily guessable passwords. Increasingly, threat actors have been using stolen, phished and brute-forced credentials to break into corporate networks and steal data. In many cases attackers using such credentials have been able to remain undetected on victim networks for months while they have moved laterally in search of high-value targets.

Even with the Gentoo breach for instance, the compromise was only discovered because the attack was loud. If the threat actors had not blocked all access to Gentoo's GitHub repositories, the outcome might have been different.  

The takeaway here—like it is for many recent breaches—is to pick proper passwords, Ducklin says. "It seems that the user whose password was guessed had fallen into the trap of using different but obviously similar passwords on multiple sites," he notes.

For example using a core password and then adding small tweaks and suffixes to the password to make it unique for different sites is not good enough. Crooks will figure out your pattern soon enough, Ducklin notes. "Use a password manager and let it choose a totally different password for each site."

Incidents like this also highlight the need for multi-factor authentication. Data breaches involving compromised user credentials are very hard to stop given the implicit trust that most current security approaches confer on users and devices inside the corporate network. So practices like strong authentication are vital to establishing user trust.

"Two factor authentication is your friend,"Ducklin says. "One-time codes for each login make it harder for the crooks."

Related Content:

  

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
No SOPA
50%
50%
No SOPA,
User Rank: Ninja
7/6/2018 | 10:14:56 PM
A Silver Lining on this Open Source Cloud
While it saddens me to see great FOSS projects maligned and even targeted at all, there is a some positive spin to this.  As anyone who has worked on a mature FOSS project can attest to, good formal development processes can actually demonstrate their value in situations like this.  Being able to quickly identify change, roll it back and reissue releases that are clean is no small task.  As often as I hear complaints about the time it takes to implement and adhere to configuration management and release controls, I would simply point to incidents like this as a marker as to why we need them.  
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
7/6/2018 | 11:31:06 AM
GitHub and dev security
After seemingly seeing a new GitHub-account breach in the headlines every few days, isn't it patently obvious that dev culture is antipathetic toward good baseline security? It seems like we in the community should be having a conversation about how to help make security training and security culture more pervasive and more friendly among the developer community.
Understanding Evil Twin AP Attacks and How to Prevent Them
Ryan Orsi, Director of Product Management for Wi-Fi at WatchGuard Technologies,  11/14/2018
Veterans Find New Roles in Enterprise Cybersecurity
Kelly Sheridan, Staff Editor, Dark Reading,  11/12/2018
To Click or Not to Click: The Answer Is Easy
Kowsik Guruswamy, Chief Technology Officer at Menlo Security,  11/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Online Malware and Threats: A Profile of Today's Security Posture
Online Malware and Threats: A Profile of Today's Security Posture
This report offers insight on how security professionals plan to invest in cybersecurity, and how they are prioritizing their resources. Find out what your peers have planned today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19296
PUBLISHED: 2018-11-16
PHPMailer before 5.2.27 and 6.x before 6.0.6 is vulnerable to an object injection attack.
CVE-2018-19301
PUBLISHED: 2018-11-15
tp4a TELEPORT 3.1.0 allows XSS via the login page because a crafted username is mishandled when an administrator later views the system log.
CVE-2018-5407
PUBLISHED: 2018-11-15
Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.
CVE-2018-14934
PUBLISHED: 2018-11-15
The Bluetooth subsystem on Polycom Trio devices with software before 5.5.4 has Incorrect Access Control. An attacker can connect without authentication and subsequently record audio from the device microphone.
CVE-2018-14935
PUBLISHED: 2018-11-15
The Web administration console on Polycom Trio devices with software before 5.5.4 has XSS.