Ether theft via transaction-state reentrancy
Published Jan 19, 2024 · Updated May 30, 2025
Reentrancy in MultiSigWallet at 0xF0C99 allows attackers to execute a confirmed transaction repeatedly through a malicious callback. The executeTransaction function calls an attacker-controlled destination, and a reentrant callback causes incorrect resetting of the transaction's executed flag. The attack requires a confirmed transaction targeting a malicious contract; repeated execution drains Ether from the wallet.
Summary
What happened
Reentrancy in MultiSigWallet at 0xF0C99 allows attackers to execute a confirmed transaction repeatedly through a malicious callback. The executeTransaction function calls an attacker-controlled destination, and a reentrant callback causes incorrect resetting of the transaction's executed flag. The attack requires a confirmed transaction targeting a malicious contract; repeated execution drains Ether from the wallet.
The record
- CVE
- CVE-2023-47033
- Published
- Jan 19, 2024
- Updated
- May 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2024CVE publishedPublication date reported by the CVE source.
- May 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- MultiSigWallet reentrancy attack procedureproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo