Schneider Electric
Easergy P5
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2022-34758 | 13 Jul 2022 | Firmware < V01.401.102 | V01.402.101 of the Easergy P5 firmware includes a fix for these vulnerabilities and is available on request from Schneider Electric’s Customer Care Center. | Update reference ↗ |
| CVE-2022-34757 | 13 Jul 2022 | Firmware < V01.401.102 | V01.402.101 of the Easergy P5 firmware includes a fix for these vulnerabilities and is available on request from Schneider Electric’s Customer Care Center. | Update reference ↗ |
| CVE-2022-34756 | 13 Jul 2022 | Firmware < V01.401.102 | V01.402.101 of the Easergy P5 firmware includes a fix for these vulnerabilities and is available on request from Schneider Electric’s Customer Care Center. | Update reference ↗ |
| CVE-2022-22722 | 4 Feb 2022 | unspecified < 01.401.101 | For CVE-2022-22723 only, if customers choose not to apply the remediation provided above, they should immediately apply the following mitigation to reduce the risk of exploit: Disable the GOOSE service of the product to reduce the risk of exposure. If GOOSE is needed for the application use it only in a secure local area network. Customers should use appropriate patching methodologies when applying these patches to their systems. We strongly recommend the use of back-ups and evaluating the impact of these patches in a Test and Development environment or on an offline infrastructure. Contact Schneider Electric’s Customer Care Center if you need assistance removing a patch. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.