Cyber Resilience

CVE-2025-1445

Published
25 March 2025
Modified
15 April 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:A/V:X/RE:X/U:X
EPSS Score 0.0031 23th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2025-1445 is a high-severity Missing Synchronization (CWE-820) vulnerability in Hitachienergy (inferred from references). Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-1445 is a vulnerability in the RTU IEC 61850 client and server functionality on the RTU500 device, specifically affecting the CMU where the IEC61850 stack is configured using TLS. The flaw occurs when renegotiation of an open IEC61850 TLS connection takes place in specific timing situations during active IEC61850 communication, potentially impacting availability. It carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and maps to CWE-820.

Unauthenticated attackers with network access can exploit this vulnerability with low complexity and no user interaction. By initiating TLS renegotiation at precise timings while IEC61850 communication is active, they can disrupt service availability on the affected RTU500 device, resulting in a denial-of-service condition.

Mitigation guidance is available in the vendor advisory published by Hitachi Energy at https://publisher.hitachienergy.com/preview?DocumentId=8DBD000207&languageCode=en&Preview=true. The vulnerability was published on 2025-03-25.

EU & UK References

Vulnerability Data

A vulnerability exists in RTU IEC 61850 client and server functionality that could impact the availability if renegotiation of an open IEC61850 TLS connection takes place in specific timing situations, when IEC61850 communication is active. Precondition is that IEC61850 as…

more

client or server are configured using TLS on RTU500 device. It affects the CMU the IEC61850 stack is configured on.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22163Shared CWE-820
CVE-2025-47154Shared CWE-820
CVE-2025-49751Shared CWE-820
CVE-2024-49114Shared CWE-820
CVE-2026-57029Shared CWE-820
CVE-2026-70637Shared CWE-820
CVE-2025-47999Shared CWE-820
CVE-2026-53153Shared CWE-820
CVE-2026-44318Shared CWE-820
CVE-2026-53277Shared CWE-820

Affected Assets

Hitachienergy
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper concurrency controls and synchronization primitives during design and coding.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect missing synchronization through concurrency testing.

prevents

Secure SDLC practices can mandate concurrency controls and synchronization primitives.

prevents

Application security requirements can specify thread-safety and locking mechanisms.

prevents

Secure architecture principles include proper synchronization for shared resources.

prevents

Secure coding standards directly require synchronization primitives to prevent race conditions.

References