Sys600 FirmwareOperating system · Hitachienergy

CVE-2022-3353

HIGH · 7.5 CVSS v3.1 Published 2023-02-21
Fix available
A fix is available. Upgrade to 8.3.3 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
A vulnerability exists in the IEC 61850 communication stack that affects multiple Hitachi Energy products.  An attacker could exploit the vulnerability by using a specially crafted message sequence, to force the IEC 61850 MMS-server communication stack, to stop accepting new MMS-client connections.  Already existing/established client-server connections are not affected. List of affected CPEs: * cpe:2.3:o:hitachienergy:fox61x_tego1:r15b08:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r2a16_3:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r2a16:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r1e01:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r1d02:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r1c07:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:fox61x_tego1:r1b02:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:gms600:1.3.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.5.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.2:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.8.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.4:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.5:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.*:*:*:*:*:*:*:* * 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:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.4:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:microscada_x_sys600:10.4.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:mms:2.2.3:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:pwc600:1.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:pwc600:1.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:pwc600:1.2:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:reb500:7:*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:reb500:8:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion670:1.2.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion670:2.0.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion650:1.1.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion650:1.3.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion650:2.1.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion670:2.1.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relionSAM600-IO:2.2.1:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relionSAM600-IO:2.2.5:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion670:2.2.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:relion650:2.2.*:*:*:*:*:*:*:* * cpe:2.3:o:hitachienergy:rtu500cmu:12.*.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:rtu500cmu:13.*.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:txpert_hub_coretec_4:2.*:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:txpert_hub_coretec_4:3.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:txpert_hub_coretec_5:3.0:*:*:*:*:*:*:*

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

A denial-of-service vulnerability exists in the IEC 61850 MMS-server communication stack used across multiple Hitachi Energy products. An attacker can send specially crafted message sequences to cause the MMS server to stop accepting new client connections. Existing established connections remain unaffected. This is a protocol-level DoS that requires crafted messages rather than simple traffic flooding.

MitigationApply vendor-provided patches or firmware updates from Hitachi Energy for all affected products. Since this is a protocol stack vulnerability, network-level mitigations alone may be insufficient; vendor patches addressing the MMS server logic are required.

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
Sys600 FirmwareOperating system
Affected:>= 10.1, <= 10.3.1
Rtu500 FirmwareOperating system
Affected:>= 12.0.1.0, <= 12.0.14.0>= 12.2.1.0, <= 12.2.11.0>= 12.4.1.0, <= 12.4.11.0>= 12.6.1.0, <= 12.6.8.0>= 12.7.1.0, <= 12.7.4.0>= 13.2.1.0, <= 13.2.5.0>= 13.3.1, <= 13.3.3= 13.4.1
Reb500 FirmwareOperating system
Affected:>= 7.0, < 8.3.3
Pwc600 FirmwareOperating system
Affected:= 1.0= 1.1= 1.2
Modular Switchgear Monitoring FirmwareOperating system
Affected:<= 2.2.3
Itt600 Sa ExplorerApplication
Affected:= 1.1.0= 1.1.1= 1.1.2= 1.5.0= 1.5.1= 1.6.0= 1.6.0.1= 1.7.0= 1.7.2= 1.8.0= 2.0.1= 2.0.2
Relion Sam600 Io FirmwareOperating system
Affected:= 2.2.1= 2.2.5
Relion 650 FirmwareOperating system
Affected:= 1.1= 1.3= 2.1= 2.2.0= 2.2.1= 2.2.2= 2.2.3= 2.2.4= 2.2.5

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. Identify the product model
    Locate the product name/model on the device label, web interface, or management console. Confirm it matches one of the affected products: Sys600, Rtu500, Reb500, Pwc600, Modular Switchgear Monitoring, Itt600 Sa Explorer, Relion Sam600 Io, or Relion 650.
    Affected if The product is not one of the listed affected products.
  2. Check the installed firmware version
    Access the device management interface or use the vendor-specific command to retrieve the firmware version. For Sys600, Rtu500, Reb500, Pwc600, and other products, this is typically shown in the system information or About section of the web UI, or via CLI command such as 'show version' or 'system info'.
    Affected if The firmware version falls within any of the affected ranges: Sys600 10.1 to 10.3.1 inclusive; Rtu500 multiple ranges as listed; Reb500 >= 7.0 and < 8.3.3; Pwc600 exactly 1.0, 1.1, or 1.2; Modular Switchgear Monitoring <= 2.2.3; Itt600 Sa Explorer specific versions listed; Relion Sam600 Io exactly 2
  3. Verify the IEC 61850 MMS server is enabled
    Check the device configuration or service settings to confirm whether the IEC 61850 MMS server feature is enabled. This is typically found in the communication protocol settings, IEC 61850 configuration section, or network services configuration of the device management interface.
    Affected if The MMS server feature is enabled and the firmware version is within the affected ranges.
  4. Test if MMS server accepts new connections
    Attempt to establish a new MMS client connection to the device on the MMS port (typically TCP port 102). Use an IEC 61850 MMS client tool or script to initiate a new connection attempt. Existing established connections should remain unaffected per the vulnerability description.
    Affected if The MMS server rejects new connection attempts while the device appears otherwise operational.

The environment is affected if the device runs any of the listed product models with a firmware version matching the affected ranges AND the IEC 61850 MMS server feature is enabled.

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 8.3.3 or later
Fixed in 8.3.3
Interim mitigation

Apply vendor-provided patches or firmware updates from Hitachi Energy for all affected products. Since this is a protocol stack vulnerability, network-level mitigations alone may be insufficient; vendor patches addressing the MMS server logic are required.

Fix this in Sys600 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3353 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-3353 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