RPC result corruption via u8 length summation
Published Aug 19, 2022 · Updated Apr 23, 2025
Integer overflow in Frontier's EVM revert-reason RPC parser allows remote authenticated users to receive incorrectly parsed exit reasons. The parser sums the 32-byte, big-endian U256 string-length field into a u8 rather than decoding it, so lengths above 255 wrap or panic. Exposure requires RPC use and matters to bridge nodes that distinguish reversion exit reasons; release builds return the wrong reason, while debug builds crash.
Summary
What happened
Integer overflow in Frontier's EVM revert-reason RPC parser allows remote authenticated users to receive incorrectly parsed exit reasons. The parser sums the 32-byte, big-endian U256 string-length field into a u8 rather than decoding it, so lengths above 255 wrap or panic. Exposure requires RPC use and matters to bridge nodes that distinguish reversion exit reasons; release builds return the wrong reason, while debug builds crash.
The record
- CVE
- CVE-2022-36008
- Published
- Aug 19, 2022
- Updated
- Apr 23, 2025
- Vendor
- Parity Technologies
- Product
- Frontier
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< commit fff8cc43b7756ce3979a38fc473f38e6e24ac451
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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