CVE Details
Basic Information
| Title | Polkadot Frontier’s constructing smart contract can bypass precompile address bounding |
|---|---|
| Type | cve |
| Published | 2025-07-28T20:34:56.710Z |
| Modified | 2025-07-28T20:46:59.149Z |
Product Information
| Vendor | polkadot-evm |
|---|---|
| Product | frontier |
| Version | < 0822030 |
CVSS Information
| Base Score | 6.9 (MEDIUM) |
|---|---|
| Attack Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |
Affected Products
- polkadot-evm frontier < 0822030
Additional Information
| CWE List | CWE-704 |
|---|---|
| Source | GitHub_M |
Description
Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. There are various account address types in Frontier, e.g. precompiled contracts, smart contracts, and externally owned accounts. Some EVM mechanisms should be unreachable by certain types of accounts for safety. For precompiles to be callable by smart contracts they must be explicitly configured as CallableByContract. If this configuration is absent, then the precompile should be unreachable via smart contract accounts. In commits prior to 0822030, the underlying implementation of CallableByContract which returned the AddressType was incorrect. It considered the contract address running under CREATE or CREATE2 to be AddressType::EOA rather than correctly as AddressType::Contract. The issue only affects users who use custom precompile implementations that utilize AddressType::EOA and AddressType::Contract. It’s not directly exploitable in any of the predefined precompiles in Frontier. This is fixed in version 0822030.