dbcve.org
Microscada Pro Sys600Application · Hitachienergy

CVE-2022-3388

HIGH · 7.8 CVSS v3.1 Published 2022-11-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
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.

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 · moderate confidence

MicroSCADA Pro and MicroSCADA X SYS600 contain an input validation vulnerability in the Monitor Pro interface that allows any authenticated user to achieve administrator-level remote code execution, regardless of their assigned role. This is a privilege escalation issue where the authorization layer fails to properly validate the user's privilege level before permitting administrative operations.

MitigationImplement strict role-based access control (RBAC) enforcement and input validation in the Monitor Pro interface to ensure administrative functions can only be executed by users with administrator privileges. Validate all user inputs server-side before processing.

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
Microscada Pro Sys600Application
Affected:= 9.0= 9.1= 9.2= 9.3= 9.4
Microscada X Sys600Application
Affected:= 10= 10.1= 10.1.1= 10.2= 10.2.1= 10.3= 10.3.1= 10.4

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 installed MicroSCADA Pro version
    Check the installed software version through the Windows Programs and Features list, or look for version information in the application installation directory (commonly under C:\Program Files\Hitachi Energy\Microscada Pro\ or similar). Compare against affected versions 9.0 through 9.4.
    Affected if The installed version is 9.0, 9.1, 9.2, 9.3, or 9.4.
  2. Identify installed MicroSCADA X version
    Check the installed software version through the Windows Programs and Features list, or look for version information in the application installation directory (commonly under C:\Program Files\Hitachi Energy\Microscada X\ or similar). Compare against affected versions 10, 10.1, 10.1.1, 10.2, 10.2.1, 10.3, 10.3.1, or 10.4.
    Affected if The installed version is 10, 10.1, 10.1.1, 10.2, 10.2.1, 10.3, 10.3.1, or 10.4.
  3. Confirm Monitor Pro interface is configured
    Check if the Monitor Pro interface component is enabled in the MicroSCADA system configuration. This is typically found in the system configuration files or administration console under the interface or communication settings.
    Affected if The Monitor Pro interface is enabled and accessible.
  4. Review user role assignments
    Examine the user account configurations in the MicroSCADA user management system (typically via the System Administration or User Manager tool) to identify non-administrator users who have access to the Monitor Pro interface.
    Affected if Non-administrator users exist with access to Monitor Pro functionality.
  5. Verify administrative function access controls
    Test or inspect whether the Monitor Pro interface enforces proper privilege checks before allowing administrative operations. This may require reviewing system logs for failed authorization attempts or examining the RBAC configuration.
    Affected if The system permits non-administrator users to access administrative functions through the Monitor Pro interface.

A user is affected if they have MicroSCADA Pro version 9.0-9.4 or MicroSCADA X version 10-10.4 with the Monitor Pro interface enabled and non-administrator users can access it.

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

Implement strict role-based access control (RBAC) enforcement and input validation in the Monitor Pro interface to ensure administrative functions can only be executed by users with administrator privileges. Validate all user inputs server-side before processing.

Fix this in Microscada Pro Sys600 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3388 — 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-2022-3388 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