dbcve.org
Scadapack 312e FirmwareOperating system · Schneider Electric

CVE-2021-22816

HIGH · 7.5 CVSS v3.1 Published 2022-01-28
Fix available
A fix is available. Upgrade to 8.19.1 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 CWE-754: Improper Check for Unusual or Exceptional Conditions vulnerability exists that could cause a Denial of Service of the RTU when receiving a specially crafted request over Modbus, and the RTU is configured as a Modbus server. Affected Products: SCADAPack 312E, 313E, 314E, 330E, 333E, 334E, 337E, 350E and 357E RTUs with firmware V8.18.1 and prior

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 CWE-754 Improper Check for Unusual or Exceptional Conditions vulnerability exists in SCADAPack RTU devices (312E through 357E) where a specially crafted Modbus request can cause denial of service when the RTU is configured as a Modbus server. The vulnerability allows an attacker to trigger an unhandled exceptional condition leading to service disruption.

MitigationUpdate firmware to a version beyond V8.18.1. If immediate patching is not feasible, implement network segmentation and restrict access to Modbus server ports to trusted clients only.

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
Scadapack 312e FirmwareOperating system
Affected:< 8.19.1
Scadapack 313e FirmwareOperating system
Affected:< 8.19.1
Scadapack 314e FirmwareOperating system
Affected:< 8.19.1
Scadapack 330e FirmwareOperating system
Affected:< 8.19.1
Scadapack 333e FirmwareOperating system
Affected:< 8.19.1
Scadapack 334e FirmwareOperating system
Affected:< 8.19.1
Scadapack 337e FirmwareOperating system
Affected:< 8.19.1
Scadapack 350e FirmwareOperating system
Affected:< 8.19.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 SCADAPack model
    Query the device via its web interface, console, or Modbus register 0-9999 (device identification) to confirm the exact model number (312e, 313e, 314e, 330e, 333e, 334e, 337e, or 350e)
    Affected if The device is a Schneider Electric SCADAPack 312e, 313e, 314e, 330e, 333e, 334e, 337e, or 350e
  2. Determine the installed firmware version
    Access the device web interface, console, or read Modbus register 0-1000 (firmware revision) to obtain the exact firmware version number
    Affected if The firmware version is below 8.19.1 (for example, 8.18.0, 8.17.x, or earlier)
  3. Verify Modbus server is enabled
    Check the device configuration via its web interface or console under Modbus settings to confirm if the Modbus server (slave) functionality is turned on
    Affected if The Modbus server role is enabled and the device is configured to respond to Modbus requests
  4. Confirm network accessibility of Modbus service
    Use a network scan or port check (for example, telnet or nmap) to verify that the Modbus port (default 502) is open and reachable from the network
    Affected if The Modbus server port is accessible from network segments that contain untrusted or unknown clients

You are affected if you have a SCADAPack 312e-350e device running firmware below version 8.19.1 with the Modbus server feature enabled and accessible from the network.

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 8.19.1 or later
Fixed in 8.19.1
Interim mitigation

Update firmware to a version beyond V8.18.1. If immediate patching is not feasible, implement network segmentation and restrict access to Modbus server ports to trusted clients only.

Recommended fix High confidence

Firmware 8.19.1 or later

  1. Verify the exact model and current firmware version of the Scadapack RTU device before upgrading
  2. Download the firmware version 8.19.1 or later from the Schneider Electric download portal (download.schneider-electric.com)
  3. Review the firmware release notes for any special installation instructions or prerequisites
  4. Backup the current device configuration if possible
  5. Follow Schneider Electric's standard firmware update procedure for Scadapack RTU devices, typically involving transferring the firmware file via the device's management interface
  6. After upgrading, verify the firmware version has been updated successfully
  7. Test that the Modbus server functionality operates normally after the upgrade
  8. Confirm the vulnerability is mitigated by ensuring the device no longer crashes from specially crafted Modbus requests

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

Fix this in Scadapack 312e Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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