dbcve.org
Microscada X Sys600Application · Hitachienergy

CVE-2022-29490

HIGH · 8.8 CVSS v3.1 Published 2022-09-12
Fix available
A fix is available. Upgrade to after 10.3.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Authorization vulnerability exists in the Workplace X WebUI of the Hitachi Energy MicroSCADA X SYS600 allows an authenticated user to execute any MicroSCADA internal scripts irrespective of the authenticated user's role. This issue affects: Hitachi Energy MicroSCADA X SYS600 version 10 to version 10.3.1. cpe:2.3:a:hitachienergy:microscada_x_sys600:10:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.1:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.1.1:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.2:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.2.1:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.3:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.3.1:*:*:*:*:*:*:*

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

Improper authorization vulnerability in the Workplace X WebUI of Hitachi Energy MicroSCADA X SYS600 allows any authenticated user to execute MicroSCADA internal scripts regardless of their assigned role. This is a vertical privilege escalation where low-privilege users can bypass role-based access controls to run privileged internal scripts.

MitigationImplement and enforce proper role-based authorization checks in the WebUI before allowing execution of internal scripts. Validate user role permissions against the specific script being requested.

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 X Sys600Application
Affected:>= 10.0, <= 10.3.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 X version
    Locate the SYS600 installation directory and check the product version information, typically found in the product's about or version dialog within the WebUI, or check system files that contain version metadata
    Affected if The installed version is between 10.0 and 10.3.1 inclusive
  2. Confirm WebUI is accessible
    Verify that the Workplace X WebUI interface is enabled and reachable by accessing the web interface URL for the SYS600 system
    Affected if The WebUI is accessible without additional configuration requirements being met
  3. Review user role assignments
    Check the user management section of the WebUI to see what roles are assigned to different users in the system
    Affected if Users exist with different privilege levels (such as operator versus administrator roles)
  4. Test internal script access with low-privilege account
    Using a user account that has limited or operator-level privileges, attempt to access or execute internal MicroSCADA scripts through the WebUI interface
    Affected if A low-privilege user can successfully invoke internal scripts that should be restricted to higher-privilege roles
  5. Verify authorization configuration
    Examine the WebUI configuration files or settings that control role-based access to internal scripts and script execution privileges
    Affected if The authorization configuration either allows all authenticated users to run internal scripts or lacks role-based restrictions on script execution

A system is affected if it runs MicroSCADA X SYS600 version 10.0 through 10.3.1, has the WebUI enabled, and permits authenticated users with limited roles to execute internal privileged scripts without proper role verification.

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
Upgrade available Upgrade to a release after 10.3.1
Interim mitigation

Implement and enforce proper role-based authorization checks in the WebUI before allowing execution of internal scripts. Validate user role permissions against the specific script being requested.

Fix this in Microscada X Sys600 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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