CVE-2022-36008 is a high-severity (CVSS 7.1) CWE-190 vulnerability in fc-rpc. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Message length overflow in frontier
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36008.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
fc-rpcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A low severity security issue was discovered affecting parsing of the RPC result of the exit reason in case of EVM reversion. In release build, this would cause the exit reason being incorrectly parsed and returned by RPC. In debug build, this would cause an overflow panic.
No action is needed unless you have a bridge node that needs to distinguish different reversion exit reasons and you used RPC for this.
Patches
The issue is patched in https://github.com/paritytech/frontier/pull/820
Workarounds
None.
References
PR https://github.com/paritytech/frontier/pull/820
For more information
If you have any questions or comments about this advisory:
- Email Wei Tang
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | fc-rpc | all versions | No fix |
Affected Products
frontierparityDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fc-rpc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of fc-rpc for CVE-2022-36008. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Frequently Asked Questions
Is CVE-2022-36008 in your dependencies?
Find it across crates.io, including transitive dependencies.