CVE-2022-22806
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-294: Authentication Bypass by Capture-replay vulnerability exists that could cause an unauthenticated connection to the UPS when a malformed connection is sent. 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 confidenceCWE-294 Authentication Bypass by Capture-replay vulnerability in APC SmartConnect UPS devices allows unauthenticated attackers to establish connections by sending malformed connection data that bypasses the authentication mechanism. The vulnerability affects multiple series (SMT, SMC, SMTL, SCL, SMX) with various firmware versions prior to the fixes.
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<= 04.5<= 04.2<= 02.9<= 02.5<= 02.5<= 02.5<= 03.1<= 03.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the UPS model seriesLocate the physical UPS or check the device documentation/network inventory for the exact model designation (SMT, SMC, SMTL, SCL, or SMX series)Affected if The device is not one of the listed series (SMT, SMC, SMTL, SCL, SMX)
-
Determine the firmware versionAccess the APC SmartConnect web interface or use the APC network management card interface to view the firmware version information, typically found under Device > About or similar firmware status sectionAffected if The firmware version matches or is below: SMT <= 04.5, SMC <= 04.2, SMTL <= 02.9, SCL (1029/1030/1036) <= 02.5, SCL (1037) <= 03.1, SMX (1031) <= 03.1
-
Confirm SmartConnect feature is enabledLog into the UPS network interface and verify that the SmartConnect feature is actively configured and operational, not disabled or in a dormant stateAffected if SmartConnect is enabled and the device is accessible over the network
-
Check network accessibility of SmartConnect interfaceVerify that the SmartConnect management interface (typically on TCP ports 80/443 or vendor-specified ports) is reachable from network segments that are not explicitly isolatedAffected if The SmartConnect interface is exposed to untrusted network segments
The environment is affected if an APC SmartConnect UPS from the SMT, SMC, SMTL, SCL, or SMX series with vulnerable firmware versions and SmartConnect enabled is network-accessible.
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 · scopedApply vendor firmware updates as they become available for affected UPS series; until patched, isolate SmartConnect devices on a dedicated VLAN with strict access controls and monitor for anomalous connection attempts.
Schneider Electric Smart-UPS firmware updates beyond the vulnerable versions (SMT >04.5, SMC >04.2, SMTL >02.9, SCL >02.5/03.1, SMX >03.1) - contact Schneider Electric for specific fixed version numbers
- 1. Identify the exact model number and current firmware version of the affected UPS device using the device interface or management software
- 2. Download the latest firmware from Schneider Electric's official support website (www.se.com) for your specific UPS model series
- 3. Review all release notes and security advisories associated with the firmware update to confirm it addresses CVE-2022-22806
- 4. Ensure the device is connected to a stable power source and consider scheduling maintenance during low-activity periods
- 5. Follow Schneider Electric's official firmware update procedure for your specific UPS model, typically via Network Management Card interface or APC management software
- 6. After updating, verify the new firmware version matches the fixed release and confirm the device is functioning normally
- 7. Review authentication and network access configurations post-update to ensure security settings are properly applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22806 — 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-2022-22806 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