CVE-2021-22713
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 · uneditedA CWE-119:Improper restriction of operations within the bounds of a memory buffer vulnerability exists in PowerLogic ION8650, ION8800, ION7650, ION7700/73xx, and ION83xx/84xx/85xx/8600 (see security notifcation for affected versions), which could cause the meter to reboot.
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 confidenceCWE-119 buffer overflow vulnerability in Schneider Electric PowerLogic ION series meters (ION8650, ION8800, ION7650, ION7700/73xx, ION83xx/84xx/85xx/8600). The vulnerability is network-exploitable (CVSS AV:N/AC:L/PR:N) with no authentication required, allowing remote attackers to trigger a buffer overflow that causes the meter to 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< 4.40.1< 372< 376< 416< 376all versionsall versionsall versionsall versionsCVSS 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 Schneider Electric PowerLogic ION meter on the networkUse network scanning tools (such as nmap, or ICS-specific discovery tools) to locate devices with Schneider Electric vendor identifiers or known ION protocol ports (typically port 502 for Modbus/TCP, or device-specific management ports). Check device hostname, banner, or response to protocol queries for identifiers like ION8650, ION8800, ION7650, ION7700, ION7300, ION8300, or ION8400.Affected if A PowerLogic ION series meter (ION8650, ION8800, ION7550/7650, ION7700/7300, ION8300/8400) is found on the network.
-
Retrieve firmware version from the meterAccess the device web interface, or query the meter via Modbus/TCP, DNP3, or manufacturer-specific protocol (ION protocol) to retrieve the firmware version field. This is typically found in the device information or system status page via the embedded web server, or through a direct protocol read of identity registers.Affected if The retrieved firmware version matches one of the affected product lines and falls below the fixed version for that model.
-
Compare installed firmware version against affected rangesMatch the retrieved firmware version to the following thresholds: ION8650 < 4.40.1, ION8800 < 372, ION7550 < 376 or < 416, ION7650 < 376, ION7700/7300/8300/8400 = all versions (any version is affected).Affected if The installed version is below the threshold for your specific model, or if the device is ION7700, ION7300, ION8300, or ION8400 (which have no fixed version and are all affected).
-
Verify network exposure of device management interfaceConfirm whether the meter is directly accessible on the network with its management interface (web UI, Modbus/TCP, or ION protocol port) exposed without firewall segmentation or VPN protection. Check if the device accepts connections from untrusted network segments.Affected if The meter management interface is reachable from network segments that contain untrusted or unauthorized users (CVSS vector AV:N indicates network-level attack is possible).
A user is affected if they have any ION7650, ION7700, ION7300, ION8300, or ION8400 meter (all versions), or an ION8650/ION8800/ION7550 meter with firmware below the fixed threshold, and this device is network-accessible to potential attackers.
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.
From vendor data4.40.1372376
Apply vendor firmware updates from Schneider Electric security notification to patch the memory boundary validation issue. Since this is an ICS device, updates should be tested in a staging environment before production deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22713 — 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-2021-22713 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