We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2025-54429

Polkadot Frontier's constructing smart contract can bypass precompile address bounding



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.

Reserved 2025-07-21 | Published 2025-07-28 | Updated 2025-07-28 | Assigner GitHub_M


MEDIUM: 6.9CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Problem types

CWE-704: Incorrect Type Conversion or Cast

Product status

< 0822030
affected

References

github.com/...ontier/security/advisories/GHSA-fr62-ppwc-mc2h

github.com/polkadot-evm/frontier/pull/1655

dotpal.io/...rlabs-2505-718c3bfa5df9fed1862fed05de506859.pdf

cve.org (CVE-2025-54429)

nvd.nist.gov (CVE-2025-54429)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2025-54429

Support options

Helpdesk Chat, Email, Knowledgebase