Skip to content

Transaction validity oversight in pallet-ethereum

Moderate severity GitHub Reviewed Published Sep 1, 2021 in polkadot-evm/frontier • Updated Oct 24, 2024

Package

cargo pallet-ethereum (Rust)

Affected versions

<= 3.0.0

Patched versions

None

Description

Impact

A bug in pallet-ethereum can cause invalid transactions to be included in the Ethereum block state in pallet-ethereum due to not validating the input data size. Any invalid transactions included this way have no possibility to alter the internal Ethereum or Substrate state. The transaction will appear to have be included, but is of no effect as it is rejected by the EVM engine. The impact is further limited by Substrate extrinsic size constraints.

Patches

Patches are applied in PR #465.

Workarounds

None.

References

Patch PR: polkadot-evm/frontier#465

For more information

If you have any questions or comments about this advisory:

References

@sorpaas sorpaas published to polkadot-evm/frontier Sep 1, 2021
Reviewed Sep 1, 2021
Published to the GitHub Advisory Database Sep 1, 2021
Published by the National Vulnerability Database Sep 3, 2021
Last updated Oct 24, 2024

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.131%
(49th percentile)

Weaknesses

CVE ID

CVE-2021-39193

GHSA ID

GHSA-hw4v-5x4h-c3xm

Source code

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