Bug 2242124 (CVE-2023-39533) - CVE-2023-39533 go-libp2p: libp2p nodes vulnerable to attack using large RSA keys
Summary: CVE-2023-39533 go-libp2p: libp2p nodes vulnerable to attack using large RSA keys
Keywords:
Status: NEW
Alias: CVE-2023-39533
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2228694
TreeView+ depends on / blocked
 
Reported: 2023-10-04 13:57 UTC by Avinash Hanwate
Modified: 2023-10-04 18:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Avinash Hanwate 2023-10-04 13:57:40 UTC
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.

https://github.com/libp2p/go-libp2p/commit/e30fcf7dfd4715ed89a5e68d7a4f774d3b9aa92d
https://github.com/libp2p/go-libp2p/pull/2454
https://github.com/quic-go/quic-go/pull/4012
https://github.com/libp2p/go-libp2p/security/advisories/GHSA-876p-8259-xjgg
https://github.com/libp2p/go-libp2p/commit/0cce607219f3710addc7e18672cffd1f1d912fbb
https://github.com/golang/go/commit/2350afd2e8ab054390e284c95d5b089c142db017
https://github.com/golang/go/issues/61460
https://github.com/libp2p/go-libp2p/commit/445be526aea4ee0b1fa5388aa65d32b2816d3a00


Note You need to log in before you can comment on or make changes to this bug.