CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-26240 – Erroneous Proof of Work calculation in geth
https://notcve.org/view.php?id=CVE-2020-26240
Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. An ethash mining DAG generation flaw in Geth before version 1.9.24 could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on 2020-11-06. This issue is relevant only for miners, non-mining nodes are unaffected. This issue is fixed as of 1.9.24 Go Ethereum, o "Geth", es la implementación oficial de Golang del protocolo Ethereum. • https://blog.ethereum.org/2020/11/12/geth_security_release https://github.com/ethereum/go-ethereum/commit/d990df909d7839640143344e79356754384dcdd0 https://github.com/ethereum/go-ethereum/pull/21793 https://github.com/ethereum/go-ethereum/security/advisories/GHSA-v592-xf75-856p • CWE-682: Incorrect Calculation •
CVSS: 7.1EPSS: 0%CPEs: 1EXPL: 0CVE-2020-26241 – Shallow copy bug in geth
https://notcve.org/view.php?id=CVE-2020-26241
Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. This is a Consensus vulnerability in Geth before version 1.9.17 which can be used to cause a chain-split where vulnerable nodes reject the canonical chain. Geth's pre-compiled dataCopy (at 0x00...04) contract did a shallow copy on invocation. An attacker could deploy a contract that writes X to an EVM memory region R, then calls 0x00..04 with R as an argument, then overwrites R to Y, and finally invokes the RETURNDATACOPY opcode. When this contract is invoked, a consensus-compliant node would push X on the EVM stack, whereas Geth would push Y. • https://blog.ethereum.org/2020/11/12/geth_security_release https://github.com/ethereum/go-ethereum/security/advisories/GHSA-69v6-xc2j-r2jf • CWE-682: Incorrect Calculation •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2020-26242 – Denial of service in geth
https://notcve.org/view.php?id=CVE-2020-26242
Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. In Geth before version 1.9.18, there is a Denial-of-service (crash) during block processing. This is fixed in 1.9.18. Go Ethereum, o "Geth", es la implementación oficial de Golang del protocolo Ethereum. En Geth versiones anteriores a 1.9.18, se presenta una Denegación de servicio (bloqueo) durante el procesamiento de bloques. • https://blog.ethereum.org/2020/11/12/geth_security_release https://github.com/ethereum/go-ethereum/security/advisories/GHSA-jm5c-rv3w-w83m •
CVSS: 10.0EPSS: 0%CPEs: 1EXPL: 2CVE-2018-15890
https://notcve.org/view.php?id=CVE-2018-15890
An issue was discovered in EthereumJ 1.8.2. There is Unsafe Deserialization in ois.readObject in mine/Ethash.java and decoder.readObject in crypto/ECKey.java. When a node syncs and mines a new block, arbitrary OS commands can be run on the server. Se detecto un problema en EthereumJ 1.8.2. Hay Deserialización insegura en ois.readObject en mine / Ethash.java y decoder.readObject en crypto / ECKey.java. • https://github.com/ethereum/ethereumj https://github.com/ethereum/ethereumj/issues/1161 https://github.com/frohoff/ysoserial • CWE-502: Deserialization of Untrusted Data •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1CVE-2018-20421
https://notcve.org/view.php?id=CVE-2018-20421
Go Ethereum (aka geth) 1.8.19 allows attackers to cause a denial of service (memory consumption) by rewriting the length of a dynamic array in memory, and then writing data to a single memory location with a large index number, as demonstrated by use of "assembly { mstore }" followed by a "c[0xC800000] = 0xFF" assignment. Go Ethereum (también conocido como geth) 1.8.19 permite que los atacantes provoquen una denegación de servicio (consumo de memoria) mediante la reescritura de la longitud de un array dinámico en la memoria y, a continuación, la escritura de datos a una única ubicación de memoria con un número de índice largo. Esto queda demostrado por el uso de "assembly { mstore }", seguido por una asignación "c[0xC800000] = 0xFF". • https://github.com/ethereum/go-ethereum/issues/18289 • CWE-770: Allocation of Resources Without Limits or Throttling •