Security readout for executives and security teams
Plain-English summary
Frontier's EVM compatibility layer could show one transfer value while moving a different underlying Substrate amount because balance truncation was wrong. For organizations running affected Frontier commits, this is an integrity issue around EVM-accounting accuracy, not a node takeover or Substrate balance compromise according to the advisory.
Executive priority
Treat as a time-sensitive integrity issue for Frontier-based chains with EVM enabled. It is not described as critical infrastructure compromise, but incorrect transfer accounting can create financial and trust impact, so upgrade or pause EVM execution promptly.
Technical view
Affected Frontier commits incorrectly truncated values when converting between EVM balance types and Substrate balance types. This can create a discrepancy between the displayed EVM transfer value and the actual Substrate value transferred. Sources identify fixes in Frontier master commit fed5e0a9577c10bea021721e8c2c5c378e16bf66 and polkadot-v0.9.22 commit e3e427fa2e5d1200a784679f8015d4774cedc934.
Likely exposure
Exposure is limited to deployments using ParityTech Frontier before the named fix commits, especially chains with EVM execution enabled. The source states the issue affects EVM internal state, not Substrate balance state or the node itself.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. The risk is unauthorized integrity impact through value discrepancies in EVM transfer handling, but the bundle does not provide evidence of public weaponization.
Researcher notes
Focus review on EVM-to-Substrate balance conversion and truncation behavior before the fix commits. The advisory explicitly limits impact to EVM internal states, so avoid broad claims about node compromise, Substrate balance corruption, or confirmed exploitation without additional evidence.
Mitigation direction
- Plan an emergency upgrade to a Frontier build containing the named fix commits.
- Apply the patched master or polkadot-v0.9.22 branch commit, as applicable.
- Temporarily pause EVM execution until patched.
- Use a Substrate CallFilter to disable pallet-evm and pallet-ethereum calls if unpatched.
- Check ParityTech advisory updates before resuming normal EVM operation.
Validation and detection
- Inventory Frontier commit hashes across all affected chain runtimes.
- Confirm deployed code includes fed5e0a9577c10bea021721e8c2c5c378e16bf66 or e3e427fa2e5d1200a784679f8015d4774cedc934.
- Verify whether pallet-evm and pallet-ethereum calls remain enabled on unpatched runtimes.
- Review recent EVM transfers for unexplained displayed-versus-actual value discrepancies.
- Confirm Substrate balance state remains consistent after remediation.
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-670: 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-31111 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
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/paritytech/frontier/security/advisories/GHSA-hc8w-mx86-9fcjCVE reference · x_refsource_CONFIRM
- https://github.com/paritytech/frontier/pull/753CVE reference · x_refsource_MISC
- https://github.com/paritytech/frontier/commit/e3e427fa2e5d1200a784679f8015d4774cedc934CVE reference · x_refsource_MISC
- https://github.com/paritytech/frontier/commit/fed5e0a9577c10bea021721e8c2c5c378e16bf66CVE reference · x_refsource_MISC
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.
Always-Incorrect Control Flow Implementation
Always-Incorrect Control Flow Implementation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.