CVE intelligence and bounded remediation

CVE-2021-35534 — Hitachienergy Gms600 Firmware security vulnerability

High CVSS 9

Insufficient security control vulnerability in internal database access mechanism of Hitachi Energy Relion 670/650/SAM600-IO, Relion 650, GMS600, PWC600 allows attacker who successfully exploited this vulnerability, of which the product does not sufficiently restrict access to an internal database tables, could allow anybody with user credentials to bypass security controls that is enforced by the product. Consequently, exploitation may lead to unauthorized modifications on data/firmware, and/or to permanently disabling the product. This issue affects: Hitachi Energy Relion 670 Series 2.0 all revisions; 2.2.2 all revisions; 2.2.3 versions prior to 2.2.3.5. Hitachi Energy Relion 670/650 Series 2.1 all revisions. 2.2.0 all revisions; 2.2.4 all revisions; Hitachi Energy Relion 670/650/SAM600-IO 2.2.1 all revisions; 2.2.5 versions prior to 2.2.5.2. Hitachi Energy Relion 650 1.0 all revisions. 1.1 all revisions; 1.2 all revisions; 1.3 versions prior to 1.3.0.8; Hitachi Energy GMS600 1.3.0; 1.3.0.1; 1.2.0. Hitachi Energy PWC600 1.0.1 version 1.0.1.4 and prior versions; 1.1.0 version 1.1.0.1 and prior versions.

Severity
High
CVSS
9 (2.0)
Published
2021-11-18
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-274, CWE-269

Affected products

  • hitachienergy / gms600_firmware / 1.2.0
  • hitachienergy / gms600_firmware / 1.3.0
  • hitachienergy / gms600_firmware / 1.3.1.0
  • hitachienergy / relion_670_firmware
  • hitachienergy / relion_670_firmware / 2.0.0
  • hitachienergy / relion_670_firmware / 2.1.0

Showing 6 representative product identities from 29 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Privilege escalation and unsafe privilege management

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map service accounts, operating-system identities, roles, capabilities, impersonation, set-user transitions, and administrative helper paths.
  • Determine whether untrusted users or lower-privilege processes can reach the affected transition or modify inputs it trusts.
  • Review file, socket, registry, device, job, container, and cloud-role permissions used before and after privilege changes.

Remediate safely

  • Apply the supported fix and redesign privileged operations as a minimal, authenticated, allowlisted interface.
  • Drop privileges before processing untrusted input, verify the drop succeeds, and remove unnecessary roles, capabilities, and write permissions.
  • Validate ownership and permissions at time of use and add explicit lower-to-higher privilege boundary tests.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.