From the /dev/ttyS0 blog post, Breaking SSL on Embedded Devices:
Here's where it gets fun: many of these devices use hard-coded SSL keys that are baked into the firmware. That means that if Alice and Bob are both using the same router with the same firmware version, then both of their routers have the same SSL keys. All Eve needs to do in order to decrypt their traffic is to download the firmware from the vendor's Web site and extract the SSL private key from the firmware image.
However, there are some practical limitations to this attack. If Eve doesn't know what router or firmware version Alice and Bob are using, it will be difficult to impossible for her to identify which firmware image to extract the SSL keys from. A good example of this is DD-WRT. There are several versions of DD-WRT available for each router supported by DD-WRT. And for each of those versions, there are several different "flavors": micro, standard, VPN, etc. Even if Eve knows that Alice and Bob are running DD-WRT, that's a lot of firmware images to work through. This becomes even more difficult when dealing with vendors whose firmware is not as standardized between releases.
That's where the LittleBlackBox project comes in. It contains a database of more than 2,000 private SSL keys that can be matched with the right hardware/firmware, and public certificates.
LittleBlackBox can be downloaded from here.
I'm not sure what admins or home users with affected routers are to do to protect themselves on this one, other than sloppy workarounds or find a different and unaffected router. I do know I'm quite tired of hard wired certificates and passwords embedded within devices.
For my security and technology observations throughout the day, find me on Twitter.