Vulnerability Note VU#566724
Embedded devices use non-unique X.509 certificates and SSH host keys
Original Release date: 25 Nov 2015 | Last revised: 17 Dec 2015
Embedded devices use non-unique X.509 certificates and SSH host keys that can be leveraged in impersonation, man-in-the-middle, or passive decryption attacks.
CWE-321: Use of Hard-coded Cryptographic Key – Multiple CVEs
Research by Stefan Viehböck of SEC Consult has found that numerous embedded devices accessible on the public Internet use non-unique X.509 certificates and SSH host keys. Products are identified as vulnerable if unpacked firmware images are found to contain hard-coded keys or certificates whose fingerprints can be matched to data from the Internet-wide scan data repository, scans.io (specifically, see SSH results and SSL certificates). Affected devices range broadly from home routers and IP cameras to VOIP phones.
For the majority of vulnerable devices, reuse of certificates and keys are limited to the product lines of individual vendors. There are some instances where identical certificates and keys are used by multiple vendors. In these cases, the root cause may be due to firmware that is developed from common SDKs, or OEM devices using ISP-provided firmware.
Vulnerable devices may be subject to impersonation, man-in-the-middle, or passive decryption attacks. It may be possible for an attacker to obtain credentials or other sensitive information that may be used in further attacks. For additional details about the research and affected products by certificates and SSH host keys, refer to SEC Consult blog post on the topic.
A remote, unauthenticated attacker may be able to carry out impersonation, man-in-the-middle, or passive decryption attacks, resulting in sensitive information exposure.
In most cases, the CERT/CC is unaware of a practical solution to this problem. Some vendors have indicated that updates or guidance will be provided, and this information will be updated within individual vendor information pages below when known. Users are encouraged to contact device vendors for more information.
Change X.509 certificates or SSH host keys
Where possible, users of affected devices should manually replace X.509 certificates or SSH host keys so that they are unique to the device.
As a general good security practice, only allow connections from trusted hosts and networks. Note that restricting access does not prevent a capable attacker from intercepting and decrypting vulnerable communications, but it may limit an attacker’s ability to make use of compromised credentials from an untrusted host.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedActiontecAffected24 Sep 201524 Nov 2015
CiscoAffected24 Sep 201501 Dec 2015
D-Link Systems, Inc.Affected24 Sep 201501 Dec 2015
Huawei TechnologiesAffected24 Sep 201524 Nov 2015
NetComm Wireless LimitedAffected24 Sep 201524 Nov 2015
Sierra WirelessAffected24 Sep 201501 Dec 2015
TechnicolorAffected24 Sep 201512 Nov 2015
Ubiquiti NetworksAffected24 Sep 201524 Nov 2015
Unify IncAffected25 Sep 201501 Dec 2015
ZTE CorporationAffected24 Sep 201505 Nov 2015
ZyXELAffected24 Sep 201501 Dec 2015
General ElectricNot Affected24 Sep 201517 Dec 2015
ADBUnknown20 Nov 201525 Nov 2015
ADTRANUnknown20 Nov 201525 Nov 2015
Alcatel-LucentUnknown24 Sep 201524 Sep 2015If you are a vendor and your product is affected, let
us know.View More »
CVSS Metrics (Learn More)
Thanks to Stefan Viehböck of SEC Consult for reporting this vulnerability.
This document was written by Joel Land.
25 Nov 2015
Date First Published:
25 Nov 2015
Date Last Updated:
17 Dec 2015
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.