LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34756: A CWE-120: Buffer Copy without Checking Size of Input vulnerability exists that could result in remote code...

A CWE-120: Buffer Copy without Checking Size of Input vulnerability exists that could result in remote code execution or the crash of HTTPs stack which is used for the device Web HMI. Affected Products: Easergy P5 (V01.401.102 and prior)

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects Schneider Electric Easergy P5 devices running firmware V01.401.102 and prior. A flaw in the device Web HMI HTTPS stack could allow remote code execution or crash the stack, creating confidentiality, integrity, and availability risk for protection relay environments.

Executive priority

Treat as high priority for environments using Easergy P5 because exploitation could affect control-system confidentiality, integrity, and availability. Prioritize asset discovery, exposure reduction, and vendor-guided remediation.

Technical view

CVE-2022-34756 is a CWE-120 buffer copy issue in the HTTPS stack used by Easergy P5 Web HMI. CVSS 3.1 is 8.8 with adjacent-network access, low complexity, no privileges, and no user interaction required. The bundle names Easergy P5 firmware V01.401.102 and prior as affected.

Likely exposure

Exposure is most likely where Easergy P5 Web HMI HTTPS access is reachable from adjacent operational or management networks. The bundle does not indicate internet exposure requirements or affected CPEs.

Exploitation context

The provided data does not show CISA KEV listing or cited evidence of active exploitation. Impact could include remote code execution or HTTPS stack crash, but no exploit maturity or public exploitation detail is provided.

Researcher notes

Evidence is limited to the CVE metadata and Schneider advisory reference. Do not assume affected versions beyond Easergy P5 firmware V01.401.102 and prior, and do not claim active exploitation without additional sourced evidence.

Mitigation direction

  • Check Schneider Electric advisory SEVD-2022-193-04 for official remediation guidance.
  • Identify and prioritize Easergy P5 devices running firmware V01.401.102 or prior.
  • Restrict Web HMI HTTPS access to trusted management paths only.
  • Monitor affected devices for unexpected HTTPS stack crashes or instability.
  • Validate any firmware or configuration change against operational safety requirements.

Validation and detection

  • Inventory Easergy P5 firmware versions across OT and substation environments.
  • Compare detected versions with V01.401.102 and prior affected range.
  • Confirm Web HMI HTTPS reachability from adjacent networks and management zones.
  • Review Schneider advisory for fixed versions or compensating controls.
  • Document remediation status per device, site, and operational owner.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-120: 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 lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-34756 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-34756Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Schneider ElectricEasergy P5FirmwareListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.