Invalid block inclusion via omitted execution validation
Published Oct 13, 2021 · Updated Aug 4, 2024
Improper input validation in Frontier before commit 146bb48 allows attackers controlling validators to include invalid transactions in blocks. The pallet-ethereum signed-extrinsic path performed transaction checks during pool validation but omitted them during block execution. Control of a validator is required; signatures remain checked, while the gap permits chain-ID replay and bounded transaction spam.
Summary
What happened
Improper input validation in Frontier before commit 146bb48 allows attackers controlling validators to include invalid transactions in blocks. The pallet-ethereum signed-extrinsic path performed transaction checks during pool validation but omitted them during block execution. Control of a validator is required; signatures remain checked, while the gap permits chain-ID replay and bounded transaction spam.
The record
- CVE
- CVE-2021-41138
- Published
- Oct 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Parity Technologies
- Product
- Frontier
- Classifications
- CWE-20, T1565.001
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 146bb48
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo