dbcve.org
Rtu520 FirmwareOperating system · Hitachienergy

CVE-2022-2081

HIGH · 7.5 CVSS v3.1 Published 2024-01-04
Fix available
A fix is available. Upgrade to after 13.2.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
A vulnerability exists in the HCI Modbus TCP function included in the product versions listed above. If the HCI Modbus TCP is enabled and configured, an attacker could exploit the vulnerability by sending a specially crafted message to the RTU500 in a high rate, causing the targeted RTU500 CMU to reboot. The vulnerability is caused by a lack of flood control which eventually if exploited causes an internal stack overflow 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 · moderate confidence

A denial-of-service vulnerability exists in the HCI Modbus TCP function of Schneider Electric RTU500 CMU devices. The vulnerability stems from missing flood/rate control mechanisms, allowing remote attackers to send high-rate specially crafted Modbus TCP messages that trigger a stack overflow, causing the device to reboot.

MitigationIf HCI Modbus TCP functionality is not required, disable it. Otherwise, apply vendor-provided patches that implement proper rate limiting and flood protection in the HCI Modbus TCP function.

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
Rtu520 FirmwareOperating system
Affected:>= 12.0.1, <= 12.0.13>= 12.2.1, <= 12.2.11>= 12.4.1, <= 12.4.11>= 12.6.1, <= 12.6.7>= 12.7.1, <= 12.7.3>= 13.2.1, <= 13.2.4= 13.3.1
Rtu530 FirmwareOperating system
Affected:>= 12.0.1, <= 12.0.13>= 12.2.1, <= 12.2.11>= 12.4.1, <= 12.4.11>= 12.6.1, <= 12.6.7>= 12.7.1, <= 12.7.3>= 13.2.1, <= 13.2.4= 13.3.1
Rtu540 FirmwareOperating system
Affected:>= 12.0.1, <= 12.0.13>= 12.2.1, <= 12.2.11>= 12.4.1, <= 12.4.11>= 12.6.1, <= 12.6.7>= 12.7.1, <= 12.7.3>= 13.2.1, <= 13.2.4= 13.3.1
Rtu560 FirmwareOperating system
Affected:>= 12.0.1, <= 12.0.13>= 12.2.1, <= 12.2.11>= 12.4.1, <= 12.4.11>= 12.6.1, <= 12.6.7>= 12.7.1, <= 12.7.3>= 13.2.1, <= 13.2.4= 13.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
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 RTU device model
    Locate the physical device or check the device inventory for the model number. The affected models are RTU520, RTU530, RTU540, and RTU560.
    Affected if The device is not one of these four RTU models.
  2. Determine the firmware version
    Access the device management interface or use the vendor-provided diagnostic tool to retrieve the current firmware version. Compare it against the affected version ranges: 12.0.1 to 12.0.13, 12.2.1 to 12.2.11, 12.4.1 to 12.4.11, 12.6.1 to 12.6.7, 12.7.1 to 12.7.3, 13.2.1 to 13.2.4, or exactly version 13.3.1.
    Affected if The installed firmware version falls within any of these ranges.
  3. Check if HCI Modbus TCP is enabled
    Access the device configuration settings and examine the HCI Modbus TCP function status. Look for a configuration option or service status that indicates whether the Modbus TCP interface is active.
    Affected if The HCI Modbus TCP function is enabled and operational on the device.
  4. Verify network exposure of Modbus TCP service
    Review network firewall rules or access control lists to determine if the Modbus TCP port (typically port 502) is exposed to untrusted network segments or the internet.
    Affected if The Modbus TCP service is reachable from untrusted networks.

A user is affected if they have an RTU520, RTU530, RTU540, or RTU560 device running a firmware version within the listed ranges with 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.

From vendor data
Upgrade available Upgrade to a release after 13.2.4
Interim mitigation

If HCI Modbus TCP functionality is not required, disable it. Otherwise, apply vendor-provided patches that implement proper rate limiting and flood protection in the HCI Modbus TCP function.

Fix this in Rtu520 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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