Vulnerabilities / Threats
7/30/2010
03:43 PM
Connect Directly
Google+
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 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
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6306
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

CVE-2014-0232
Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

CVE-2014-3525
Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server 4.2.1.1 and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

CVE-2014-3563
Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

CVE-2014-3587
Published: 2014-08-22
Integer overflow in the cdf_read_property_info function in cdf.c in file through 5.19, as used in the Fileinfo component in PHP before 5.4.32 and 5.5.x before 5.5.16, allows remote attackers to cause a denial of service (application crash) via a crafted CDF file. NOTE: this vulnerability exists bec...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.