Skip to content
Fencer Vulns
high 8.8

CVE-2022-22725 json

A CWE-120: Buffer Copy without Checking Size of Input vulnerability exists that could lead to a buffer overflow causing program crashes and…

published 2022-02-04 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-27868

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

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)

Patch / fix

  • schneider-electric easergy_p3_firmware 30.205

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-055-03 updated cvss 8.8

Schneider Electric Easergy P5 and P3

  • Schneider Electric Software, LLC Easergy P3 < 30.205 Schneider Electric Software, LLC Easergy P5 All firmware < 01.401.102
    affected: mitigation “For CVE-2022-22723 and CVE-2022-22725 only, if users choose not to apply the remediation provided above, they should immediately apply the following mitigation to reduce the risk of exploit:” se.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

2.79% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 8.3 AV:A/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • n/a Easergy P3 (All versions prior to V30.205)

Classification

Weakness
  • CWE-120 Buffer Copy without Checking Size of Input

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.