Study of 4000 embedded devices from over 70 vendors shows reused crypto keys leave millions of devices insecure, only 5 vendors known to have fixes on the way
‘Worrying’ 9 Per Cent Of Encrypted Web Vulnerable To Private Key Attacks — Getting encryption right can be hard.
Context & Ripple Effects
This study lands at the start of a decade-long pattern: researchers scanning real devices and finding the same cryptographic hygiene failure everywhere they look. Within a year, the same class of flaw was quantified at scale — over 4.5M network appliances, IoT devices, and embedded systems reusing known private keys for HTTPS and SSH servers — confirming the problem was structural, not a one-off vendor lapse.
What makes the original finding durable is how little changed afterward. By 2023, researchers showed that large portions of SSH keys protecting computer-to-server traffic remain vulnerable to complete compromise, and open-source TCP/IP stacks in millions of devices were still shipping the Amnesia:33 vulnerabilities. Key reuse is not an edge case; it is the default failure mode of low-cost embedded engineering.
First-order effects
- Owners of affected routers, appliances, and IoT gear face active exposure: an attacker who extracts one device's private key can decrypt or impersonate traffic across every other device sharing it, and only five vendors have confirmed fixes in progress.
- The remaining 70-plus vendors named in the study must now decide whether to ship firmware updates for hardware that was likely sold as set-and-forget — a cost many consumer-embedded vendors have historically avoided.
Second-order effects
- Enterprises buying network equipment gain a new procurement criterion — per-device unique key generation at first boot — shifting pressure onto vendors whose supply chains stamp identical keys into identical units.
- Certificate authorities and hosting providers face collateral trust damage: when 9% of the encrypted web can be compromised via private-key reuse, relying parties must weigh revocation and reissuance against keys they cannot verify are unique.
Third-order effects
- If the pattern holds — from this 2015 study through Amnesia:33 and the 2023 SSH findings — embedded security becomes a lifecycle-liability question for regulators and insurers, since devices shipped with shared secrets cannot be patched retroactively at scale.
- Vendors that industrialize unique-key provisioning and signed firmware updates convert a compliance burden into a differentiator, consolidating the market around suppliers who treat cryptography as infrastructure rather than a checkbox.
The trend: Embedded and IoT security research keeps converging on the same root cause — weak key management baked into cheap hardware — pushing the industry toward provisioning and update practices that make cryptographic uniqueness mandatory rather than optional.