Security readout for executives and security teams
These GE Multilink industrial switches reused the same RSA private key across customer installations. If an attacker obtained that key from firmware and captured traffic, protected network communications could be exposed. The issue is critical because it undermines trust in encryption across affected deployments. Exposure is most likely in industrial or utility environments using listed GE Multilink switches on vulnerable firmware. Risk depends on whether the devices are deployed, whether sensitive traffic traverses them, and whether attackers can capture relevant network traffic. Treat as high priority for industrial networks that still run these legacy switches. The business concern is loss of confidentiality for traffic believed to be encrypted, especially in operational environments where device replacement may require planning. Mitigation focus: Confirm current GE and CISA advisory guidance for affected switch families.; Inventory ML800, ML1200, ML1600, and ML2400 devices at firmware 4.2.1 or earlier.; Inventory ML810, ML3000, and ML3100 devices at firmware 5.2.0 or earlier..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-321: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2014-5419 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:C/I:C/A:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:N/C:C/I:C/A:C1010Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
10CriticalVector: AV:N/AC:L/Au:N/C:C/I:C/A:C
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/news-events/ics-advisories/icsa-15-013-04aCVE reference
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2015/icsa-15-013-04a.jsonCVE reference
- https://ics-cert.us-cert.gov/advisories/ICSA-15-013-04CVE reference · x_refsource_MISC, x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Cryptographic Key
Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.