Cryptocurrency theft via unchecked token issuer
Published May 12, 2022 · Updated Aug 3, 2024
Access-control failure in EOSIO batdappboomx 327c04cf allows remote attackers to obtain cryptocurrency through crafted transfer calls. The transfer dispatcher invokes the payment handler without checking that the caller is the official eosio.token issuer. An attacker-controlled EOSIO account can call transfer@batdappboomx with memo action:buy, causing the contract to pay a reward despite receiving no ticket fee.
Summary
What happened
Access-control failure in EOSIO batdappboomx 327c04cf allows remote attackers to obtain cryptocurrency through crafted transfer calls. The transfer dispatcher invokes the payment handler without checking that the caller is the official eosio.token issuer. An attacker-controlled EOSIO account can call transfer@batdappboomx with memo action:buy, causing the contract to pay a reward despite receiving no ticket fee.
The record
- CVE
- CVE-2022-27134
- Published
- May 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- CVE-batdappboomx poc.pyproof 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