Rust EVM erroneousle handles record_external_operation error return

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2024-21629: 0.58% estimated exploitation activity in the next 30 days; percentile 47.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact In rust-evm, a feature called recordexternaloperation was introduced, allowing library users to record custom gas changes. This feature can have some bogus interactions with the call stack. In particular, during finalization of a CREATE or CREATE2, in the case that the substack execution happens successfully, rust-evm will first commit the substate, and then call recordexternaloperation(Write(outcode.len())). If recordexternaloperation later fails, this error is returned to the parent call stack, instead of Succeeded. Yet, the substate commitment already happened. This causes smart contracts able to commit state changes, when the parent caller contract receives zero address (which usually indicates that the execution has failed). This issue only impacts library users with custom recordexternaloperation that returns errors. Patches The issue is patched in release 0.41.1. The commit can be seem here. Workarounds None. References Patch PR #264.

Published by the source

3 Jan 2024, 21:48 UTC

Last modified by the source

3 Jan 2024, 21:48 UTC

Source last checked

26 Oct 2026, 15:37 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-27wg-99g8-2v4v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-21629

Advisory: Rust EVM erroneousle handles `record_external_operation` error return
IDs: CVE-2024-21629, GHSA-27wg-99g8-2v4v
Record: https://patchnext.com/advisories/cve-2024-21629 (revision 1, source checked 26 Oct 2026, 15:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: evm 0.41.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io evm: affected <= 0.41.0; fixed in 0.41.1

## Suggested inspection (read-only)
- crates.io evm: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on evm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-27wg-99g8-2v4v (GitHub-reviewed advisory GHSA-27wg-99g8-2v4v lists affected ranges: crates.io evm >=0 <=0.41.0)

Commands are suggestions: review each one before running it.