Token theft via unchecked self-destruct payout target
Published Sep 7, 2021 · Updated Aug 4, 2024
Token theft in the 0xRACER 1.0 smart contract allows attackers to redirect contract balances through a crafted calling contract. The destroycontract() function executes its self-destruct procedure with a caller-selected payout target and does not verify that target against the transaction address. An attacker must cause a victim contract to invoke the function; the resulting payout sends that contract balance to an attacker-controlled address.
Summary
What happened
Token theft in the 0xRACER 1.0 smart contract allows attackers to redirect contract balances through a crafted calling contract. The destroycontract() function executes its self-destruct procedure with a caller-selected payout target and does not verify that target against the transaction address. An attacker must cause a victim contract to invoke the function; the resulting payout sends that contract balance to an attacker-controlled address.
The record
- CVE
- CVE-2020-19767
- Published
- Sep 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1657
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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
Public exploit references
- 0xRACER destroycontract exploit write-upproof 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