dbcve.org
Rack Power Distribution Unit With Network Management Card 2 FirmwareOperating system · Schneider Electric

CVE-2021-22825

HIGH · 8.0 CVSS v3.1 Published 2022-01-28
Fix available
A fix is available. Upgrade to 1.2.0.2 / 7.0.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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-200: Exposure of Sensitive Information to an Unauthorized Actor vulnerability exists that could allow an attacker to access the system with elevated privileges when a privileged account clicks on a malicious URL that compromises the security token. Affected Products: AP7xxxx and AP8xxx with NMC2 (V6.9.6 or earlier), AP7xxx and AP8xxx with NMC3 (V1.1.0.3 or earlier), and APDU9xxx with NMC3 (V1.0.0.28 or earlier)

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 confidence

This is a CWE-200 vulnerability in APC network management card (NMC) firmware where a malicious URL can compromise a security token when clicked by a privileged user, allowing unauthorized access with elevated privileges. The vulnerability affects NMC2 firmware versions 6.9.6 and earlier on AP7xxxx/AP8xxx models, and NMC3 firmware versions 1.1.0.3/1.0.0.28 and earlier on AP7xxx/AP8xxx and APDU9xxx models.

MitigationUpdate NMC2 firmware to version 6.9.7 or later and NMC3 firmware to version 1.1.0.4/1.0.0.29 or later. Until patched, educate privileged users to avoid clicking untrusted URLs and consider network segmentation to limit exposure.

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
Rack Power Distribution Unit With Network Management Card 2 FirmwareOperating system
Affected:< 7.0.6
Rack Power Distribution Unit With Network Management Card 3 FirmwareOperating system
Affected:< 1.2.0.2

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 NMC device type and model
    Access the NMC web interface or SSH console and locate the device model information (AP7xxx, AP8xxx, or APDU9xxx) and confirm whether it uses NMC2 or NMC3 firmware. This is typically visible on the login page, dashboard, or via the 'about' command in SSH.
    Affected if Device is an AP7xxx/AP8xxx with NMC2, or an AP7xxx/AP8xxx/APDU9xxx with NMC3 - only these models and NMC types are affected.
  2. Determine the installed NMC2 firmware version
    If the device has NMC2, check the firmware version in the web interface under System > About or via SSH using the 'version' or 'about' command. Look for a version number.
    Affected if The version is 7.0.6 or lower, or 6.9.6 or earlier per the CVE description.
  3. Determine the installed NMC3 firmware version
    If the device has NMC3, check the firmware version in the web interface under System > About or via SSH using the 'version' or 'about' command. Look for a version number.
    Affected if The version is 1.2.0.2 or lower, or specifically 1.1.0.3/1.0.0.28 or earlier per the CVE description.
  4. Verify if privileged users exist who could click malicious URLs
    Review user accounts in the NMC interface under User Management or Access Control. Identify accounts with administrative or privileged access rights.
    Affected if Privileged user accounts exist - the exploitation requires a privileged user to click a maliciously crafted URL.

A user is affected if they have an APC NMC2 or NMC3 device with firmware version below 7.0.6 (NMC2) or below 1.2.0.2 (NMC3), and there are privileged users who could potentially click a malicious URL.

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 1.2.0.2 / 7.0.6 or later
Fixed in 1.2.0.27.0.6
Interim mitigation

Update NMC2 firmware to version 6.9.7 or later and NMC3 firmware to version 1.1.0.4/1.0.0.29 or later. Until patched, educate privileged users to avoid clicking untrusted URLs and consider network segmentation to limit exposure.

Recommended fix High confidence

Rack PDU with NMC2: upgrade to firmware 7.0.6 or later; Rack PDU with NMC3: upgrade to firmware 1.2.0.2 or later

  1. Identify the exact model number (AP7xxx, AP8xxx, or APDU9xxx) and current NMC firmware version of the Rack PDU
  2. Navigate to Schneider Electric's support portal at download.schneider-electric.com
  3. Locate the firmware update for your specific PDU model and NMC version
  4. Download the appropriate firmware: NMC2 upgrade to version 7.0.6 or later, NMC3 upgrade to version 1.2.0.2 or later
  5. Review Schneider Electric's firmware installation guide for your specific PDU model
  6. Apply the firmware update following the vendor's documented upgrade procedure
  7. After reboot, verify the firmware has been updated to the fixed version (NMC2: 7.0.6+ or NMC3: 1.2.0.2+)
  8. Confirm the vulnerability is resolved by reviewing the security release notes
Caveat Firmware updates may require downtime and should be tested in a non-production environment first; ensure compatible PDU model before applying

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

Fix this in Rack Power Distribution Unit With Network Management Card 2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

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