dbcve.org
Microscada X Sys600Application · Hitachienergy

CVE-2022-29922

HIGH · 7.5 CVSS v3.1 Published 2022-09-14
Fix available
A fix is available. Upgrade to 10.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Input Validation vulnerability in the handling of a specially crafted IEC 61850 packet with a valid data item but with incorrect data type in the IEC 61850 OPC Server in the Hitachi Energy MicroSCADA X SYS600, MicroSCADA Pro SYS600. The vulnerability may cause a denial-of-service on the IEC 61850 OPC Server part of the SYS600 product. This issue affects: Hitachi Energy MicroSCADA Pro SYS600 version 9.4 FP2 Hotfix 4 and earlier versions Hitachi Energy MicroSCADA X SYS600 version 10 to version 10.3.1. cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.0:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.1:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.2:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.3:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.4:*:*:*:*:*:*:* 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 input validation in the IEC 61850 OPC Server allows specially crafted IEC 61850 packets with valid data items but incorrect data types to cause a denial-of-service condition. The vulnerability stems from the server not validating that the data type matches what is expected before processing the packet data.

MitigationApply vendor patches for MicroSCADA Pro SYS600 (9.4 FP2 Hotfix 4 and later) and MicroSCADA X SYS600 (10.3.2 and later). Until patched, consider network segmentation to limit exposure to untrusted IEC 61850 traffic.

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:>= 9.0, < 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm MicroSCADA X SYS600 is installed
    Locate the installation directory or check system inventory for Hitachi Energy MicroSCADA X SYS600 software
    Affected if The software is not present on the system, then the CVE does not apply
  2. Identify the installed version
    Check the installed version of MicroSCADA X SYS600 - this is typically found in the software itself, installation logs, or version information accessible through the product's about or system information interface
    Affected if The installed version is 9.0 through 10.3.x (specifically < 10.4)
  3. Verify IEC 61850 OPC Server is enabled
    Check the MicroSCADA X SYS600 configuration for IEC 61850 server or OPC server settings - this is typically configured in the system's communication or protocol configuration files
    Affected if IEC 61850 OPC Server functionality is enabled and processing IEC 61850 protocol traffic
  4. Inspect for crash or DoS indicators
    Review system logs, event logs, and application logs for unexpected crashes, restarts, or error messages related to IEC 61850 packet processing
    Affected if Recent crashes or denial-of-service events have occurred involving the IEC 61850 server component

A user is affected if Hitachi Energy MicroSCADA X SYS600 versions 9.0 through 10.3.x are installed with IEC 61850 OPC Server enabled and processing network traffic.

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.

dbcve · scoped
Upgrade available Upgrade to 10.4 or later
Fixed in 10.4
Interim mitigation

Apply vendor patches for MicroSCADA Pro SYS600 (9.4 FP2 Hotfix 4 and later) and MicroSCADA X SYS600 (10.3.2 and later). Until patched, consider network segmentation to limit exposure to untrusted IEC 61850 traffic.

Recommended fix Moderate confidence

MicroSCADA X SYS600: upgrade to version 10.4 or later; MicroSCADA Pro SYS600: contact vendor for fixed version

  1. Identify the specific MicroSCADA X SYS600 or MicroSCADA Pro SYS600 version currently installed
  2. For MicroSCADA X SYS600: Upgrade to version 10.4 or later
  3. For MicroSCADA Pro SYS600: Contact Hitachi Energy for specific fixed version (9.4 FP2 Hotfix 5 or later)
  4. After upgrade, verify the IEC 61850 OPC Server service is running correctly
  5. Test IEC 61850 communications to confirm normal operation
Caveat Upgrade to major version 10.x may require testing of existing IEC 61850 configurations and integrations

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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