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

7/30/2010
03:43 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Most SSL Sites Poorly Configured

Half of all SSL servers run older, insecure version of SSL; attacks against HTTPS browser sessions detailed at Black Hat

BLACK HAT USA -- Las Vegas -- The good news about SSL-based websites: Most are running strong encryption. The bad news: More than 60 percent aren't properly configured.

Click here for more of Dark Reading's Black Hat articles.

Researcher Ivan Ristic, who is director of engineering, Web application firewall, and SSL at Qualys, revealed findings here yesterday from a study he conducted of some 120 million registered domain names. Ristic found that 20 million of them support SSL, but only 720,000 of these have potentially valid SSL certificates. "That's a very small percentage, but it doesn't really mean anything apart from that a fraction of sites use SSL, which we've known," Ristic say.

Of the more telling findings was that of all the SSL sites, half use SSLv2, an older version of SSL, which is known to be insecure. Only 38 percent of all SSL sites are actually configured well, Ristic says, and 32 percent contain a previously exposed renegotiation vulnerability in the protocol.

Meanwhile, researchers Robert "RSnake" Hansen and Josh Sokol here yesterday detailed some 24 exploitation techniques possible against HTTPS/SSL for browsers that leverage man-in-the-middle (MITM) attacks. Among them: cookie poisoning and injecting malicious content into browser tabs. The researchers warned that HTTPS can't guarantee confidentiality and integrity in the browser.

"The sky is not falling ... but SSL is pretty frail right now," Hansen said in the presentation. "There needs to be proper tab isolation, cookie sandboxing, and proper padding and jitter, and a lot of this goes away," however, he says. Hansen recommends using a separate browser for sensitive browsing.

Ristic, meanwhile, says while the state of SSL websites is "average" in terms of security, SSL is rarely targeted by attackers today. "I have a disclaimer: SSL is not a common attack vector today because there's so much low-hanging fruit out there. I think it's the time to start fixing things, and they can be fixed."

Two-thirds of the SSL sites use default settings, which leave them open to attack. "To fix this, you have to raise awareness and reach end users or talk to the vendors and see if they can make the defaults better, which is probably the more feasible [solution]," Ristic says. Leaving default support for insecure protocols, for example, in SSL servers is one common mistake.

"To configure an SSL server well is a 15-minute job. You choose the key size for the cert, disable the insecure protocols, and disable the insecure ciphers."

And while the insecure SSLv2, which is susceptible to MITMattacks, has been disabled in most major browsers, Ristic says, it's still running many SSL websites. "The saddest thing was that more than half of all of them support SSL2. We've known that to be insecure for years."

There was little or no support in the more secure TLS 1.1 and 1.2 protocols in the SSL websites, he found.

But most SSL websites use strong encryption -- 128-bit and higher, the study found. Overall, Ristic says only 38.4 percent of SSL websites got an "A" for their security and configuration, while 61.46 percent got a B or lower. Ristic plans to go public with all of the data from the survey, and to run the survey on an annual basis.

Jeff Moss, founder of Black Hat, during the keynote here called SSL "broken" and said while some security problems have been addressed, it still has a ways to go.

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
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Zero Trust doesn't have to break your budget!
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-33347
PUBLISHED: 2021-06-18
An issue was discovered in JPress v3.3.0 and below. There are XSS vulnerabilities in the template module and tag management module. If you log in to the background by means of weak password, the storage XSS vulnerability can occur.
CVE-2021-33576
PUBLISHED: 2021-06-18
An issue was discovered in Cleo LexiCom 5.5.0.0. Within the AS2 message, the sender can specify a filename. This filename can include path-traversal characters, allowing the file to be written to an arbitrary location on disk.
CVE-2021-33577
PUBLISHED: 2021-06-18
An issue was discovered in Cleo LexiCom 5.5.0.0. The requirement for the sender of an AS2 message to identify themselves (via encryption and signing of the message) can be bypassed by changing the Content-Type of the message to text/plain.
CVE-2021-32536
PUBLISHED: 2021-06-18
The login page in the MCUsystem does not filter with special characters, which allows remote attackers can inject JavaScript without privilege and thus perform reflected XSS attacks.
CVE-2021-21669
PUBLISHED: 2021-06-18
Jenkins Generic Webhook Trigger Plugin 1.72 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.