Vulnerabilities (CVE)

Filtered by vendor Protocol
Filtered by product Libp2p
Angry Yack Logo
Total 4 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2023-40583 1 Protocol 1 Libp2p 2024-11-21 N/A 7.5 HIGH
libp2p is a networking stack and library modularized out of The IPFS Project, and bundled separately for other tools to use. In go-libp2p, by using signed peer records a malicious actor can store an arbitrary amount of data in a remote node’s memory. This memory does not get garbage collected and so the victim can run out of memory and crash. If users of go-libp2p in production are not monitoring memory consumption over time, it could be a silent attack i.e. the attacker could bring down nodes o ...

Show More

CVE-2022-23492 1 Protocol 1 Libp2p 2024-11-21 N/A 7.5 HIGH
go-libp2p is the offical libp2p implementation in the Go programming language. Version `0.18.0` and older of go-libp2p are vulnerable to targeted resource exhaustion attacks. These attacks target libp2p’s connection, stream, peer, and memory management. An attacker can cause the allocation of large amounts of memory, ultimately leading to the process getting killed by the host’s operating system. While a connection manager tasked with keeping the number of connections within manageable limits ha ...

Show More

CVE-2022-23487 1 Protocol 1 Libp2p 2024-11-21 N/A 7.5 HIGH
js-libp2p is the official javascript Implementation of libp2p networking stack. Versions older than `v0.38.0` of js-libp2p are vulnerable to targeted resource exhaustion attacks. These attacks target libp2p’s connection, stream, peer, and memory management. An attacker can cause the allocation of large amounts of memory, ultimately leading to the process getting killed by the host’s operating system. While a connection manager tasked with keeping the number of connections within manageable limit ...

Show More

CVE-2022-23486 1 Protocol 1 Libp2p 2024-11-21 N/A 7.5 HIGH
libp2p-rust is the official rust language Implementation of the libp2p networking stack. In versions prior to 0.45.1 an attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based netwo ...

Show More