CyberRota Analysis
AI-GeneratedThe libp2p-quic component of the libp2p networking stack is vulnerable to a panic during the QUIC handshake process when a remote peer presents a valid but short-lived TLS certificate that has expired by the time the handshake completes. This can lead to application crashes for any service utilizing an affected libp2p-quic listener, significantly impacting availability. Organizations using libp2p-quic should prioritize upgrading to version 0.13.1 to mitigate this high-severity vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
libp2p-rust is the official Rust language implementation of the libp2p networking stack. Prior to 0.13.1, libp2p-quic could panic during an inbound QUIC handshake when a remote peer presented a valid short-lived libp2p TLS certificate and delayed the final TLS 1.3 handshake fragment until after the certificate expired. In the Quinn post-handshake upgrade path, transports/quic/src/connection/connecting.rs called libp2p_tls::certificate::parse a second time in remote_peer_id and used expect on the result. The repeated wall-clock validity check could reject the now-expired certificate, causing the expect call to terminate any application exposing an affected libp2p-quic listener. This vulnerability is fixed in 0.13.1.