dbcve.org
Easergy P5 FirmwareOperating system · Schneider Electric

CVE-2022-22722

HIGH · 7.5 CVSS v3.1 Published 2022-02-04
Fix available
A fix is available. Upgrade to 01.401.101 or later.
See remediation →
80/100
Remediation priority · High
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-798: Use of Hard-coded Credentials vulnerability exists that could result in information disclosure. If an attacker were to obtain the SSH cryptographic key for the device and take active control of the local operational network connected to the product they could potentially observe and manipulate traffic associated with product configuration. Affected Product: Easergy P5 (All firmware versions prior to V01.401.101)

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 hard-coded SSH cryptographic key vulnerability (CWE-798) in Schneider Electric Easergy P5 protection relays allows attackers with network access to obtain the static SSH key and intercept or manipulate configuration traffic if they gain control of the local operational network.

MitigationUpdate firmware to V01.401.101 or later which replaces the hardcoded SSH key with unique, dynamically-generated keys; coordinate update during planned maintenance window due to industrial environment criticality.

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
Easergy P5 FirmwareOperating system
Affected:< 01.401.101

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/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. Confirm device model is Easergy P5
    Access the device web interface, configuration software, or front panel display to verify the exact model number is Schneider Electric Easergy P5 protection relay
    Affected if Device is not an Easergy P5 model - not affected by this specific CVE
  2. Identify installed firmware version
    Check the firmware version through the device web interface (typically under System > Device Information or About section), configuration software (such as Easergy Studio), or the device's front panel LCD menu under Device Info or Maintenance
    Affected if Unable to retrieve firmware version - further investigation needed
  3. Compare firmware version against vulnerability range
    Compare your installed firmware version number to the affected range: any version below 01.401.101 is vulnerable. Note the full version string including any sub-version numbers (e.g., 01.400.100, 01.401.0)
    Affected if Firmware version is 01.401.101 or higher - not affected; version is below 01.401.101 - vulnerable
  4. Verify SSH service is enabled and accessible
    Check device network configuration settings via web interface or configuration software to determine if SSH service is enabled. From an external network perspective, attempt to verify if TCP port 22 (or configured SSH port) is reachable to the device
    Affected if SSH is disabled entirely - limited attack surface but firmware still contains the hardcoded key; SSH is enabled and network-accessible - actively vulnerable to exploitation

Device is affected if it is an Easergy P5 relay running firmware version below 01.401.101 with SSH service enabled and reachable on 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 01.401.101 or later
Fixed in 01.401.101
Interim mitigation

Update firmware to V01.401.101 or later which replaces the hardcoded SSH key with unique, dynamically-generated keys; coordinate update during planned maintenance window due to industrial environment criticality.

Recommended fix High confidence

V01.401.101

  1. Obtain the firmware update file V01.401.101 or later from the official Schneider Electric download portal (download.schneider-electric.com)
  2. Verify the integrity of the firmware file using checksums provided by Schneider Electric
  3. Review the Easergy P5 firmware upgrade instructions in the product manual
  4. Connect to the Easergy P5 device through the recommended management interface
  5. Perform a backup of the current device configuration before initiating the upgrade
  6. Initiate the firmware upgrade process following the manufacturer's documented procedure
  7. Verify that the upgrade completed successfully and the device is running firmware version 01.401.101 or later
  8. Confirm that the SSH cryptographic keys have been regenerated or updated as part of the firmware upgrade

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

Fix this in Easergy P5 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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