Vulnerabilities · 2023 · Protocol
CVE-2023-40583
Protocol Libp2p vulnerability
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 over a period of time (how long depends on the node resources i.e. a go-libp2p node on a virtual server with 4 gb of memory takes about 90 sec to bring down; on a larger server, it might take a bit longer.) This issue was patched in version 0.27.4.
Affected products
Libp2p. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Protocol Libp2p runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/libp2p/go-libp2p/security/advisories/GHSA-gcq9-qqwx-rgj3 · Vendor Advisory
- github.com/libp2p/go-libp2p/commit/45d3c6fff662ddd6938982e7e9309ad5fa2ad8dd · Patch
- github.com/libp2p/go-libp2p/releases/tag/v0.27.4
- github.com/libp2p/go-libp2p/releases/tag/v0.27.7
- nvd.nist.gov/vuln/detail/CVE-2023-40583
- cve.org/CVERecord?id=CVE-2023-40583
More vulnerabilities in Protocol products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.