Account takeover via unprotected ownership assignment
Published Aug 3, 2021 · Updated Aug 4, 2024
Improper access control in the RobotCoin smart contract allows remote attackers to seize ownership and increase the RBTC supply. The public owned() function assigns msg.sender to the owner variable without checking the caller or restricting repeated invocation. Any blockchain participant able to submit a transaction can invoke the function without prior privileges, gaining owner-only authority to mint additional tokens.
Summary
What happened
Improper access control in the RobotCoin smart contract allows remote attackers to seize ownership and increase the RBTC supply. The public owned() function assigns msg.sender to the owner variable without checking the caller or restricting repeated invocation. Any blockchain participant able to submit a transaction can invoke the function without prior privileges, gaining owner-only authority to mint additional tokens.
The record
- CVE
- CVE-2021-34272
- Published
- Aug 3, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 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
No sourced classifications are available.
Public exploit references
- RobotCoin ownership-takeover demonstrationproof of concept · demonstrated
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