Security readout for executives and security teams
Plain-English summary
CVE-2022-34757 affects Schneider Electric Easergy P5 devices. Weak SSH cipher suites may be used between Easergy Pro software and the device, potentially exposing protected communication details to an attacker with adjacent network access. The issue is medium severity, but it matters in operational environments because integrity and availability impacts are rated high.
Executive priority
Prioritize for environments using Easergy P5 in operational technology networks. This is not presented as internet-scale or actively exploited, but weak management-channel cryptography can undermine trust in sensitive device communications.
Technical view
The vulnerability is CWE-327 in Easergy P5 firmware V01.401.102 and prior. The CVSS 3.1 vector is AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H, score 6.7. Sources describe weak SSH cryptography between Easergy Pro and the device, enabling observation of protected communication details under constrained conditions.
Likely exposure
Exposure is likely limited to organizations running Schneider Electric Easergy P5 firmware V01.401.102 or earlier where Easergy Pro communicates with devices over reachable adjacent networks.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation appears constrained by adjacent network access, high attack complexity, and required user interaction, but affected systems may be operationally important.
Researcher notes
Do not assume broader Schneider Electric product exposure from this bundle. The named affected product is Easergy P5 firmware V01.401.102 and prior. Public evidence provided does not include exploit details, active exploitation, or specific patch version text.
Mitigation direction
- Review Schneider Electric security notification SEVD-2022-193-04 for vendor remediation guidance.
- Inventory Easergy P5 devices and identify firmware versions V01.401.102 or earlier.
- Apply Schneider Electric-recommended firmware or configuration updates where available.
- Restrict Easergy Pro-to-device management paths to trusted, monitored networks.
- Treat exposed adjacent-network management access as higher priority until remediated.
Validation and detection
- Confirm whether Easergy P5 devices are deployed in the environment.
- Record firmware versions and flag V01.401.102 or earlier as affected.
- Verify Easergy Pro communication paths are limited to authorized management networks.
- Check whether Schneider Electric remediation from SEVD-2022-193-04 has been applied.
- Document residual devices awaiting vendor-approved remediation or compensating controls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-34757 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H1.25.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.7MediumVector: CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.