lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 19 Dec 2010 18:10:27 +0000
From: "Thor (Hammer of God)" <thor@...merofgod.com>
To: Craig Heffner <cheffner@...ttys0.com>
Cc: "full-disclosure@...ts.grok.org.uk" <full-disclosure@...ts.grok.org.uk>
Subject: Re: Default SSL Keys in Multiple Routers

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@...ts.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@...merofgod.com<mailto:thor@...merofgod.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@...ts.grok.org.uk<mailto:full-disclosure@...ts.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/.



Content of type "text/html" skipped

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ