CVE-2023-6711
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 · uneditedVulnerability exists in SCI IEC 60870-5-104 and HCI IEC 60870-5-104 that affects the RTU500 series product versions listed below. Specially crafted messages sent to the mentioned components are not validated properly and can result in buffer overflow and as final consequence to a reboot of an RTU500 CMU.
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 confidenceBuffer overflow vulnerability in SCI IEC 60870-5-104 and HCI IEC 60870-5-104 components of RTU500 series. Specially crafted IEC 60870-5-104 protocol messages lack proper input validation, causing overflow that results in CMU device reboot.
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>= 12.0.1.0, < 12.0.15.0>= 12.2.1.0, < 12.2.12.0>= 12.4.1.0, < 12.4.12.0>= 12.6.1.0, < 12.6.10.0>= 12.7.1.0, < 12.7.7.0>= 13.2.1.0, < 13.2.7.0>= 13.4.1.0, < 13.4.4.0= 13.5.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify RTU500 hardware modelLocate the physical device or check system documentation for the Hitachi Energy RTU500 series model number (e.g., RTU500, CMU). This vulnerability affects only RTU500 series devices.Affected if Device is not an Hitachi Energy RTU500 series unit
-
Determine firmware versionAccess the RTU500 management interface or use the vendor's configuration tool to retrieve the installed firmware version. Common methods include: web UI, CLI command 'show version', or management software.Affected if Firmware version does not fall within any of the affected ranges (12.0.1.0-12.0.14.x, 12.2.1.0-12.2.11.x, 12.4.1.0-12.4.11.x, 12.6.1.0-12.6.9.x, 12.7.1.0-12.7.6.x, 13.2.1.0-13.2.6.x, 13.4.1.0-13.4.3.x, or 13.5.1.0)
-
Verify IEC 60870-5-104 protocol is enabledCheck the RTU500 configuration for active IEC 60870-5-104 protocol instances. Access the protocol configuration section in the management interface or configuration file and confirm if SCI IEC 60870-5-104 or HCI IEC 60870-5-104 components are configured and enabled.Affected if IEC 60870-5-104 protocol (SCI or HCI) is not enabled on the device
-
Inspect protocol listener configurationReview the network configuration to identify which IEC 60870-5-104 ports are listening. The vulnerability resides in the SCI (Serial Communication Interface) and HCI (Host Communication Interface) IEC 60870-5-104 components. Check if these services are exposed to network traffic.Affected if No IEC 60870-5-104 listeners are configured or the SCI/HCI components are disabled
Device is affected if it is an Hitachi Energy RTU500 with IEC 60870-5-104 (SCI or HCI) enabled and the firmware version matches one of the vulnerable ranges listed.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.0.15.012.2.12.012.4.12.0
Apply vendor-provided patches for RTU500 series. Until patched, implement network segmentation and traffic filtering for IEC 60870-5-104 traffic to reduce attack surface.
Rtu500 Firmware 12.0.15.0, 12.2.12.0, 12.4.12.0, or 12.6.10.0 (depending on your current branch)
- Identify the current firmware version of the RTU500 CMU by checking the system configuration or firmware management interface
- Determine which firmware branch (12.0.x, 12.2.x, 12.4.x, or 12.6.x) is currently deployed
- Obtain the appropriate fixed firmware version from Hitachi Energy based on the installed branch: 12.0.15.0 or later for 12.0.x branch; 12.2.12.0 or later for 12.2.x branch; 12.4.12.0 or later for 12.4.x branch; 12.6.10.0 or later for 12.6.x branch
- Review Hitachi Energy firmware upgrade documentation and release notes for any specific upgrade procedures
- Back up current configuration according to RTU500 backup procedures before initiating upgrade
- Apply firmware upgrade via the standard RTU500 firmware update mechanism
- Verify the upgrade was successful and the new firmware version is running
- Confirm the vulnerability is remediated by ensuring the fixed version is properly installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2023-6711 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-6711 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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