https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 20:13:35 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-244699 EUVD-2026-244699 https://cve.radiocsirt.org/vuln/euvd-2026-244699 https://cve.radiocsirt.org/vuln/fkie_cve-2024-21629 <p>Rust EVM is an Ethereum Virtual Machine interpreter. In `rust-evm`, a feature called `record_external_operation` 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 `record_external_operation(Write(out_code.len()))`. If `record_external_operation` 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 `record_external_operation` that returns errors. The issue is patched in release 0.41.1. No known workarounds are available.</p> <p>Rust EVM is an Ethereum Virtual Machine interpreter. In `rust-evm`, a feature called `record_external_operation` 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 `record_external_operation(Write(out_code.len()))`. If `record_external_operation` 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 `record_external_operation` that returns errors. The issue is patched in release 0.41.1. No known workarounds are available.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-21629 https://cve.radiocsirt.org/vuln/ghsa-27wg-99g8-2v4v <p><strong>Affected:</strong> crates.io: evm</p> <p>### Impact</p> <p>In `rust-evm`, a feature called `record_external_operation` was introduced, allowing library users to record custom gas changes. This feature can have some bogus interactions with the call stack.</p> <p>In particular, during finalization of a `CREATE` or `CREATE2`, in the case that [the substack execution happens successfully](https://github.com/rust-ethereum/evm/blob/release-v041/src/executor/stack/executor.rs#L1012C25-L1012C69), `rust-evm` will first commit the substate, and then call `record_external_operation(Write(out_code.len()))`. If `record_external_operation` 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).</p> <p>This issue only impacts library users with custom `record_external_operation` that returns errors.</p> <p>### Patches</p> <p>The issue is patched in release 0.41.1. The commit can be seem [here](https://github.com/rust-ethereum/evm/commit/d8991ec727ad0fb64fe9957a3cd307387a6701e4).</p> <p>### Workarounds</p> <p>None.</p> <p>### References</p> <p>Patch PR [#264](https://github.com/rust-ethereum/evm/pull/264).</p> <p><strong>Affected:</strong> crates.io: evm</p> <p>### Impact</p> <p>In `rust-evm`, a feature called `record_external_operation` was introduced, allowing library users to record custom gas changes. This feature can have some bogus interactions with the call stack.</p> <p>In particular, during finalization of a `CREATE` or `CREATE2`, in the case that [the substack execution happens successfully](https://github.com/rust-ethereum/evm/blob/release-v041/src/executor/stack/executor.rs#L1012C25-L1012C69), `rust-evm` will first commit the substate, and then call `record_external_operation(Write(out_code.len()))`. If `record_external_operation` 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).</p> <p>This issue only impacts library users with custom `record_external_operation` that returns errors.</p> <p>### Patches</p> <p>The issue is patched in release 0.41.1. The commit can be seem [here](https://github.com/rust-ethereum/evm/commit/d8991ec727ad0fb64fe9957a3cd307387a6701e4).</p> <p>### Workarounds</p> <p>None.</p> <p>### References</p> <p>Patch PR [#264](https://github.com/rust-ethereum/evm/pull/264).</p> https://cve.radiocsirt.org/vuln/ghsa-27wg-99g8-2v4v https://cve.radiocsirt.org/vuln/gsd-2024-21629 gsd-2024-21629 https://cve.radiocsirt.org/vuln/gsd-2024-21629