dbcve.org
Easergy P5 FirmwareOperating system · Schneider Electric

CVE-2022-22723

HIGH · 8.8 CVSS v3.1 Published 2022-02-04
Fix available
A fix is available. Upgrade to 01.401.101 or later.
See remediation →
93/100
Remediation priority · Urgent
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 vulnerability exists that could lead to a buffer overflow causing program crashes and arbitrary code execution when specially crafted packets are sent to the device over the network. Protection functions and tripping function via GOOSE can be impacted. 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 · moderate confidence

A buffer overflow vulnerability (CWE-120) exists in the Schneider Electric Easergy P5 protection relay where the device fails to properly validate the size of incoming network packets before copying them into fixed-size buffers. When specially crafted packets are sent to the device over the network, this can overflow the buffer, potentially causing program crashes and enabling arbitrary code execution. The vulnerability specifically impacts protection functions and the tripping function via the GOOSE (GOOSE - Generic Object Oriented Substation Event) protocol used in IEC 61850 communications.

MitigationUpdate Easergy P5 firmware to version V01.401.101 or later to remediate this vulnerability. Prior to update, isolate affected devices on a restricted network segment and implement compensating controls such as deep packet inspection at network boundaries to filter malicious GOOSE packets.

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

CVSS:3.1/AV:A/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. Confirm Easergy P5 device model
    Identify the device through its web interface, management console, or network discovery. Look for 'Easergy P5' or 'P5' in device identification.
    Affected if The device is not an Easergy P5 protection relay, then this CVE does not apply.
  2. Check installed firmware version
    Access the device web interface or management console and navigate to the firmware/version information section. Compare the displayed firmware version to 01.401.101.
    Affected if Firmware version is lower than 01.401.101, the device is potentially affected.
  3. Verify GOOSE/IEC 61850 protocol is enabled
    Check the device configuration for IEC 61850 communications settings. Look for GOOSE protocol configuration options in the network or communication settings menu.
    Affected if GOOSE protocol is enabled and the device is on the network, the vulnerability can be exploited via specially crafted GOOSE packets.
  4. Assess network exposure
    Determine if the device is accessible from untrusted networks. Check firewall rules, network segmentation, and whether the device has direct internet exposure.
    Affected if The device is accessible from less-trusted network segments without packet filtering, exploitation is possible.

The environment is affected if an Easergy P5 device with firmware below 01.401.101 has GOOSE/IEC 61850 enabled and is accessible over 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 Easergy P5 firmware to version V01.401.101 or later to remediate this vulnerability. Prior to update, isolate affected devices on a restricted network segment and implement compensating controls such as deep packet inspection at network boundaries to filter malicious GOOSE packets.

Recommended fix High confidence

V01.401.101

  1. 1. Obtain the firmware version V01.401.101 from the official Schneider Electric download portal at download.schneider-electric.com
  2. 2. Review the firmware release notes and installation instructions provided with the update
  3. 3. Create a backup of the current device configuration before proceeding with the upgrade
  4. 4. Connect to the Easergy P5 device through an authorized management interface
  5. 5. Upload and apply firmware version V01.401.101 following the vendor's documented upgrade procedure
  6. 6. After upgrade completion, verify the device is running firmware version 01.401.101
  7. 7. Confirm that protection functions and GOOSE communication are operating normally
  8. 8. Monitor the device for any anomalies following the upgrade
Caveat Review release notes for any changes to protection settings or GOOSE configuration that may require revalidation after 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
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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