dbcve.org
Rtu500 FirmwareOperating system · Hitachienergy

CVE-2022-4608

HIGH · 7.5 CVSS v3.1 Published 2023-07-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 HCI IEC 60870-5-104 function included in certain versions of the RTU500 series product. The vulnerability can only be exploited, if the HCI 60870-5-104 is configured with support for IEC 62351-3. After session resumption interval is expired an RTU500 initiated update of session parameters causes an unexpected restart due to a stack overflow.

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

A stack overflow vulnerability exists in the HCI IEC 60870-5-104 function of RTU500 series products. When the HCI 60870-5-104 is configured with IEC 62351-3 support and the session resumption interval expires, an RTU500-initiated update of session parameters triggers a stack overflow causing an unexpected device restart (denial of service).

MitigationApply vendor-provided patches for the RTU500 series. If no patch is available, consider disabling IEC 62351-3 support if业务ally acceptable, or implement network segmentation to limit exposure to authenticated attackers.

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
Rtu500 FirmwareOperating system
Affected:= 13.3.1= 13.3.2= 13.3.3= 13.4.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
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 device model identifier in the RTU500 system inventory, device management interface, or hardware labeling. Confirm it is an RTU500 series device from Hitachi Energy.
    Affected if The device is not an RTU500 series product - the vulnerability does not apply to other devices.
  2. Check the firmware version
    Access the RTU500 firmware management interface, system information panel, or use the vendor-specific command to retrieve the installed firmware version. Compare against the affected versions: 13.3.1, 13.3.2, 13.3.3, and 13.4.1.
    Affected if The installed firmware version matches exactly 13.3.1, 13.3.2, 13.3.3, or 13.4.1 - other versions are not affected by this specific CVE.
  3. Verify HCI IEC 60870-5-104 is configured
    Check the RTU500 protocol configuration settings or HCI module settings to determine if the IEC 60870-5-104 protocol function is enabled and active.
    Affected if IEC 60870-5-104 is not configured or is disabled - the vulnerability cannot be triggered.
  4. Confirm IEC 62351-3 support is enabled
    Inspect the IEC 60870-5-104 security settings or IEC 62351-3 configuration panel to verify whether TLS/SSH security support for IEC 62351-3 is turned on.
    Affected if IEC 62351-3 support is disabled - the specific stack overflow condition does not occur.
  5. Check session resumption interval
    Review the IEC 62351-3 session management or TLS session configuration to identify if a session resumption interval is set and configured to expire.
    Affected if No session resumption interval is configured or it is set to never expire - the trigger condition is not present.

The environment is affected only if the device is an RTU500 with firmware 13.3.1, 13.3.2, 13.3.3, or 13.4.1, AND HCI IEC 60870-5-104 is enabled with IEC 62351-3 support, AND a session resumption interval is configured to expire.

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

Apply vendor-provided patches for the RTU500 series. If no patch is available, consider disabling IEC 62351-3 support if业务ally acceptable, or implement network segmentation to limit exposure to authenticated attackers.

Fix this in Rtu500 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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