CVE-2025-1718VulnerabilityPublished 24 Jun 2025Updated 25 Jun 2025

CVE-2025-1718: Hitachi Energy Relion 670/650 and SAM600-IO · Unchecked Error Condition

Affects Hitachi Energy Relion 670/650 and SAM600-IOSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Hitachi Energy Relion 670/650 and SAM600-IO	Affected =2.2.6.0 =2.2.5.0 =2.2.4.0 =2.2.3.0 =2.2.2.0 =2.2.1.0 =2.2.0.0 =2.1.0 =2.0.0 =1	Fixed in–

AI-suggested

1. Restrict FTP access strictly: Limit FTP access to trusted administrators and secure it using network segmentation and firewall rules to prevent unauthorized access. 2. Implement strong authentication and credential management: Enforce multi-factor authentication for all users with file access privileges and regularly rotate credentials to reduce the risk of compromise. 3. Monitor FTP logs and device behavior: Deploy continuous monitoring to detect unusual FTP activity or unexpected device reboots, enabling rapid incident response. 4. Apply vendor patches or updates promptly once available: Although no patches are currently linked, coordinate with Hitachi Energy for updates or workarounds. 5. Employ compensating controls: If patching is delayed, consider disabling FTP access if operationally feasible or replacing FTP with more secure protocols such as SFTP or FTPS. 6. Conduct regular security audits and vulnerability assessments on critical infrastructure devices to identify and remediate similar issues proactively. 7. Develop and test incident response plans specifically for device reboots and availability disruptions to minimize downtime and operational impact.

Description

An authenticated user with file access privilege via FTP access can cause the Relion 670/650 and SAM600-IO series device to reboot due to improper disk space management.

Impact

For European organizations, particularly those involved in energy production, transmission, and distribution, this vulnerability poses a significant risk to operational continuity. Relion 670/650 and SAM600-IO devices are integral to grid protection and automation, and unexpected reboots can cause temporary loss of monitoring and control capabilities. This can lead to delayed fault detection, potential equipment damage, and in worst cases, cascading failures affecting large portions of the electrical grid. The disruption could impact critical infrastructure, including hospitals, transportation, and industrial facilities, thereby affecting public safety and economic stability. Given the increasing focus on smart grids and digitalization in Europe, the availability of these devices is paramount. Attackers exploiting this vulnerability could cause denial-of-service conditions remotely, potentially as part of a broader attack campaign targeting energy infrastructure. The fact that exploitation requires only authenticated FTP access means that insider threats or compromised credentials could be leveraged to trigger the reboot, increasing the attack surface. The absence of known exploits in the wild suggests that proactive mitigation can prevent exploitation, but the high severity score underscores the urgency of addressing this vulnerability.

CWE-754Improper Check for Unusual or Exceptional Conditions (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Check the results of all functions that return a value and verify that the value is expected.
Implementation
If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

publisher.hitachienergy.com/preview?DocumentID=8DBD000174&LanguageCode=en&DocumentPartId=&Action=Launch (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Jun 2025, 11:54 UTC

WeaknessesCWE-754

Technical details

References

Community reviews

Related threats