CVE-2018-10299
published 2018-04-23CVE-2018-10299: An integer overflow in the batchTransfer function of a smart contract implementation for Beauty Ecosystem Coin (BEC), the Ethereum ERC20 token used in the…
PriorityP272high7.5CVSS 3.0
AVNACLPRNUINSUCNIHAN
ITWEXPLOITVulnCheck KEVInitial access
Exploited in the wild
EPSS
2.78%
84.6th percentile
An integer overflow in the batchTransfer function of a smart contract implementation for Beauty Ecosystem Coin (BEC), the Ethereum ERC20 token used in the Beauty Chain economic system, allows attackers to accomplish an unauthorized increase of digital assets by providing two _receivers arguments in conjunction with a large _value argument, as exploited in the wild in April 2018, aka the "batchOverflow" issue.
Detection & IOCsextracted from sources · hover to see the quote
- →The batchOverflow attack exploits the batchTransfer function of the BECToken (Beauty Ecosystem Coin) ERC-20 smart contract by supplying exactly two _receivers arguments combined with a large _value argument to trigger an integer overflow, resulting in unauthorized token minting. ↗
- →Detection should focus on transactions targeting the BECToken contract's batchTransfer function where the product of the number of receivers and the _value argument overflows a 256-bit integer, resulting in an abnormally large token balance increase (on the order of 10^58 tokens). ↗
- →Post-factum investigation of exploit transactions can be performed by replaying historical transactions against a patched version of the contract and identifying transactions that behave differently (e.g., succeed on the vulnerable contract but are blocked on the patched one), indicating integer overflow exploitation. ↗
- ·The vulnerability is specific to the Beauty Ecosystem Coin (BEC) ERC-20 smart contract's batchTransfer function; other ERC-20 contracts with similar batch transfer patterns using unchecked arithmetic may be analogously vulnerable. ↗
- ·IoCs for Ethereum smart contract attacks operate at the level of blockchain state transitions (blocks, transactions, EVM instructions) rather than traditional host/network artifacts, requiring blockchain-aware forensic tooling such as archive nodes with full history. ↗
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
vulncheck7.5HIGH
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-7g6w-wx5f-p467: An integer overflow in the batchTransfer function of a smart contract implementation for Beauty Ecosystem Coin (BEC), the Ethereum ERC20 token used in
ghsa_unreviewed·2022-05-14
CVE-2018-10299 [HIGH] CWE-190 GHSA-7g6w-wx5f-p467: An integer overflow in the batchTransfer function of a smart contract implementation for Beauty Ecosystem Coin (BEC), the Ethereum ERC20 token used in
An integer overflow in the batchTransfer function of a smart contract implementation for Beauty Ecosystem Coin (BEC), the Ethereum ERC20 token used in the Beauty Chain economic system, allows attackers to accomplish an unauthorized increase of digital assets by providing two _receivers arguments in conjunction with a large _value argument, as exploited in the wild in April 2018, aka the "batchOverflow" issue.
VulnCheck
beauty beauty_ecosystem_coin Integer Overflow or Wraparound
vulncheck·2018·CVSS 7.5
CVE-2018-10299 [HIGH] beauty beauty_ecosystem_coin Integer Overflow or Wraparound
beauty beauty_ecosystem_coin Integer Overflow or Wraparound
An integer overflow in the batchTransfer function of a smart contract implementation for Beauty Ecosystem Coin (BEC), the Ethereum ERC20 token used in the Beauty Chain economic system, allows attackers to accomplish an unauthorized increase of digital assets by providing two _receivers arguments in conjunction with a large _value argument, as exploited in the wild in April 2018, aka the "batchOverflow" issue.
Affected: beauty beauty_ecosystem_coin
Required Action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Exploitation References: https://www.cve.org/CVERecord?id=CVE-2018-10299
Exploit PoC: https://vulncheck.com/xdb/71842891a6c7
No detection rules found.
No public exploits indexed.
arXiv
EtherClue: Digital investigation of attacks on Ethereum smart contracts
arxiv_fulltext·2021-09-02
EtherClue: Digital investigation of attacks on Ethereum smart contracts
frontmatter
EtherClue: Digital investigation of attacks on Ethereum smart contracts
[um]Simon Joseph Aquilina
[email protected]
[unipi,arc]Fran Casino
[email protected]
[um]Mark Vellacor1
[email protected]
[cor1]Corresponding author
[um,umdlt]Joshua Ellul
[email protected]
[unipi,arc]Constantinos Patsakis
[email protected]
[um]Department of Computer Science, University of Malta, Msida, Malta
[umdlt]Centre for Distributed Ledger Technologies, University of Malta, Msida, Malta
[unipi]Department of Informatics, University of Piraeus, 80 Karaoli & Dimitriou str., 18534 Piraeus, Greece
[arc]Information Management Systems Institute, Athena Research Center, Artemidos 6, Marousi 15125, Greece
keywordBlockchain Forensics Ethereum Attacks Indicators of Compromise Ethereum
arXiv
EVMPatch: Timely and Automated Patching of Ethereum Smart Contracts
arxiv_fulltext·2020-10-02
EVMPatch: Timely and Automated Patching of Ethereum Smart Contracts
EVMPatch: Timely and Automated Patching of Ethereum Smart Contracts
[1]^#1
Michael Rodler
University of Duisburg-Essen
Wenting Li
NEC Laboratories Europe
Ghassan O. Karame
NEC Laboratories Europe
Lucas Davi
University of Duisburg-Essen
A slightly shorter version of this paper will be published at USENIX Security Symposium 2021.
## Abstract
Recent attacks exploiting errors in smart contract code had devastating consequences thereby questioning the benefits of this technology.
It is currently highly challenging to fix errors and deploy a patched contract in time.
Instant patching is especially important since smart contracts are always online due to the distributed nature of blockchain systems.
They also manage considerable amounts of assets, which are at risk and often beyond re
https://dasp.co/#item-3https://medium.com/secbit-media/a-disastrous-vulnerability-found-in-smart-contracts-of-beautychain-bec-dbf24ddbc30ehttps://peckshield.com/2018/04/22/batchOverflow/https://support.okex.com/hc/en-us/articles/360002944212-BeautyChain-BEC-Withdrawal-and-Trading-Suspendedhttps://twitter.com/OKEx_/status/987967343983714304https://www.reddit.com/r/ethereum/comments/8esyg9/okex_erc20_bug/https://dasp.co/#item-3https://medium.com/secbit-media/a-disastrous-vulnerability-found-in-smart-contracts-of-beautychain-bec-dbf24ddbc30ehttps://peckshield.com/2018/04/22/batchOverflow/https://support.okex.com/hc/en-us/articles/360002944212-BeautyChain-BEC-Withdrawal-and-Trading-Suspendedhttps://twitter.com/OKEx_/status/987967343983714304https://www.reddit.com/r/ethereum/comments/8esyg9/okex_erc20_bug/
2018-04-23
Published
Exploited in the wild