rapid7/ssh-badkeys

A collection of static SSH keys (public and private) that have made their way into software and hardware products.

SSH Bad Keys

This is a collection of static SSH keys (host and authentication) that have made their way into software and hardware products. This was inspired by the Little Black Box project, but focused primarily on SSH (as opposed to TLS) keys.

Keys are split into two categories; authorized keys and host keys. The authorized keys can be used to gain access to a device with this public key. The host keys can be used to conduct a MITM attack against the device, but do not provide direct access.

This collection depends on submissions from researchers to stay relevant. If you are aware of a static key (host or authorized), please open an Issue or submit a Pull Request. The Issues list also contains a wishlist of known bad keys that we would like to include.

For additional key types and a broader scope, take a look at the Kompromat project.

ssh-badkeys's Issues

Add Lancom default SSH hostkeys

SSH
 ssh-dss 27:c5:1d:9f:be:27:3d:50:d7:bf:c1:68:0b:18:97:d7
 ssh-rsa 03:56:e6:52:ee:d2:da:f0:73:b5:df:3d:09:08:54:b7

http://www.lancom-systems.de/download/documentation/Reference_Manual/LCOS-ADDENDUM-884-DE.pdf

Add Cisco Virtual WSA, ESA, and SMA authorized keys

See http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20150625-ironport

Add Barracuda Load Balancer ADC key for the cluster user

http://seclists.org/fulldisclosure/2015/Jan/76

Invalid keys?

While doing some quick research I happened to notice that two keys in this repository may be malformed in one way or another:

$  find . -name \*.pub | parallel --gnu "ssh-keygen -E md5 -lf {} > /dev/null"            
./authorized/exagrid-cve-2016-1561.pub is not a public key file.
./authorized/f5-bigip-cve-2012-1493.pub is not a public key file.

Could be a PEBKAC too.

Passwords

Some bad keys have passwords. Do we have a preferred format/method for storing these alongside the key?

DDN Default SSH Keys

https://labs.mwrinfosecurity.com/advisories/ddn-default-ssh-keys/

Comcast/Shaw 1039-bit RSA: e7:86:c7:22:b3:08:af:c7:11:fb:a5:ff:9a:ae:38:e4

SSH 1039-bit RSA e7:86:c7:22:b3:08:af:c7:11:fb:a5:ff:9a:ae:38:e4
SSH 1024-bit DSS b6:b9:6c:8b:4c:11:72:81:b1:f7:83:27:91:d6:81:fc

Add FortiSIEM default SSH key for the "tunneluser" account

See https://fortiguard.com/psirt/FG-IR-19-296

add the vagrant default key's

you can download them here:
https://github.com/mitchellh/vagrant/tree/master/keys

Debian keys?

Originally @hmoore-r7 cataloged a variety of weak Debian keys on DigitalOffense.net (link is now dead). However a mirror remains in another Github repository here: g0tmi1k/debian-ssh. No license currently exists on g0tmi1k's repository besides a copyright notice for HD Moore's original contribution, so I think it should be fine to merge keys from that repo into this one. My thought being that private keys from that repo could be use to gain access to known authorized keys.

Thoughts?

"House of Keys" Embedded systems - SSL/SSH

GitHub: https://github.com/sec-consult/houseofkeys

Blog: http://blog.sec-consult.com/2015/11/house-of-keys-industry-wide-https.html

Blog: http://blog.sec-consult.com/2016/09/house-of-keys-9-months-later-40-worse.html

Add Kali RPI keys

http://docs.kali.org/armel-armhf/install-kali-linux-arm-raspberry-pi

IMPORTANT Please change your ssh host keys as soon as possible as ALL rpi images have the same keys.