CVE-2018-12078

The CVE-2018-12078 entry describes a vulnerability in the mintToken function of PolyAI (AI), an ERC20 smart contract, where there is no period constraint. This allows the owner to arbitrarily increase the total supply, enabling profit through dilution. The provided documents do not include exploi...

CVE-2018-12084

The CVE-2018-12084 case concerns BitAsean (BAS), a tradable Ethereum ERC20 token. The vulnerability resides in the smart-contract mintToken function, which has no period/expiration constraint, enabling the owner to arbitrarily inflate the total supply and profit. Documents confirm the issue as th...

CVE-2018-12083

The CVE-2018-12083 entry concerns GOAL Bonanza (GOAL), an Ethereum ERC20 token whose smart-contract mintToken function has no period constraint, enabling the owner to arbitrarily increase total supply. This minting oversight creates a supply manipulation risk described as the tradeTrap. Affected ...

CVE-2018-12082

The CVE-2018-12082 entry concerns Fujinto (NTO) ERC20 token smart contract where the mintToken function has no period constraint. This allows the owner to arbitrarily increase total supply, enabling profit by altering supply. Connected sources corroborate the same description across NVD/CNVD/PRIO...

CVE-2018-11446

CVE-2018-11446 describes a tradeTrap in the Gold Reward (GRX) ERC20 contract where the buy() path multiplies amount by buyPrice without SafeMath, enabling an overflow that can trap funds. The owner can set buyPrice via setPrices(), potentially manipulating prices and enabling arbitrage-like explo...

CVE-2018-12067

Summary: CVE-2018-12067 affects Substratum (SUB), an Ethereum ERC20 token. Multiple sources describe a vulnerability in the tradeTrap mechanism: the sell function can overflow due to the multiplication of the input amount and a manipulable variable sellPrice, enabling a potential financial loss t...

CVE-2018-12079

CVE-2018-12079 affects Substratum (SUB) ERC20 token contracts. The mintToken function lacks a period constraint, allowing the owner to arbitrarily increase total supply (tradeTrap), enabling potential profit extraction. Documented impact indicates ability to inflate supply without explicit period...

CVE-2018-12084

The mintToken function of a smart contract implementation for BitAsean BAS, a tradable Ethereum ERC20 token, has no period constraint, which allows the owner to increase the total supply of the digital assets arbitrarily so as to make profits, aka the "tradeTrap" issue...

CVE-2018-12081

CVE-2018-12081 affects the Target Coin (TGT) ERC20 token. The mintToken function has no period constraint, allowing the owner to arbitrarily increase total supply, enabling profit via inflation of assets. The vulnerability is defined in the NVD description and corroborated by multiple feeds; no e...

CVE-2018-12079

The mintToken function of a smart contract implementation for Substratum SUB, a tradable Ethereum ERC20 token, has no period constraint, which allows the owner to increase the total supply of the digital assets arbitrarily so as to make profits, aka the "tradeTrap" issue...

CVE-2018-12068

The sell function of a smart contract implementation for Target Coin TGT, a tradable Ethereum ERC20 token, allows a potential trap that could be used to cause financial damage to the seller, because of overflow of the multiplication of its argument amount and a manipulable variable sellPrice, aka...

CVE-2018-12062

The sell function of a smart contract implementation for SwftCoin SWFTC, a tradable Ethereum ERC20 token, allows a potential trap that could be used to cause financial damage to the seller, because of overflow of the multiplication of its argument amount and a manipulable variable sellPrice, aka...

CVE-2018-12083

The mintToken function of a smart contract implementation for GOAL Bonanza GOAL, a tradable Ethereum ERC20 token, has no period constraint, which allows the owner to increase the total supply of the digital assets arbitrarily so as to make profits, aka the "tradeTrap" issue...

CVE-2018-12078

The mintToken function of a smart contract implementation for PolyAI AI, a tradable Ethereum ERC20 token, has no period constraint, which allows the owner to increase the total supply of the digital assets arbitrarily so as to make profits, aka the "tradeTrap" issue...

CVE-2018-12067

The sell function of a smart contract implementation for Substratum SUB, a tradable Ethereum ERC20 token, allows a potential trap that could be used to cause financial damage to the seller, because of overflow of the multiplication of its argument amount and a manipulable variable sellPrice, aka...

CVE-2018-12080

The mintToken function of a smart contract implementation for Internet Node Token INT, a tradable Ethereum ERC20 token, has no period constraint, which allows the owner to increase the total supply of the digital assets arbitrarily so as to make profits, aka the "tradeTrap" issue...

CVE-2018-11446

The buy function of a smart contract implementation for Gold Reward GRX, an Ethereum ERC20 token, allows a potential trap that could be used to cause financial damage to the buyer because of overflow of the multiplication of its argument amount and a manipulable variable buyPrice, aka the...

Design/Logic Flaw

The approveAndCallcode function of a smart contract implementation for Block 18 18T, an tradable Ethereum ERC20 token, allows attackers to steal assets e.g., transfer the contract's balances into their account because the callcode i.e., spender.callextraData is not verified, aka the "evilReflex"...

CVE-2018-12702

The approveAndCallcode function of a smart contract implementation for Globalvillage ecosystem GVE, an Ethereum ERC20 token, allows attackers to steal assets e.g., transfer the contract's balances into their account because the callcode i.e., spender.callextraData is not verified, aka the...

Design/Logic Flaw

The approveAndCallcode function of a smart contract implementation for Globalvillage ecosystem GVE, an Ethereum ERC20 token, allows attackers to steal assets e.g., transfer the contract's balances into their account because the callcode i.e., spender.callextraData is not verified, aka the...