LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25193: GE Reason RT43X Clocks Use of Hard-coded Cryptographic Key

By having access to the hard-coded cryptographic key for GE Reason RT430, RT431 & RT434 GNSS clocks in firmware versions prior to version 08A06, attackers would be able to intercept and decrypt encrypted traffic through an HTTPS connection.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects GE Reason RT430, RT431, and RT434 GNSS clocks running firmware before 08A06. A hard-coded cryptographic key could let an attacker decrypt encrypted HTTPS traffic, exposing information sent to or from the clock. The published impact is confidentiality only, not system takeover or outage.

Executive priority

Treat as a targeted operational technology confidentiality issue. Prioritize environments where GNSS clocks support critical timing functions or where management traffic is observable beyond trusted administrators. It is not KEV-listed in the provided bundle, so urgency should be risk-based rather than emergency-driven.

Technical view

CVE-2020-25193 is CWE-321: use of a hard-coded cryptographic key. For affected GE Reason RT43X firmware before 08A06, access to that key could allow interception and decryption of HTTPS traffic. CVSS 3.1 is 5.3, network exploitable, low complexity, no privileges, no user interaction, confidentiality impact low.

Likely exposure

Exposure is most likely in organizations operating GE Reason RT430, RT431, or RT434 GNSS clocks, especially where management or HTTPS traffic crosses networks that untrusted parties could observe. The bundle does not identify other affected GE products or CPEs.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation. The risk is traffic confidentiality loss if an attacker can access the hard-coded key and observe relevant HTTPS communications.

Researcher notes

The evidence is narrow but consistent: affected products are GE Reason RT430, RT431, and RT434 GNSS clocks before firmware 08A06. The stated outcome is HTTPS traffic decryption, with no integrity or availability impact in the supplied CVSS vector. No exploit details should be assumed from this bundle.

Mitigation direction

  • Inventory GE Reason RT430, RT431, and RT434 GNSS clocks.
  • Confirm firmware versions and identify systems before 08A06.
  • Upgrade affected clocks to firmware 08A06 or later per GE guidance.
  • Review the CISA ICS advisory and GE bulletin for operational guidance.
  • Limit management access to trusted administrative networks.

Validation and detection

  • Verify each RT43X model and firmware version from asset records or device administration.
  • Confirm no RT430, RT431, or RT434 remains below firmware 08A06.
  • Check whether HTTPS management traffic traverses shared or untrusted networks.
  • Confirm compensating access controls around clock management interfaces.
  • Document remediation status for all identified affected clocks.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2020-25193 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2020-25193Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GEReason RT43X ClocksunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-321 · source CWE mapping

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.