dbcve.org
Gms600 FirmwareOperating system · Hitachienergy

CVE-2021-35534

HIGH · 7.2 CVSS v3.1 Published 2021-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Relion 670/650, SAM600-IO, GMS600, and PWC600 products contain an insufficient security control in their internal database access mechanism. The products do not adequately restrict access to internal database tables, allowing any authenticated user to bypass security controls enforced by the product. This broken access control enables unauthorized modifications to data/firmware or permanent disabling of the device.

MitigationApply vendor-supplied patches (Relion 670 2.2.3.5+, 2.2.5.2+; Relion 650 1.3.0.8+; PWC600 1.0.1.5+, 1.1.0.2+). If patching is not immediately feasible, implement compensating controls including network segmentation to limit exposure, strict access control lists, and monitoring for unauthorized database access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gms600 FirmwareOperating system
Affected:= 1.2.0= 1.3.0= 1.3.1.0
Relion 670 FirmwareOperating system
Affected:all versions= 2.0.0= 2.1.0= 2.2.0= 2.2.1= 2.2.2= 2.2.3= 2.2.4= 2.2.5
Relion 650 FirmwareOperating system
Affected:= 1.0.0= 1.1.0= 1.2.0= 1.3.0= 2.1.0= 2.2.0= 2.2.1= 2.2.4= 2.2.5
Relion Sam600 Io FirmwareOperating system
Affected:= 2.2.1= 2.2.5
Pwc600 FirmwareOperating system
Affected:= 1.0.1.0= 1.0.1.1= 1.0.1.3= 1.0.1.4= 1.1.0.0= 1.1.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the product model
    Access the device web interface or system information page to determine the exact product model (Gms600, Relion 670, Relion 650, Sam600 Io, or PWC600)
    Affected if The product is any of the five affected models listed in the CVE
  2. Locate the firmware version
    Navigate to the device settings, about page, or system status section in the web interface to find the installed firmware version
    Affected if The firmware version cannot be determined or is not visible
  3. Compare firmware version against affected Relion 670 versions
    If the product is Relion 670, note that ALL versions are affected per the CVE
    Affected if The product is Relion 670 with any firmware version
  4. Compare firmware version against affected Relion 650 versions
    If the product is Relion 650, compare your version against: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 2.1.0, 2.2.0, 2.2.1, 2.2.4, 2.2.5
    Affected if The installed version matches one of these listed versions
  5. Compare firmware version against affected Gms600, Sam600 Io, or PWC600 versions
    For Gms600 check versions 1.2.0, 1.3.0, 1.3.1.0; for Sam600 Io check 2.2.1, 2.2.5; for PWC600 check 1.0.1.0, 1.0.1.1, 1.0.1.3, 1.0.1.4, 1.1.0.0, 1.1.0.1
    Affected if The installed version matches one of these listed versions

If the product is any of the five affected models and the firmware version matches the specific versions listed (or any version for Relion 670), the environment is affected by this broken access control vulnerability in the internal database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches (Relion 670 2.2.3.5+, 2.2.5.2+; Relion 650 1.3.0.8+; PWC600 1.0.1.5+, 1.1.0.2+). If patching is not immediately feasible, implement compensating controls including network segmentation to limit exposure, strict access control lists, and monitoring for unauthorized database access attempts.

Fix this in Gms600 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-35534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-35534 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data