dbcve.org
Rtu500 FirmwareOperating system · Abb

CVE-2022-28613

HIGH · 7.5 CVSS v3.1 Published 2022-05-02
Fix available
A fix is available. Upgrade to 12.0.14.0 / 12.2.12.0 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 HCI Modbus TCP function included in the product versions listed above. If the HCI Modbus TCP is en-abled and configured, an attacker could exploit the vulnerability by sending a specially crafted message to the RTU500, causing the receiving RTU500 CMU to reboot. The vulnerability is caused by the validation error in the length information carried in MBAP header in the HCI Modbus TCP function.

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 validation error exists in the HCI Modbus TCP function's handling of the MBAP (Modbus Application Protocol) header. The length field in the MBAP header is not properly validated, allowing an attacker to send specially crafted messages that cause the RTU500 CMU to reboot, resulting in denial of service.

MitigationIf HCI Modbus TCP is not required in the deployment environment, disable it. Otherwise, apply vendor-supplied patches that add proper validation of the MBAP header length field before processing Modbus messages.

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:>= 12.2.1.0, < 12.2.12.0
Rtu500 FirmwareOperating system
Affected:>= 12.0.1.0, < 12.0.14.0>= 12.4.1.0, < 12.4.12.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

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 RTU500 firmware version
    Access the RTU500 device management interface or use the device's diagnostic command to retrieve the current firmware version. This is typically found in system information, device status, or firmware management sections of the product documentation.
    Affected if The installed firmware version falls within any of these ranges: ABB: >= 12.2.1.0 and < 12.2.12.0; Hitachi Energy: >= 12.0.1.0 and < 12.0.14.0, OR >= 12.4.1.0 and < 12.4.12.0, OR >= 12.6.1.0 and < 12.6.8.0, OR >= 12.7.1.0 and < 12.7.4.0, OR >= 13.2.1.0 and < 13.2.5.0
  2. Confirm HCI Modbus TCP is enabled
    Locate the HCI Modbus TCP configuration settings in the RTU500 device management interface, configuration files, or through the device's command-line interface. Look for Modbus TCP server or HCI Modbus settings.
    Affected if HCI Modbus TCP functionality is actively enabled on the device, as this is the vulnerable component that processes the MBAP header
  3. Verify the device is network accessible via Modbus TCP
    Check network configuration to confirm the device has an active Modbus TCP listener. This may involve checking listening ports, network services, or firewall rules on the RTU500.
    Affected if The Modbus TCP port is open and accessible, making the device potentially reachable to an attacker sending malicious MBAP headers

The device is affected if it runs a firmware version within the affected ranges AND has HCI Modbus TCP enabled and accessible.

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 12.0.14.0 / 12.2.12.0 / 12.4.12.0 or later
Fixed in 12.0.14.012.2.12.012.4.12.0
Interim mitigation

If HCI Modbus TCP is not required in the deployment environment, disable it. Otherwise, apply vendor-supplied patches that add proper validation of the MBAP header length field before processing Modbus messages.

Recommended fix High confidence

Rtu500 Firmware 12.0.14.0, 12.2.12.0, 12.4.12.0, 12.6.8.0, or 12.7.4.0 (depending on installed branch)

  1. 1. Identify the current firmware version of the Rtu500 device by accessing the device management interface or checking system information.
  2. 2. Determine which firmware branch (12.0.x, 12.2.x, 12.4.x, 12.6.x, or 12.7.x) the device is currently running.
  3. 3. Download the appropriate fixed firmware version from Hitachi Energy's official support portal at publisher.hitachienergy.com.
  4. 4. For branch 12.0.x: upgrade to version 12.0.14.0 or later.
  5. 5. For branch 12.2.x: upgrade to version 12.2.12.0 or later.
  6. 6. For branch 12.4.x: upgrade to version 12.4.12.0 or later.
  7. 7. For branch 12.6.x: upgrade to version 12.6.8.0 or later.
  8. 8. For branch 12.7.x: upgrade to version 12.7.4.0 or later.
Caveat Firmware upgrades may require downtime and should be tested in a staging environment before production deployment

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

Fix this in Rtu500 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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