libp2p nodes vulnerable to attack using large RSA keys
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.27.8, 0.28.2, 0.29.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- libp2p go-libp2p
fixed in 0.27.8; From 0.28.0 · fixed in 0.28.2
- github.com/libp2p/go-libp2pGo
fixed in 0.27.8; From 0.28.0 · fixed in 0.28.2; From 0.29.0 · fixed in 0.29.1
- github.com/libp2p/go-libp2pGo
fixed in 0.27.8
- github.com/libp2p/go-libp2pGo
From 0.28.0 · fixed in 0.28.2
- github.com/libp2p/go-libp2pGo
From 0.29.0 · fixed in 0.29.1