Skip to content

Incorrect parsing of EVM reversion exit reason in RPC

Moderate severity GitHub Reviewed Published Aug 15, 2022 in polkadot-evm/frontier • Updated Jan 31, 2023

Package

cargo frontier (Rust)

Affected versions

<= 0.1.0

Patched versions

None

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 polkadot-evm/frontier#820

Workarounds

None.

References

PR polkadot-evm/frontier#820

For more information

If you have any questions or comments about this advisory:

References

@sorpaas sorpaas published to polkadot-evm/frontier Aug 15, 2022
Published to the GitHub Advisory Database Aug 18, 2022
Reviewed Aug 18, 2022
Published by the National Vulnerability Database Aug 19, 2022
Last updated Jan 31, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.097%
(41st percentile)

Weaknesses

CVE ID

CVE-2022-36008

GHSA ID

GHSA-mjvm-mhgc-q4gp

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.