CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2019-25072 – Uncontrolled resource consumption in github.com/tendermint/tendermint
https://notcve.org/view.php?id=CVE-2019-25072
Due to support of Gzip compression in request bodies, as well as a lack of limiting response body sizes, a malicious server can cause a client to consume a significant amount of system resources, which may be used as a denial of service vector. Debido a la compatibilidad con la compresión Gzip en los cuerpos de las solicitudes, así como a la falta de limitación del tamaño de los cuerpos de las respuestas, un servidor malicioso puede hacer que un cliente consuma una cantidad significativa de recursos del sistema, lo que puede usarse como un vector de denegación de servicio. • https://github.com/tendermint/tendermint/commit/03085c2da23b179c4a51f59a03cb40aa4e85a613 https://github.com/tendermint/tendermint/pull/3430 https://pkg.go.dev/vuln/GO-2020-0037 • CWE-400: Uncontrolled Resource Consumption •
CVSS: 4.3EPSS: 0%CPEs: 3EXPL: 0CVE-2020-5303 – Denial of service in Tendermint
https://notcve.org/view.php?id=CVE-2020-5303
Tendermint before versions 0.33.3, 0.32.10, and 0.31.12 has a denial-of-service vulnerability. Tendermint does not limit the number of P2P connection requests. For each p2p connection, it allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions. Additionally, Tendermint does not reclaim activeID of a peer after it's removed in Mempool reactor. • https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6 https://hackerone.com/reports/820317 • CWE-787: Out-of-bounds Write CWE-789: Memory Allocation with Excessive Size Value •