5626 matches found
CVE-2018-10705
The Owned smart contract implementation for Aurora DAO AURA, an Ethereum ERC20 token, allows attackers to acquire contract ownership because the setOwner function is declared as public. An attacker can then conduct a lockBalances denial of service attack...
CVE-2018-10705
CVE-2018-10705 affects Aurora DAO (AURA) Ethereum ERC20 token. The Owned contract’s setOwner() is public and unprotected, allowing an attacker to acquire contract ownership. Once ownership is changed, privileged functions like lockBalances() can be called, enabling a Denial-of-Service (DoS) by pr...
CVE-2018-10705
The Owned smart contract implementation for Aurora DAO AURA, an Ethereum ERC20 token, allows attackers to acquire contract ownership because the setOwner function is declared as public. An attacker can then conduct a lockBalances denial of service attack...
Threat Outbreak Alert RuleID32722: Email Messages Distributing Malicious Software on May 8, 2018
Medium Alert ID: 57826 First Published: 2018 May 8 16:28 GMT Version: 1 Summary Cisco Security has detected significant activity related to spam email messages distributing malicious software. Email messages that are related to this threat RuleID32722 may contain the following files: Name | Size ...
Code injection
The Owned smart contract implementation for Aurora IDEX Membership IDXM, an Ethereum ERC20 token, allows attackers to acquire contract ownership because the setOwner function is declared as public. A new owner can subsequently modify variables...
CVE-2018-10666
The Owned smart contract implementation for Aurora IDEX Membership IDXM, an Ethereum ERC20 token, allows attackers to acquire contract ownership because the setOwner function is declared as public. A new owner can subsequently modify variables...
CVE-2018-10666
CVE-2018-10666 concerns the Owned smart contract implementation of Aurora IDEX Membership (IDXM). The vulnerability arises because setOwner is public, enabling an attacker to become contract owner. A new owner can then invoke functions protected by onlyOwner, potentially altering important variab...
Useless Ethereum Token Information Disclosure Vulnerability
Useless Ethereum Token UET is a virtual currency. A security vulnerability exists in the 'transferFrom' function implemented by smart contract in UET, which stems from the program's failure to correctly compute calculations containing the 'value' parameter. The vulnerability can be exploited by a...
CVE-2018-10468
The transferFrom function of a smart contract implementation for Useless Ethereum Token UET, an Ethereum ERC20 token, allows attackers to steal assets e.g., transfer all victims' balances into their account because certain computations involving value are incorrect, as exploited in the wild...
Code injection
The transferFrom function of a smart contract implementation for Useless Ethereum Token UET, an Ethereum ERC20 token, allows attackers to steal assets e.g., transfer all victims' balances into their account because certain computations involving value are incorrect, as exploited in the wild...
CVE-2018-10468
CVE-2018-10468 affects the Useless Ethereum Token (UET) ERC20 contract. The transferFrom function mishandles calculations involving _value, enabling an attacker to steal funds (e.g., drain victims’ balances). Exploitation has been observed in the wild since 2017-12. Related tokens (e.g., DimonCoi...
CVE-2018-10468
The transferFrom function of a smart contract implementation for Useless Ethereum Token UET, an Ethereum ERC20 token, allows attackers to steal assets e.g., transfer all victims' balances into their account because certain computations involving value are incorrect, as exploited in the wild...
New batchOverflow Bug in Multiple ERC20 Smart Contracts (CVE-2018–10299)
Built on our earlier efforts in analyzing EOS tokens, we have developed an automated system to scan and analyze Ethereum-based ERC-20 token transfers. Specifically, our system will automatically send out alerts if any suspicious transactions e.g., involving unreasonably large tokens occur. In...
New proxyOverflow Bug in Multiple ERC20 Smart Contracts (CVE-2018-10376)
On 4/24/2018, 01:17:50 p.m. UTC, PeckShield again detected an unusual MESH token transaction shown in Figure 1. In this particular transaction, someone transferred a large amount of MESH token — 0x8fff,ffff,ffff,ffff,ffff,ffff,ffff,ffff,ffff,ffff,ffff,ffff,ffff,ffff,ffff,ffff 63 f’s to herself...
Beauty Ecosystem Coin smart contract integer overflow vulnerability
Beauty Ecosystem Coin BEC is a virtual currency system based on blockchain technology by the Beauty Chain Foundation. smart contract is one of the smart contracts. An integer overflow vulnerability exists in the 'batchTransfer' function of the smart contract implementation in BEC. An attacker cou...
CVE-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 Beauty Chain economic system, allows attackers to accomplish an unauthorized increase of digital assets by providing two receivers arguments in...
CVE-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 Beauty Chain economic system, allows attackers to accomplish an unauthorized increase of digital assets by providing two receivers arguments in...
CVE-2018-10299
Beauty Ecosystem Coin (BEC) smart-contract vulnerability: batchTransfer suffers an integer overflow when calculating the amount as the product of cnt and _value, enabling an attacker to inflate balances for two _receivers with a large _value. The issue is documented as batchOverflow and was obser...
VulnCheck KEV: CVE-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 Beauty Chain economic system, allows attackers to accomplish an unauthorized increase of digital assets by providing two receivers...
Coinbase: ETH contract handling errors
A business logic error in the ETH contract handling code allowed for a nested revert call in contract execution to improperly credit a user account though funds had not been transferred. In addition, the code did not appropriately handle delegatecall within a contract. Sample contract for the fir...