Arbitrary token transfer via tx.origin authorization
Published Jun 24, 2021 · Updated Aug 4, 2024
Authorization bypass in the RC Ethereum token smart contract allows attackers to transfer arbitrary token amounts to arbitrary addresses. addMeByRC trusts tx.origin to identify the owner, so a malicious intermediary contract invoked by that owner becomes authorized as an RC contract. Exploitation requires the token-sale owner to invoke an attacker-controlled contract, after which its claim call transfers tokens.
Summary
What happened
Authorization bypass in the RC Ethereum token smart contract allows attackers to transfer arbitrary token amounts to arbitrary addresses. addMeByRC trusts tx.origin to identify the owner, so a malicious intermediary contract invoked by that owner becomes authorized as an RC contract. Exploitation requires the token-sale owner to invoke an attacker-controlled contract, after which its claim call transfers tokens.
The record
- CVE
- CVE-2020-17753
- Published
- Jun 24, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 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
- Phishing contract proof of conceptproof 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