Input Validation Vulnerability in Hitachi Energy’s MicroSCADA Pro/X SYS600 Products

published 2022-11-21 3y ago modified 2026-06-17 4mo ago also EUVD-2022-42766

cvss: 8.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

An input validation vulnerability exists in the Monitor Pro interface of MicroSCADA Pro and MicroSCADA X SYS600. An authenticated user can launch an administrator level remote code execution irrespective of the authenticated user's role.

Is CVE-2022-3388 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-333-03 updated 2023-11-09 cvss 8.8

Hitachi Energy MicroSCADA Pro/X SYS600 Products (Update A)

Hitachi Energy SYS600 9.x <=9.4_FP2_Hotfix_4 Hitachi Energy SYS600 10.x <=10.4
affected: vendor fix, mitigation “Hitachi Energy released the following recommended immediate actions:” publisher.hitachienergy.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Hitachi Energy MicroSCADA Pro SYS600
Hitachi Energy MicroSCADA X SYS600

Classification

Weakness

CWE-20 Improper Input Validation

References

search.abb.com /library/Download.aspx?DocumentID=8DBD000123&LanguageCode=en&DocumentPartId=&Action=Launch&elqaid=4293&elqat=1
vendor-advisory

Sources

CVE List CVE-2022-3388
NVD CVE-2022-3388

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.