go-libp2p up to 0.27.3 Node resource consumption

Summaryinfo

A vulnerability described as problematic has been identified in go-libp2p up to 0.27.3. This impacts an unknown function of the component Node Handler. Such manipulation leads to resource consumption. This vulnerability is uniquely identified as CVE-2023-40583. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in go-libp2p up to 0.27.3 and classified as problematic. Affected by this issue is an unknown code block of the component Node Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. CVE summarizes:

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.

The weakness was disclosed 08/26/2023 as GHSA-gcq9-qqwx-rgj3. The advisory is available at github.com. This vulnerability is handled as CVE-2023-40583 since 08/16/2023. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.

Upgrading to version 0.27.4 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 45d3c6fff662ddd6938982e7e9309ad5fa2ad8dd is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• go-libp2p

Version

• 0.27.0
• 0.27.1
• 0.27.2
• 0.27.3

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion