CyberSecBulletin
CVE-2023-4518NVD status: Modified

Relion670: Improper Validation of Specified Quantity in Input

CVE-2023-4518 is a high-severity improper validation of specified quantity in input vulnerability in Relion670 from Hitachi Energy, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Relion670 versions: Relion 670 series version 2.2.0 all revisions; Relion 670/650/SAM600-IO series version 2.2.1 all revisions; elion 670 series version 2.2.2 all revisions, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.7% chance of exploitation within 30 days, higher than 54% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Relion 670 Firmware to 2.2.2.6 or 2.2.3.7 or 2.2.4.4 or 2.2.5.6, whichever matches your release line, or a later version.
  2. Update Relion 650 Firmware to 2.2.4.4 or 2.2.5.6, whichever matches your release line, or a later version.
  3. Update Relion Sam600-io Firmware to 2.2.5.6 or a later version.
  4. Read the advisory on publisher.hitachienergy.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Hitachi EnergyRelion670Relion 670 series version 2.2.0 all revisions; Relion 670/650/SAM600-IO series version 2.2.1 all revisions; elion 670 series version 2.2.2 all revisions; Relion 670 series version 2.2.3 all revisions; Relion 670/650 series version 2.2.4 all revisions; Relion 670/650/SAM600-IO series version 2.2.5 all revisionsNot stated
HitachienergyRelion 670 Firmware2.2.0 up to, but not including, 2.2.2.6; 2.2.3 up to, but not including, 2.2.3.7; 2.2.4 up to, but not including, 2.2.4.4; 2.2.5 up to, but not including, 2.2.5.62.2.2.6, 2.2.3.7, 2.2.4.4, 2.2.5.6
HitachienergyRelion 650 Firmware2.2.4 up to, but not including, 2.2.4.4; 2.2.5 up to, but not including, 2.2.5.6; 2.2.1; 2.2.1.62.2.4.4, 2.2.5.6
HitachienergyRelion Sam600-io Firmware2.2.5 up to, but not including, 2.2.5.6; 2.2.1; 2.2.1.62.2.5.6

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.5MediumCNA (hitachienergy.com)
CVSS 3.17.5HighNVD

Official description

A vulnerability exists in the input validation of the GOOSE messages where out of range values received and processed by the IED caused a reboot of the device. In order for an attacker to exploit the vulnerability, goose receiving blocks need to be configured.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Validation of Specified Quantity in Input

The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

More Improper Validation of Specified Quantity in Input vulnerabilities (CWE-1284)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Improper Validation of Specified Quantity in Input vulnerabilities

Spotted an error? Tell us.