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.

Endpoint

5/28/2009
01:44 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Members Of Legendary '90s Hacker Group Relaunch Password-Cracking Tool

L0phtCrack is back: Former members of L0pht Heavy Industries retool their tool after buying it back from Symantec

It's official: The famous password-cracking tool L0phtCrack is back, and its creators plan to keep it that way.

L0phtCrack 6 tool, released Wednesday, was developed in 1997 by Christien Rioux, Chris Wysopal, and Peiter "Mudge" Zatko from the former L0pht Heavy Industries -- the hacker think tank best known for testifying before Congress that it could shut down the Internet in 30 minutes. In January of this year, Rioux, Wysopal, and Zatko bought back L0phtCrack from Symantec, and later announced they would build a new version of the tool with support for 64-bit Windows platforms and other new features.

"When Symantec stopped supporting L0phtCrack [in 2005], a lot of people were still using it. They left their customers high and dry," says Mudge, who, along with his co-developers, had initially worried that could happen. "We had clauses in place so that if Symantec ever did cease to support and maintain it, we could have certain options [to get it back]. We didn't want somebody to take it from us and deep-six it. We thought it was a useful tool."

Weak passwords are still a major problem today, even 12 years after Mudge and his colleagues first wrote the proof-of-concept code for L0phtCrack. The tool was later sold commercially by @stake, the security consulting firm that purchased L0pht and then was later acquired by Symantec.

"People are still tremendously dependent on passwords. We have all of these cached credentials and network logons," Mudge says, adding that weak passwords are still getting compromised. "This still needs to be brought to people's attention in a relatively powerful way, and that's what the tool always did."

Among the new features in L0phtCrack 6 is 64-bit support, as well as support for Windows Vista. The tool provides password assessment and recovery, dictionary and brute-force cracking, password-quality scoring, remediation, remote scanning, and executive reporting.

Mudge says he's working on a Mac OS X interface for L0phtCrack, and that later versions of the tool will look at different types of password hashes and encoded credentials. The developers also are exploring how to harness more horsepower for the tool using, for instance, a machine's graphics processing card to handle some of the heavy lifting.

L0phtCrack 6 is available for download from L0pht's newly launched Website. It costs $295 for the Professional version, $595 for the Administrator version, and $1,195 for the Consultant version.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Navigating the Asia-Pacific Threat Landscape: Experts Dive In
Kelly Sheridan, Staff Editor, Dark Reading,  9/25/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...