Security readout for executives and security teams
Plain-English summary
Enbra EWM can accept replayed wireless meter data as if it were fresh. This can make old readings appear current because the system uses the readout time rather than detecting that the sensor data was reused. The business risk is incorrect operational or billing decisions based on manipulated meter integrity, not data theft or service outage.
Executive priority
Prioritize assessment where EWM readings influence billing, compliance reporting, energy operations, or customer trust. This is a data-integrity issue with localized attack requirements, so urgency depends on how directly meter readings drive financial or operational decisions.
Technical view
CVE-2021-34572 is CWE-345 in Enbra EWM 1.7.29, version 03.11.2019. The software does not detect replayed wireless M-Bus Security mode 5 device data and replaces sensor timestamps with readout time. CVSS 3.1 is 6.5 with adjacent-network attack vector and high integrity impact.
Likely exposure
Exposure appears limited to organizations using Enbra EWM 1.7.29 with wireless M-Bus Security mode 5 devices. The CVE source bundle does not identify other Enbra products, cloud services, or later versions as affected.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The attack vector is adjacent, so risk is highest where an attacker can interact with local wireless M-Bus communications.
Researcher notes
The public record names one affected product/version and describes replay acceptance, but does not provide a vendor patch, exploit status, or broad product matrix. Avoid extrapolating beyond Enbra EWM 1.7.29 and wireless M-Bus Security mode 5 contexts.
Mitigation direction
- Identify whether Enbra EWM 1.7.29 version 03.11.2019 is deployed.
- Check Enbra or system integrator guidance for updates, replacements, or compensating controls.
- Treat affected meter readings as integrity-sensitive until replay detection is confirmed.
- Reconcile EWM readings against independent operational or billing records.
- Restrict physical and radio proximity access around affected metering environments.
Validation and detection
- Inventory EWM installations and record exact software version and deployment role.
- Confirm whether wireless M-Bus Security mode 5 devices feed the system.
- Review whether sensor timestamps are preserved or overwritten during readout.
- Check for repeated or stale readings presented as current values.
- Ask the vendor whether the deployed build detects replayed device data.
Public sources used
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-345: 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-2021-34572 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.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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:L/PR:N/UI:N/S:U/C:N/I:H/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.fit.vutbr.cz/~polcak/CVE-2021-34572.enCVE reference · x_refsource_CONFIRM
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.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.