theDocumentId => 1132781 How Not To Deploy SSL

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.

Risk

1/15/2010
04:05 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

How Not To Deploy SSL

The most common missteps that lead to SSL security problems

Last year was a rough one for Secure Sockets Layer (SSL), which was the focus of several high-profile hacks demonstrating its weaknesses, not to mention a protocol flaw resulting in an extension to the specification. But there are many mistakes organizations make when deploying SSL that leave them wide open to attack, according to an SSL expert.

Ivan Ristic, a researcher with SSL Labs and an author with Feisty Duck, says man-in-the-middle (MITM) attacks and other SSL vulnerabilities that were exposed are technical issues organizations can't really do much about. It's up to the vendors to fix those. "A much bigger problem is the thousands of Websites that have incorrectly deployed SSL," Ristic says.

In a presentation at the OWASP meeting in London yesterday, Ristic rattled off a laundry list of mistakes made with SSL that leave Websites and organizations vulnerable and render SSL useless. "The irony is that these are reasonably straightforward things to deploy [correctly]," he says. But people still incorrectly deploy SSL regularly, he says.

Ristic's list (PDF) includes self-signed SSL certificates, do-it-yourself certificate authorities (CAs), mixing SSL and plain text, not using secure cookies, using incomplete certificates, not using EV SSL, not using SSL at all, mixing page content (think plain-text link), poor Website management, only using SSL for some things in a site, and inconsistent DNS configuration.

Ristic says self-signed certificates can be found on some smaller Websites, and that some techies try serving as their own certificate authority for SSL, both of which are a no-no: A self-signed certificate is inherently insecure, and a homegrown CA can leave the CA root unprotected, he says.

Mixing SSL and plain text in a Website leaves the door open for a MITM attack, such as sslstrip to convert an HTTPS link to plain old HTTP, according to Ristic. And it's fairly common for Websites to not bother securing their cookies -- in other words, not transmitting them over SSL at all, which leaves them exposed.

And some sites don't even bother using SSL at all, he says. "If you don't have SSL, you don't have control over your real [brand] presence. It's the only thing that provides some form of authentication on the Internet," he says.

Ristic also warns that a single plain-text link on an SSL-secured Web page could compromise the entire site. And deploying SSL for only "important" things on the site, such as authentication, leaves the site exposed to session-hijacking, he says. "The assumption of many sites is that it's my credentials that are important. But it's not protecting the session: If someone hijacks it, he is able to be logged on as me and will be able to post [as me on a blogging site, for instance,'" he says.

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
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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-23412
PUBLISHED: 2021-07-23
All versions of package gitlogplus are vulnerable to Command Injection via the main functionality, as options attributes are appended to the command to be executed without sanitization.
CVE-2021-3159
PUBLISHED: 2021-07-23
A stored cross site scripting (XSS) vulnerability in the /sys/attachment/uploaderServlet component of Landray EKP V12.0.9.R.20160325 allows attackers to execute arbitrary web scripts or HTML via a crafted SVG, SHTML, or MHT file.
CVE-2021-25203
PUBLISHED: 2021-07-23
Arbitrary file upload vulnerability in Victor CMS v 1.0 allows attackers to execute arbitrary code via the file upload to \CMSsite-master\admin\includes\admin_add_post.php.
CVE-2021-25204
PUBLISHED: 2021-07-23
Cross-site scripting (XSS) vulnerability in SourceCodester E-Commerce Website v 1.0 allows remote attackers to inject arbitrary web script or HTM via the subject field to feedback_process.php.
CVE-2021-25206
PUBLISHED: 2021-07-23
Arbitrary file upload vulnerability in SourceCodester Responsive Ordering System v 1.0 allows attackers to execute arbitrary code via the file upload to Product_model.php.