CVE-2023-4518

Device reboot via out-of-range GOOSE values

Published Dec 1, 2023 · Updated Sep 23, 2024

Improper input validation in Hitachi Energy Relion 670 series affected 2.2 firmware allows adjacent attackers to reboot the IED. GOOSE message processing accepts out-of-range values without enforcing the permitted quantity bounds, causing a reboot. Exploitation requires configured GOOSE receiving blocks and network access to deliver crafted GOOSE traffic; the reported consequence is a service interrupt.

CVSS severity6.5
Medium
EPSS probability0.70%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper input validation in Hitachi Energy Relion 670 series affected 2.2 firmware allows adjacent attackers to reboot the IED. GOOSE message processing accepts out-of-range values without enforcing the permitted quantity bounds, causing a reboot. Exploitation requires configured GOOSE receiving blocks and network access to deliver crafted GOOSE traffic; the reported consequence is a service interrupt.

The record

CVE
CVE-2023-4518
Published
Dec 1, 2023
Updated
Sep 23, 2024
Vendor
Hitachi Energy
Product
Relion 670 series
Classifications
CWE-1284, T0814
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 1, 2023CVE publishedPublication date reported by the CVE source.
  2. Sep 23, 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.

  1. Affected versionversion=elion 670 series version 2.2.2 all revisions
  2. Affected versionversion=Relion 670/650/SAM600-IO series version 2.2.1 all revisions
  3. Affected versionversion=Relion 670/650/SAM600-IO series version 2.2.5 all revisions
  4. Affected versionversion=Relion 670/650 series version 2.2.4 all revisions
  5. Affected versionversion=Relion 670 series version 2.2.0 all revisions
  6. Affected versionversion=Relion 670 series version 2.2.3 all revisions

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Hitachi Energy · Relion 670 seriesversion=elion 670 series version 2.2.2 all revisions; version=Relion 670/650/SAM600-IO series version 2.2.1 all revisions; version=Relion 670/650/SAM600-IO series version 2.2.5 all revisions; version=Relion 670/650 series version 2.2.4 all revisions; version=Relion 670 series version 2.2.0 all revisions; version=Relion 670 series version 2.2.3 all revisions

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
6.5Hitachi EnergyCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-1284Improper Validation of Specified Quantity in Input
T0814Denial of Service

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