Traffic decryption via reused post-reset private key
Published Jan 12, 2021 · Updated Aug 4, 2024
Hard-coded cryptographic keys in Siemens SCALANCE X-200RNA before 3.2.7 and X-300 before 4.1.0 allow remote attackers to decrypt traffic. After a factory reset, affected devices retain a firmware-shipped private key instead of generating a unique replacement, exposing the associated TLS identity. An unauthenticated attacker positioned in a man-in-the-middle path can reuse the known key to decrypt previously captured communications; no device modification or service interruption is reported.
Summary
What happened
Hard-coded cryptographic keys in Siemens SCALANCE X-200RNA before 3.2.7 and X-300 before 4.1.0 allow remote attackers to decrypt traffic. After a factory reset, affected devices retain a firmware-shipped private key instead of generating a unique replacement, exposing the associated TLS identity. An unauthenticated attacker positioned in a man-in-the-middle path can reuse the known key to decrypt previously captured communications; no device modification or service interruption is reported.
The record
- CVE
- CVE-2020-28395
- Published
- Jan 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Siemens
- Product
- SCALANCE X-200RNA
- Classifications
- CWE-321, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions < V3.2.7
What conditions does exploitation require?
What is affected?
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.
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