dbcve.org
Easergy P3 FirmwareOperating system · Schneider Electric

CVE-2022-22725

HIGH · 8.8 CVSS v3.1 Published 2022-02-04
Fix available
A fix is available. Upgrade to 30.205 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 P3 (All versions prior to V30.205)

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 CWE-120 buffer overflow vulnerability exists in the Easergy P3 protection relay that allows remote attackers to send specially crafted network packets which overflow a buffer, potentially causing program crashes and arbitrary code execution. The vulnerability specifically impacts protection and tripping functions via the GOOSE (IEC 61850) protocol.

MitigationUpgrade Easergy P3 firmware to version V30.205 or later. As a compensating control, isolate the device behind a firewall and restrict network access to minimize exposure to untrusted 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 P3 FirmwareOperating system
Affected:< 30.205

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 P3 device identity
    Locate the physical device or access its management interface to verify the model is Schneider Electric Easergy P3 protection relay
    Affected if The device is not an Easergy P3 relay
  2. Check installed firmware version
    Access the device web interface, console, or management software and locate the firmware version information. Compare it against the affected range of versions prior to 30.205
    Affected if Firmware version is below 30.205 (e.g., 30.100, 30.101, etc.)
  3. Verify GOOSE protocol configuration
    Access the device settings or IEC 61850 configuration and determine whether the GOOSE (Generic Object Oriented Substation Event) protocol is enabled
    Affected if GOOSE protocol is enabled and configured for protection/tripping functions
  4. Assess network exposure
    Review network topology and firewall rules to determine if the device is accessible from untrusted networks or if it can receive packets from non-segmented network segments
    Affected if Device is reachable from untrusted networks without firewall filtering

A user is affected if they have an Easergy P3 relay running firmware below version 30.205 with GOOSE protocol enabled and the device is network-accessible to untrusted attackers.

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 30.205 or later
Fixed in 30.205
Interim mitigation

Upgrade Easergy P3 firmware to version V30.205 or later. As a compensating control, isolate the device behind a firewall and restrict network access to minimize exposure to untrusted packets.

Recommended fix High confidence

V30.205 or later

  1. Download firmware version 30.205 or later from Schneider Electric's official support portal (download.schneider-electric.com)
  2. Consult Schneider Electric Easergy P3 firmware upgrade documentation for device-specific instructions
  3. Follow the official firmware update procedure for your Easergy P3 device, ensuring proper backup of current configuration
  4. Verify the firmware upgrade was successful by checking the device version
  5. Test protection functions and GOOSE communications to confirm normal operation
  6. Ensure the device is properly re-secured post-upgrade (restrict network access, enable appropriate security settings)
Caveat Review Schneider Electric release notes for any configuration or compatibility changes between your current version and V30.205

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

Fix this in Easergy P3 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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