Re: Default SSL Keys in Multiple Routers

["Thor (Hammer of God)" <thor () hammerofgod com>]

Quite interesting.  It was one of those those things I just assumed was part of the build process. Thanks for the app 
and info.
t


Sent from my Windows Phone emulator.
________________________________
From: Craig Heffner
Sent: Sunday, December 19, 2010 10:03 AM
To: Thor (Hammer of God)
Cc: full-disclosure () lists grok org uk
Subject: Re: [Full-disclosure] Default SSL Keys in Multiple Routers

> From a security standpoint, it is. But it's easier and probably more cost effective for the manufacturer.

Sometimes the key will be different between firmware versions, sometimes it won't. Sometimes the same key will be used 
for two different models. It just depends. Some models don't have hard coded keys, but most of the consumer grade stuff 
(and even some of the low-end business stuff) does.

- Craig

On Sun, Dec 19, 2010 at 12:17 PM, Thor (Hammer of God) <thor () hammerofgod com<mailto:thor () hammerofgod com>> wrote:
These manufacturers use the same key on each of their models?  That seems ridiculous to me...
T
________________________________
From: Craig Heffner
Sent: Sunday, December 19, 2010 5:56 AM
To: full-disclosure () lists grok org uk<mailto:full-disclosure () lists grok org uk>
Subject: [Full-disclosure] Default SSL Keys in Multiple Routers


Many routers that provide an HTTPS administrative interface use default or hard-coded SSL keys that can be recovered by 
extracting the file system from the device's firmware.

The LittleBlackBox project contains a database of over 2,000 (and growing) private SSL keys that are correlated with 
their respective public certificates, and hardware/firmware versions. While most of these certificates are from DD-WRT 
firmware, there are also private keys from other vendors including Cisco, Linksys, D-Link and Netgear.

Private keys can be recovered by supplying LittleBlackBox with the corresponding public key. If the public key is not 
readily available, LittleBlackBox can retrieve the public certificate from a pcap file, live traffic capture, or by 
directly querying the target host.

LittleBlackBox can be downloaded from http://littleblackbox.googlecode.com.

More information is available at http://www.devttys0.com/2010/12/breaking-ssl-on-embedded-devices/.


_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/