Private-key compromise via low boot-time entropy
Published Feb 28, 2020 · Updated Sep 16, 2024
Insufficient entropy in Juniper Junos on QFX3500 and QFX3600 switches allows remote authenticated users to compromise SSH or TLS private keys. At boot, the RANDOM_INTERRUPT source contributes too few bytes before Junos generates SSH host keys or self-signed TLS certificates. Exposure is limited to credentials generated immediately after boot, enabling confidentiality loss without data alteration or service interruption.
Summary
What happened
Insufficient entropy in Juniper Junos on QFX3500 and QFX3600 switches allows remote authenticated users to compromise SSH or TLS private keys. At boot, the RANDOM_INTERRUPT source contributes too few bytes before Junos generates SSH host keys or self-signed TLS certificates. Exposure is limited to credentials generated immediately after boot, enabling confidentiality loss without data alteration or service interruption.
The record
- CVE
- CVE-2015-3006
- Published
- Feb 28, 2020
- Updated
- Sep 16, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-331
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 28, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo