Vulnerabilities / Threats
8/16/2010
01:37 PM
Connect Directly
RSS
E-Mail
50%
50%

Passwords Quickly Hacked With PC Graphics Cards

Georgia Tech researchers find that high-end, readily available graphics processing units are powerful enough to easily crack secret codes.




Slideshow: Cloud Security Pros And Cons
(click for larger image and for full photo gallery)
Passwords with fewer than 12 characters can be quickly brute-force decoded using a PC graphics processing unit (GPU) that costs just a few hundred dollars, according to researchers at the Georgia Institute of Technology.

"We've been using a commonly available graphics processor to test the integrity of typical passwords of the kind in use here at Georgia Tech and many other places," said Richard Boyd, a senior research scientist at the university's research institute, in a statement. "Right now we can confidently say that a seven-character password is hopelessly inadequate."

Today's top graphics processors offer about two teraflops of parallel processing power. For comparison, "in the year 2000, the world's fastest supercomputer, a cluster of linked machines costing $110 million, operated at slightly more than 7 teraflops," he said.

The barrier to using multi-core graphics processors -- available from Nvidia or AMD's ATI division -- for compute-intensive processes other than graphics processing, said Boyd, first fell in 2007, when Nvidia released a C-based software development kit. "Once Nvidia did that, interest in GPUs really started taking off," he said. "If you can write a C program, you can program a GPU now." Or use it to crack a password.

Furthermore, thanks to Moore's Law, graphics processors continue to increase in power, which means that GPUs will get better, not worse, at cracking passwords.

But who needs a graphics processor? People often create and rely on simple passwords, and many websites use passwords more for psychological than security purposes.

But the Georgia Tech research underscores the importance of getting people to adopt longer, non-simple passwords to make them safer against attack. "Length is a major factor in protecting against 'brute forcing' a password," according to one research scientist involved in the project, Joshua Davis. "A computer keyboard contains 95 characters, and every time you add another character, your protection goes up exponentially, by 95 times."

For the record, to defend against GPU attacks, the password researchers recommend using sentence-length passwords that mix letters with numbers or symbols, and which are at least 12 characters long.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
ANON1241631011972
50%
50%
ANON1241631011972,
User Rank: Apprentice
11/1/2011 | 6:35:42 PM
re: Passwords Quickly Hacked With PC Graphics Cards
I think this article overstates the capabilities and the use case does not generally exist in the real world. Passwords do not exist in a cyberspace vacuum, just waiting to be attacked in isolation. They exist in combination with a user identifier and a challenge/response system behind a UI. While the brute force methods may be capable of generating all the possible combinations, they still have to test them against a validation challenge with the correct response set. Most password challenge systems have two additional inhibitors against brute force attacks: 1. They don't respond at GPU speeds 2. They usually disable the account after 3 to 5 failed attempts. So, unless the brute force program has the password database available and the appropriate decode algorithms to provide the correct challenge/response patterns, it will not succeed. If the attacker has that kind of access, he or she is already past the firewall and well into the bowels of the network.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.