4437 matches found
CVE-2018-16733
In Go Ethereum aka geth before 1.8.14, TraceChain in eth/apitracer.go does not verify that the end block is after the start block...
CVE-2018-16733
In Go Ethereum aka geth before 1.8.14, TraceChain in eth/apitracer.go does not verify that the end block is after the start block...
CVE-2018-16733
CVE-2018-16733 affects go-ethereum (geth) prior to 1.8.14, where TraceChain in eth/api_tracer.go does not verify that the end block is after the start block. The vulnerability’s root cause is improper validation in the tracing path, potentially enabling malformed block processing and, in some des...
PT-2018-13711 · Ethereum · Go-Ethereum
Name of the Vulnerable Software and Affected Versions: Go Ethereum versions prior to 1.8.14 Description: The issue arises from improper input validation in the TraceChain function within the eth/api tracer.go file. Specifically, it does not verify that the end block is after the start block. This...
CVE-2018-15552
The "PayWinner" function of a simplelottery smart contract implementation for The Ethereum Lottery, an Ethereum gambling game, generates a random value with publicly readable variable "maxTickets" which is private, yet predictable and readable by the eth.getStorageAt function. Therefore, it allow...
Code injection
The "PayWinner" function of a simplelottery smart contract implementation for The Ethereum Lottery, an Ethereum gambling game, generates a random value with publicly readable variable "maxTickets" which is private, yet predictable and readable by the eth.getStorageAt function. Therefore, it allow...
CVE-2018-15552
The CVE describes a vulnerability in the PayWinner function of a simplelottery smart contract used by The Ethereum Lottery. The root cause is that the function uses the publicly readable storage variable maxTickets (private in code) to generate a random value, which is readable via eth.getStorage...
CVE-2018-15552
The "PayWinner" function of a simplelottery smart contract implementation for The Ethereum Lottery, an Ethereum gambling game, generates a random value with publicly readable variable "maxTickets" which is private, yet predictable and readable by the eth.getStorageAt function. Therefore, it allow...
Wallarm joins AI Leaders @ AI Summit
Wallarm joins a select group of AI startups and prominent technologists from Nvidia, Netflix, Microsoft and Amazon to participate in AI Summit on September 19–20 at San Francisco’s Palace of Fine Arts. AI Summit puts AI to work by delivering real value in the business. In just 3 years this...
Dynamic Binary Analysis Tool: Manticore
Manticore is a prototyping tool for dynamic binary analysis, with support for symbolic execution, taint analysis, and binary instrumentation. Manticore comes with an easy-to-use command line tool that quickly generates new program “test cases” or sample inputs with symbolic execution. Each test...
Design/Logic Flaw
The maxRandom function of a smart contract implementation for All For One, an Ethereum gambling game, generates a random value with publicly readable variables because the seed value can be retrieved with a getStorageAt call. Therefore, it allows attackers to always win and get rewards...
CVE-2018-12056
The maxRandom function of a smart contract implementation for All For One, an Ethereum gambling game, generates a random value with publicly readable variables because the seed value can be retrieved with a getStorageAt call. Therefore, it allows attackers to always win and get rewards...
CVE-2018-11687
An integer overflow in the distributeBTR function of a smart contract implementation for Bitcoin Red BTCR, an Ethereum ERC20 token, allows the owner to accomplish an unauthorized increase of digital assets by providing a large address array, as exploited in the wild in May 2018, aka the...
CVE-2018-12056
Affected software: All For One’s Ethereum-based gambling contract. Vulnerability: The maxRandom function generates a random value using publicly readable variables because the _seed can be retrieved with getStorageAt, enabling attackers to predict the outcome. Impact: Attackers could always win a...
CVE-2018-12056
The maxRandom function of a smart contract implementation for All For One, an Ethereum gambling game, generates a random value with publicly readable variables because the seed value can be retrieved with a getStorageAt call. Therefore, it allows attackers to always win and get rewards...
CVE-2018-11687
An integer overflow in the distributeBTR function of a smart contract implementation for Bitcoin Red BTCR, an Ethereum ERC20 token, allows the owner to accomplish an unauthorized increase of digital assets by providing a large address array, as exploited in the wild in May 2018, aka the...
Code injection
The transferProxy and approveProxy functions of a smart contract implementation for SmartMesh SMT, an Ethereum ERC20 token, allow attackers to accomplish an unauthorized transfer of digital assets because replay attacks can occur with the same-named functions with the same signatures in other...
CVE-2018-10769
Summary (CVE-2018-10769): The SmartMesh (SMT) smart contract’s transferProxy and approveProxy functions are vulnerable to replay attacks, allowing unauthorized transfers of digital assets. The issue arises because the same-named functions (with identical signatures) exist in other tokens (First, ...
CVE-2018-10769
The transferProxy and approveProxy functions of a smart contract implementation for SmartMesh SMT, an Ethereum ERC20 token, allow attackers to accomplish an unauthorized transfer of digital assets because replay attacks can occur with the same-named functions with the same signatures in other...
Integer overflow
An integer overflow in the unprotected distributeToken function of a smart contract implementation for EETHER EETHER, an Ethereum ERC20 token, will lead to an unauthorized increase of an attacker's digital assets...