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.

Vulnerabilities / Threats

10/25/2011
04:12 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Tool Lets Single Laptop Take Down An SSL Server

Yet another strike against SSL security

SSL is in the hot seat again: A new, free tool is now circulating that can take down an HTTPS Web server in a denial-of-service attack using a single laptop via a DSL connection.

Researchers with a hacker group called The Hackers Choice (THC) yesterday released the so-called THC-SSL-DOS tool that abuses the SSL renegotiation feature, which basically reperforms the encryption handshake.

The tool lets an attacker use a single connection to relentlessly perform the renegotiation with the SSL server, eventually overwhelming it. "It's a constant renegotiation. Instead of forming new connections over and over again ... it increases the overhead of the server," says Tyler Reguly, manager of security research and development with nCircle.

It all comes down to an SSL feature -- SSL renegotiation -- that isn't typically needed for Web servers. "Unless you wanted to change the encryption level, it's not a necessity. Some SSL VPNs make extensive use of it, but it's not needed in the Web browsing world," Reguly says.

The hackers who wrote the tool recommend disabling SSL renegotiation. But even that won't completely prevent such a denial-of-service attack. "It still works if SSL Renegotiation is not supported but requires some modifications and more bots before an effect can be seen," the THC hackers said in a statement.

For the tool to take down server farms with SSL load balancing, it requires using about 20 "average size" laptops and 120 Kbps of traffic, they said.

The new tool is reminiscent of the Slowloris attack tool that keeps connections open by sending partial HTTP requests and sends headers at regular intervals to prevent the sockets from closing, and OWASP's Slow HTTP Post tool. There's also the open-source slowhttptest tool that checks a server's vulnerability to a Slowloris-type attack.

nCircle's Reguly was initially skeptical of the attack, but downloaded the tool and gave it a spin. Much to his surprise, it worked well -- too well. "It definitely took down the server I tested it on. My laptop versus the HTTPS server was a success," he says. "It was kind of scary."

SSL has been under heavy scrutiny during the past couple of years for its vulnerability to man-in-the-middle attacks and for the high volume of SSL-based websites that are improperly configured. Some 80 percent, for example, are vulnerable to a Firesheep or similar attack, according to data from SSL Labs, Qualys' community project. And 70 percent of SSL servers handle credential login in plain text, while 55 percent submit passwords in plain text.

On top of that, there are this year's attacks of certificate authorities Comodo and DigiNotar, for instance. "We warned in 2002 about giving hundreds of commercial companies (so-called Certification Authorities) a master key to ALL SSL traffic," said Fred Mauer, a senior cryptographer at THC, in a post. "Only a real genius can come up with such an idea. And last but not least the immense complexity of SSL Renegotiation strikes again in 2011 with the release of THC-SSL-DOS. It’s time for a new security model that adequately protects the citizens."

THC also dismissed the idea of renegotiating encryption. "Renegotiating Key material is a stupid idea from a cryptography standpoint. If you are not happy with the key material negotiated at the start of the session then the session should be re-established and not re-negotiated," the group said.

The tool is available here for download.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. 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
AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4147
PUBLISHED: 2019-09-16
IBM Sterling File Gateway 2.2.0.0 through 6.0.1.0 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 158413.
CVE-2019-5481
PUBLISHED: 2019-09-16
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
CVE-2019-5482
PUBLISHED: 2019-09-16
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
CVE-2019-15741
PUBLISHED: 2019-09-16
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. An unsafe interaction with logrotate could result in a privilege escalation
CVE-2019-16370
PUBLISHED: 2019-09-16
The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.