dbcve.org
Smt Series 1015 Ups FirmwareOperating system · Schneider Electric

CVE-2022-22805

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-09
Fix available
A fix is available. Upgrade to after 04.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability exists that could cause remote code execution when an improperly handled TLS packet is reassembled. Affected Product: SmartConnect Family: SMT Series (SMT Series ID=1015: UPS 04.5 and prior), SMC Series (SMC Series ID=1018: UPS 04.2 and prior), SMTL Series (SMTL Series ID=1026: UPS 02.9 and prior), SCL Series (SCL Series ID=1029: UPS 02.5 and prior / SCL Series ID=1030: UPS 02.5 and prior / SCL Series ID=1036: UPS 02.5 and prior / SCL Series ID=1037: UPS 03.1 and prior), SMX Series (SMX Series ID=1031: UPS 03.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 classic buffer overflow vulnerability (CWE-120) exists in the TLS packet reassembly logic of APC Smart-UPS devices across SMT, SMC, SMTL, SCL, and SMX series. The affected firmware versions copy TLS packet data into a fixed-size buffer without validating input size, allowing an attacker to overflow the buffer via maliciously crafted TLS packets and achieve remote code execution.

MitigationUpdate UPS firmware to vendor-specified patched versions: SMT Series (UPS 04.6+), SMC Series (UPS 04.3+), SMTL Series (UPS 03.0+), SCL Series (UPS 02.6+ for ID1029/1030/1036, UPS 03.2+ for ID1037), and SMX Series (UPS 03.2+). Isolate affected devices on network segments with limited exposure to untrusted TLS connections until patched.

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
Smt Series 1015 Ups FirmwareOperating system
Affected:<= 04.5
Smc Series 1018 Ups FirmwareOperating system
Affected:<= 04.2
Smtl Series 1026 Ups FirmwareOperating system
Affected:<= 02.9
Scl Series 1029 Ups FirmwareOperating system
Affected:<= 02.5
Scl Series 1030 Ups FirmwareOperating system
Affected:<= 02.5
Scl Series 1036 Ups FirmwareOperating system
Affected:<= 02.5
Scl Series 1037 Ups FirmwareOperating system
Affected:<= 03.1
Smx Series 1031 Ups FirmwareOperating system
Affected:<= 03.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 UPS model series
    Locate the physical UPS or check the device documentation/network management interface to confirm the model series. Look for model numbers containing SMT, SMC, SMTL, SCL, or SMX prefixes.
    Affected if The device is NOT one of these series: SMT, SMC, SMTL, SCL, or SMX.
  2. Determine the installed firmware version
    Access the UPS web interface, NMC (Network Management Card) configuration, or use the APC PowerChute software to view the firmware version. The version is typically displayed in the device information or status page.
    Affected if Unable to retrieve the firmware version for comparison.
  3. Compare firmware version against affected ranges
    Check the installed firmware version against these limits: SMT Series <= 04.5, SMC Series <= 04.2, SMTL Series <= 02.9, SCL Series (ID1029/1030) <= 02.5, SCL Series (ID1036) <= 02.5, SCL Series (ID1037) <= 03.1, SMX Series <= 03.1.
    Affected if Firmware version is within or below the affected version limits listed.
  4. Confirm TLS/network management features are enabled
    Check the UPS configuration or NMC settings to determine if Network Management Card, web server, or any TLS-enabled remote management interface is active.
    Affected if TLS/network management features are disabled and the device has no network exposure.

The device is affected if it is an SMT, SMC, SMTL, SCL, or SMX series UPS with firmware version at or below the specified limits AND has TLS-enabled network management interfaces enabled.

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 a release after 04.5
Interim mitigation

Update UPS firmware to vendor-specified patched versions: SMT Series (UPS 04.6+), SMC Series (UPS 04.3+), SMTL Series (UPS 03.0+), SCL Series (UPS 02.6+ for ID1029/1030/1036, UPS 03.2+ for ID1037), and SMX Series (UPS 03.2+). Isolate affected devices on network segments with limited exposure to untrusted TLS connections until patched.

Recommended fix Moderate confidence

Firmware version higher than affected versions - obtain latest firmware from Schneider Electric for your specific UPS model (SMT, SMC, SMTL, SCL, or SMX series)

  1. 1. Identify the specific UPS model (SMT, SMC, SMTL, SCL, or SMX series) from the affected product list
  2. 2. Determine the current firmware version installed on the affected UPS device
  3. 3. Visit the Schneider Electric website (www.se.com) or contact Schneider Electric technical support to obtain the latest firmware version for your specific UPS model
  4. 4. Download the firmware update from an official Schneider Electric source
  5. 5. Follow Schneider Electric's documented firmware upgrade procedure for the affected UPS model (typically involves uploading the firmware file through the device's network management interface or serial connection)
  6. 6. After upgrading, verify the firmware version has been updated to a version higher than the affected versions listed (SMT: >04.5, SMC: >04.2, SMTL: >02.9, SCL: >02.5/03.1 depending on model, SMX: >03.1)
Caveat Firmware updates on UPS devices may temporarily interrupt power protection; ensure proper planning and maintenance window

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

Fix this in Smt Series 1015 Ups Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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