https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 03:16:36 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-338812 EUVD-2026-338812 https://cve.radiocsirt.org/vuln/euvd-2026-338812 https://cve.radiocsirt.org/vuln/fkie_cve-2026-57080 <p>Net::BitTorrent versions through 2.1.0 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix.</p> <p>The peer-wire framing in _process_messages trusts the 4-byte length prefix sent by a connected peer with no upper bound, while receive_data appends every inbound byte to the input buffer. A peer announces a length prefix of up to about 4 GiB and then streams bytes; the decoder waits until the buffer holds the full message before processing it, so the buffer grows without limit.</p> <p>Peer connections are unauthenticated, so any peer in the swarm exhausts the downloading process&#39;s memory. The largest legitimate message is a 16 KiB piece block, so any announced length far above that is anomalous.</p> <p>Net::BitTorrent versions through 2.1.0 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix.</p> <p>The peer-wire framing in _process_messages trusts the 4-byte length prefix sent by a connected peer with no upper bound, while receive_data appends every inbound byte to the input buffer. A peer announces a length prefix of up to about 4 GiB and then streams bytes; the decoder waits until the buffer holds the full message before processing it, so the buffer grows without limit.</p> <p>Peer connections are unauthenticated, so any peer in the swarm exhausts the downloading process&#39;s memory. The largest legitimate message is a 16 KiB piece block, so any announced length far above that is anomalous.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-57080 https://cve.radiocsirt.org/vuln/ghsa-h9mr-rh28-v9r2 <p>Net::BitTorrent versions through 2.0.1 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix.</p> <p>The peer-wire framing in _process_messages trusts the 4-byte length prefix sent by a connected peer with no upper bound, while receive_data appends every inbound byte to the input buffer. A peer announces a length prefix of up to about 4 GiB and then streams bytes; the decoder waits until the buffer holds the full message before processing it, so the buffer grows without limit.</p> <p>Peer connections are unauthenticated, so any peer in the swarm exhausts the downloading process&#39;s memory. The largest legitimate message is a 16 KiB piece block, so any announced length far above that is anomalous.</p> <p>Net::BitTorrent versions through 2.0.1 for Perl allow remote memory exhaustion via an uncapped peer-wire message-length prefix.</p> <p>The peer-wire framing in _process_messages trusts the 4-byte length prefix sent by a connected peer with no upper bound, while receive_data appends every inbound byte to the input buffer. A peer announces a length prefix of up to about 4 GiB and then streams bytes; the decoder waits until the buffer holds the full message before processing it, so the buffer grows without limit.</p> <p>Peer connections are unauthenticated, so any peer in the swarm exhausts the downloading process&#39;s memory. The largest legitimate message is a 16 KiB piece block, so any announced length far above that is anomalous.</p> https://cve.radiocsirt.org/vuln/ghsa-h9mr-rh28-v9r2