CVE-2022-2081 is a high severity stack overflow in the HCI Modbus TCP function of Hitachi Energy RTU500 firmware, scored 7.5 by NVD. A high rate of crafted messages can reboot the CMU. I could not read the vendor advisory, so check it for affected and fixed versions.
What's affected
The record says a flaw in the HCI Modbus TCP function, in the product versions listed in the vendor advisory, lets an attacker send specially crafted messages at a high rate to an RTU500 and make the targeted CMU reboot. The flaw needs HCI Modbus TCP to be enabled and configured. The record explains the cause as a lack of flood control, which leads to an internal stack overflow. The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
The vendor advisory is the only reference, and its page needs JavaScript to render, so I could not read the affected firmware versions or the fixed ones. The record's product list gives only the RTU520 firmware family without version numbers, so I will not state any. Use the advisory itself.
The record lists the weakness as CWE-787, out-of-bounds write.
Weakness class: CWE-787.
How to check if you're exposed
First check whether the feature is on. The flaw needs HCI Modbus TCP enabled and configured, so look at the communication configuration of each RTU500 and note which units use it.
Then compare firmware versions with the lists in the Hitachi Energy advisory. I did not retrieve that list, so the advisory is the source of truth.
Finally, see who can reach the Modbus TCP port. The attack assumes network access with no privileges, so a unit on a flat network is more exposed than one behind a firewall that allows only the master station.
What to do now
- Inventory RTU500 units and their firmware, and mark those with HCI Modbus TCP enabled.
- Read the Hitachi Energy advisory for the affected and fixed versions.
- Update the firmware as the advisory directs, following your change process for operational technology.
- If you cannot update, disable HCI Modbus TCP where it is not needed.
- Limit access to the Modbus TCP port to known master stations with firewall rules, and add rate limits where the network equipment supports them.
Why it matters
Modbus TCP is old and has no authentication of its own. Any host that can reach the port can send requests. The record describes a lack of flood control: the function does not limit how fast messages arrive, and at high rates an internal buffer on the stack overflows. The weakness is CWE-787.
The documented effect is a reboot of the communication unit. In a substation or pipeline, a unit that restarts repeatedly can drop telemetry and control at the moment operators need it. An availability bug in this equipment has operational consequences that a score of 7.5 does not show.
Network design is the best defence for protocols like this one. Segment the control network, allow only the master stations, and monitor for message bursts.
This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.
Quick check
Do I need the Modbus feature on to be affected?
Yes. The record says HCI Modbus TCP must be enabled and configured.
Which firmware is fixed?
I could not read the advisory, so I do not state one. Read the Hitachi Energy advisory for the affected and fixed versions.
Sources
Last reviewed: 19 October 2026.