Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2024-32984— Yamux Memory Exhaustion Vulnerability via Active::pending_frames property

Quick assessment

Affected
libp2p rust-yamux
Exploitation
Public or AI PoC available; prioritize validation
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

HashiCorp Yamux是美国HashiCorp公司的一个多路复用器。 Yamux 0.13.2之前版本存在安全漏洞，该漏洞源于Active pending_frames 属性可能造成的 Yamux 内存耗尽。

CVSS 7.5 · High EPSS 0.76% · P54
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-32984

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Yamux Memory Exhaustion Vulnerability via Active::pending_frames property
Source: CVE Program / CVE List V5
Vulnerability Description
Yamux is a stream multiplexer over reliable, ordered connections such as TCP/IP. The Rust implementation of the Yamux stream multiplexer uses a vector for pending frames. This vector is not bounded in length. Every time the Yamux protocol requires sending of a new frame, this frame gets appended to this vector. This can be remotely triggered in a number of ways, for example by: 1. Opening a new libp2p Identify stream. This causes the node to send its Identify message. Of course, every other protocol that causes the sending of data also works. The larger the response, the more data is enqueued. 2. Sending a Yamux Ping frame. This causes a Pong frame to be enqueued. Under normal circumstances, this queue of pending frames would be drained once they’re sent out over the network. However, the attacker can use TCP’s receive window mechanism to prevent the victim from sending out any data: By not reading from the TCP connection, the receive window will never be increased, and the victim won’t be able to send out any new data (this is how TCP implements backpressure). Once this happens, Yamux’s queue of pending frames will start growing indefinitely. The queue will only be drained once the underlying TCP connection is closed. An attacker can cause a remote node to run out of memory, which will result in the corresponding process getting terminated by the operating system.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
未加控制的资源消耗(资源穷尽)
Source: CVE Program / CVE List V5
Vulnerability Title
Yamux 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
HashiCorp Yamux是美国HashiCorp公司的一个多路复用器。 Yamux 0.13.2之前版本存在安全漏洞，该漏洞源于Active pending_frames 属性可能造成的 Yamux 内存耗尽。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
libp2p rust-yamux < 0.13.2 -

II. Public POCs for CVE-2024-32984

# POC Description Source Link Shenlong Link
AI-Generated POC Premium
Qwen3.6-35B-A3B · 10361 chars
Pro+ exclusive includes:
Vulnerability reproduction recording (real sandbox build + trigger, exclusive)
In-depth vulnerability mechanism
Trigger conditions & impact
Full executable POC code
Exploit chain & mitigation
POC zip download
100+ AI POC generations per month

III. Intelligence Information for CVE-2024-32984

请登录查看更多情报信息。

Patches & Fixes for CVE-2024-32984 (1)

Vendor Advisories for CVE-2024-32984 (1)

Other References for CVE-2024-32984 (1)

IV. Related Vulnerabilities

Same product: rust-yamux
Same vendor: libp2p
Same weakness: CWE-400

V. Comments for CVE-2024-32984

No comments yet

Leave a comment