CVE-2023-39533

HighCVSS 7.5

Published: 08/08/2023(UTC)Updated: 01/09/2026(UTC)Translated: 18/06/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Elevated risk

1.50%

73th percentile - higher than 73% of all known CVEs

Summary

In go-libp2p, prior to versions 0.27.8, 0.28.2, and 0.29.1, a malicious peer can use large RSA keys to perform a resource exhaustion attack, forcing a node to spend time verifying signatures of the large key.

Risk Assessment

An attacker can cause significant resource strain, potentially leading to slowdowns or crashes of applications using go-libp2p.

Recommendation

It is recommended to update to versions 0.27.8, 0.28.2, or 0.29.1 and to use the updated Go compiler in versions 1.20.7 or 1.19.12.

Other vulnerabilities in go-libp2p

CVE-2023-40583High
In the go-libp2p library, using signed peer records, a malicious actor can store an arbitrary amount of data in a remote node's memory. This memory is not garbage collected, which can lead to memory exhaustion and node crashes.

Original NVD description (English source)

go-libp2p is the Go implementation of the libp2p Networking Stack. Prior to versions 0.27.8, 0.28.2, and 0.29.1 malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key. This vulnerability is present in the core/crypto module of go-libp2p and can occur during the Noise handshake and the libp2p x509 extension verification step. To prevent this attack, go-libp2p versions 0.27.8, 0.28.2, and 0.29.1 restrict RSA keys to <= 8192 bits. To protect one's application, it is necessary to update to these patch releases and to use the updated Go compiler in 1.20.7 or 1.19.12. There are no known workarounds for this issue.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS