Skip to content
Noroxi
NVD / CVE Program· CNA Hitachi Energy

CVE-2021-35534: Insufficient Security Control Vulnerability

Noroxi assessment

Priority: Monitor (action score 29/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.7% (FIRST EPSS); higher than 78.3% of all records.
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • According to the record, no fixed version is available yet.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.2 · v3.1—No exploit No fix recorded
Published
Nov 18, 2021
Updated
Jun 16, 2026
EPSS
1.7% · 78th percentile

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
28 / 40 · 7.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.7%

CNA vs NVD score

NVD
7.2
CNA · Hitachi Energy
7.2
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-35534

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for hitachienergy records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
hitachienergygms600 firmware
hitachienergygms600
hitachienergyrelion 670 firmware
hitachienergyrelion 670
hitachienergyrelion 650 firmware
hitachienergyrelion 650
hitachienergyrelion sam600-io firmware
hitachienergyrelion sam600-io
hitachienergypwc600 firmware
hitachienergypwc600

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • hitachienergy gms600 firmware1.2.0
  • hitachienergy gms600 firmware1.3.0
  • hitachienergy gms600 firmware1.3.1.0
  • hitachienergy pwc600 firmware1.0.1.0
  • hitachienergy pwc600 firmware1.0.1.1
  • hitachienergy pwc600 firmware1.0.1.3
  • hitachienergy pwc600 firmware1.0.1.4
  • hitachienergy pwc600 firmware1.1.0.0
  • hitachienergy pwc600 firmware1.1.0.1
  • hitachienergy relion 650 firmware1.0.0
  • hitachienergy relion 650 firmware1.1.0
  • hitachienergy relion 650 firmware1.2.0
  • hitachienergy relion 650 firmware1.3.0
  • hitachienergy relion 650 firmware2.1.0
  • hitachienergy relion 650 firmware2.2.0
  • hitachienergy relion 650 firmware2.2.1
  • hitachienergy relion 650 firmware2.2.4
  • hitachienergy relion 650 firmware2.2.5
  • hitachienergy relion 670 firmwareall versions
  • hitachienergy relion 670 firmware2.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Hitachi Energy). Independent of NVD's CPE analysis and usually ahead of it.

  • Hitachi Energy GMS600

    • 1.3.0, 1.3.1.0 1.3.0.1, 1.2.0affected

  • Hitachi Energy PWC600

    • 1.0.1 and later · up to and including 1.0.1.4affected
    • 1.1.0 and later · up to and including 1.1.0.1affected

  • Hitachi Energy Relion 650

    • 1.1 all revisions, 1.2 all revisions, 1.0 all revisionsaffected
    • 1.3 and later · before 1.3.0.8affected

  • Hitachi Energy Relion 670 Series

    • 2.0 all revisions, 2.2.2 all revisionsaffected
    • 2.2.3 and later · before 2.2.3.5affected

  • Hitachi Energy Relion 670/650 Series

    • 2.2.0 all revisions, 2.2.4 all revisions, 2.1 all revisionsaffected

  • Hitachi Energy Relion 670/650/SAM600-IO

    • 2.2.1 all revisionsaffected
    • 2.2.5 and later · before 2.2.5.2affected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-274 · Improper Handling of Insufficient Privileges

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records