CryptoBotsBattle Integer Overflow Vulnerability

CryptoBotsBattle CBTB is an Ether-based digital currency. An integer overflow vulnerability exists in the 'batchTransfer' function in CBTB's smart contract implementation. An attacker could exploit the vulnerability to create an arbitrary number of tokens for any user...

Integer overflow

An Integer overflow vulnerability exists in the batchTransfer function of a smart contract implementation for CryptoBotsBattle CBTB, an Ethereum token. This vulnerability could be used by an attacker to create an arbitrary amount of tokens for any user...

CVE-2018-17882

Summary: CVE-2018-17882 concerns CryptoBotsBattle (CBTB), an Ethereum token. The flaw is an integer overflow in the smart contract’s batchTransfer function, enabling an attacker to create an arbitrary number of tokens for a user. Concrete details across connected sources confirm the affected comp...

CVE-2018-17882

An Integer overflow vulnerability exists in the batchTransfer function of a smart contract implementation for CryptoBotsBattle CBTB, an Ethereum token. This vulnerability could be used by an attacker to create an arbitrary amount of tokens for any user...

Code injection

The determineWinner function of a smart contract implementation for HashHeroes Tiles, an Ethereum game, uses a certain blockhash value in an attempt to generate a random number for the case where NUMTILES equals the number of people who purchased a tile, which allows an attacker to control the...

CVE-2018-17987

The determineWinner function of a smart contract implementation for HashHeroes Tiles, an Ethereum game, uses a certain blockhash value in an attempt to generate a random number for the case where NUMTILES equals the number of people who purchased a tile, which allows an attacker to control the...

CVE-2018-17987

The determineWinner function of a smart contract implementation for HashHeroes Tiles, an Ethereum game, uses a certain blockhash value in an attempt to generate a random number for the case where NUMTILES equals the number of people who purchased a tile, which allows an attacker to control the...

CVE-2018-17987

HashHeroes Tiles is affected by CVE-2018-17987 in the determineWinner function of its Ethereum smart contract. The vulnerability arises from using a blockhash value to generate a random number when NUM_TILES equals the number of tile Purchases, enabling an attacker to influence the prize by being...

CVE-2018-17877

A lottery smart contract implementation for Greedy 599, an Ethereum gambling game, generates a random value that is predictable via an external contract call. The developer used the extcodesize function to prevent a malicious contract from being called, but the attacker can bypass it by writing t...

CVE-2018-17968

A gambling smart contract implementation for RuletkaIo, an Ethereum gambling game, generates a random value that is predictable by an external contract call. The developer wrote a random function that uses a block timestamp and block hash from the Ethereum blockchain. This can be predicted by...

Code injection

A lottery smart contract implementation for Greedy 599, an Ethereum gambling game, generates a random value that is predictable via an external contract call. The developer used the extcodesize function to prevent a malicious contract from being called, but the attacker can bypass it by writing t...

Code injection

A gambling smart contract implementation for RuletkaIo, an Ethereum gambling game, generates a random value that is predictable by an external contract call. The developer wrote a random function that uses a block timestamp and block hash from the Ethereum blockchain. This can be predicted by...

CVE-2018-17877

A lottery smart contract implementation for Greedy 599, an Ethereum gambling game, generates a random value that is predictable via an external contract call. The developer used the extcodesize function to prevent a malicious contract from being called, but the attacker can bypass it by writing t...

CVE-2018-17877

CVE-2018-17877 concerns a lottery Smart Contract for Greedy 599 (Ethereum). The vulnerability: the contract generates a random value that is predictable through an external contract call. The developer attempted to prevent malicious contracts with extcodesize(), but an attacker can bypass this by...

CVE-2018-17968

CVE-2018-17968 concerns a gambling smart contract for RuletkaIo on Ethereum. The vulnerability arises from a flawed random() function that relies on block timestamp and block hash, enabling an external contract to predict the generated random value. The description notes that an attacker could re...

PolyAI Integer Overflow Vulnerability

PolyAI AI is an ethereum-based virtual currency. The 'mintToken' function in PolyAI's smart contract implementation suffers from an integer overflow vulnerability that can be exploited by an attacker to set the balance of any user to any value...

CVE-2018-12975

The random function of the smart contract implementation for CryptoSaga, an Ethereum game, generates a random value with publicly readable variables such as timestamp, the current block's blockhash, and a private variable which can be read with a getStorageAt call. Therefore, attackers can...

Design/Logic Flaw

The random function of the smart contract implementation for CryptoSaga, an Ethereum game, generates a random value with publicly readable variables such as timestamp, the current block's blockhash, and a private variable which can be read with a getStorageAt call. Therefore, attackers can...

CVE-2018-12975

CVE-2018-12975 concerns CryptoSaga’s smart contract random() function. The vulnerability stems from using publicly readable variables—timestamp, current blockhash—and a private variable readable via getStorageAt—as inputs to random value creation. This allows an attacker to precompute the random ...

CVE-2018-12975

The random function of the smart contract implementation for CryptoSaga, an Ethereum game, generates a random value with publicly readable variables such as timestamp, the current block's blockhash, and a private variable which can be read with a getStorageAt call. Therefore, attackers can...