What is CVE-2022-36008?

CVE-2022-36008 is a medium-severity integer overflow or wraparound vulnerability in fc-rpc (rust), affecting versions <= 1.0.0. No fixed version is listed yet. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.

How severe is CVE-2022-36008?

CVE-2022-36008 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of fc-rpc are affected by CVE-2022-36008?

fc-rpc (rust) versions <= 1.0.0 is affected.

Is there a fix for CVE-2022-36008?

No fixed version is listed for CVE-2022-36008 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2022-36008 exploitable, and should I be worried?

Whether CVE-2022-36008 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-36008 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-36008?

No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use checked arithmetic or integer types that enforce bounds.

CVE-2022-36008 in fc-rpc

Q: How severe is CVE-2022-36008?

CVE-2022-36008 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of fc-rpc are affected by CVE-2022-36008?

fc-rpc (rust) versions <= 1.0.0 is affected.

Q: Is there a fix for CVE-2022-36008?

No fixed version is listed for CVE-2022-36008 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2022-36008 exploitable, and should I be worried?

Whether CVE-2022-36008 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-36008 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-36008?

No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use checked arithmetic or integer types that enforce bounds.

Summary

Incorrect parsing of EVM reversion exit reason in RPC

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

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.

An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.

CVE-2022-36008 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

fc-rpc (<= 1.0.0)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue is patched in https://github.com/paritytech/frontier/pull/820

Frequently Asked Questions

What is CVE-2022-36008? CVE-2022-36008 is a medium-severity integer overflow or wraparound vulnerability in fc-rpc (rust), affecting versions <= 1.0.0. No fixed version is listed yet. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
How severe is CVE-2022-36008? CVE-2022-36008 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of fc-rpc are affected by CVE-2022-36008? fc-rpc (rust) versions <= 1.0.0 is affected.
Is there a fix for CVE-2022-36008? No fixed version is listed for CVE-2022-36008 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2022-36008 exploitable, and should I be worried? Whether CVE-2022-36008 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-36008 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-36008? No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use checked arithmetic or integer types that enforce bounds.