03:56 PM
George V. Hulme
George V. Hulme
Connect Directly

New SSL Attacks Don't Change Your Web Risk

There's been a a lot of talk about SSL security since last week's Black Hat conference. While these attacks are significant, I don't see them as changing the security posture of the Web.

There's been a a lot of talk about SSL security since last week's Black Hat conference. While these attacks are significant, I don't see them as changing the security posture of the Web.At the Black Hat security conference last week, Dan Kaminsky, director of penetration testing for IOActive pointed out, once again, that the X.509 certificates used in SSL encryption and authentication too often rely on vulnerable MD2 cryptographic hash functions. Also, security researcher Moxie Marlinspike revealed how attackers can spoof SSL certificates by including a "null" string character inside the certificate field, which then tricks the users' Web browser into accepting the attacker's code.

According to Marlinspike, it's not the SSL protocol that's the problem, it's how so many site implementations of SSL that are insecure. This includes many of the major banks, email systems, social networking sites, and more. Even most software update mechanisms.

One of the concerning aspects of Marlinspike's research, just isn't how banks, email systems, or social network sites are running vulnerable implementations of SSL -- it's that software update systems are doing the same. This needs to be a trusted process. As most users have their systems set for automatic updates, and if a malicious someone were able to spoof the connection then malware could be easily sent to the system, rather than a patch. The solution for this is simple: software makers need to digitally sign their updates.

When it comes to the weak X.509 certificates we've known about this for some time, and the industry is moving away from MD2 hashes.

Second, regarding Marlinspike, one needs to understand that SSL merely creates the secure tunnel between your system and whatever web site you're interacting - and does nothing for the security of your end point or the Web site itself. That means most any SSL attack that would result from this flaw would be a man-in-the middle attack where the bad guy would capture traffic flowing between your PC and the Web site.

Unfortunately, the Web sites you're connecting to are already wide open and vulnerable, and has been pointed out many times. Same is true for most end user systems. It's just easier to drop malware on Web sites that will infect systems, and then capture that data, or infect end points directly -- than it is to conduct man-in-the-middle attacks. So, while interesting, and serious, and a hole that needs to be plugged, it's simply another hole in the hull of a ship already taking considerable water.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2014-08-30
Cisco Intelligent Automation for Cloud (aka Cisco Cloud Portal) 2008.3_SP9 and earlier does not properly consider whether a session is a problematic NULL session, which allows remote attackers to obtain sensitive information via crafted packets, related to an "iFrame vulnerability," aka Bug ID CSCuh...

Published: 2014-08-30
The Amazon.com Kindle application before 4.5.0 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

Published: 2014-08-29
DCTStream.cc in Poppler before 0.13.3 allows remote attackers to cause a denial of service (crash) via a crafted PDF file.

Published: 2014-08-29
Cross-site scripting (XSS) vulnerability in Six Apart (formerly Six Apart KK) Movable Type (MT) Pro 5.13 allows remote attackers to inject arbitrary web script or HTML via the comment section.

Published: 2014-08-29
Monitoring Agent for UNIX Logs 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP09, and 6.2.3 through FP04 and Monitoring Server (ms) and Shared Libraries (ax) 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP08, 6.2.3 through FP01, and 6.3.0 through FP01 in IBM Tivoli Monitoring (ITM)...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.