{"answers":{"affected":"2 open source packages ship an affected version, including yamux.","exploited":"There is no known exploitation of CVE-2024-32984 in the wild and no public exploit code.","fix":"Upgrade yamux to 0.13.2 or later.","what":"CVE-2024-32984 is a high-severity denial of service vulnerability in libp2p rust-yamux, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-32984 and fix it if it is affected.\n\nWhat it is: CVE-2024-32984 is a high-severity denial of service vulnerability in libp2p rust-yamux, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-32984 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- yamux (crates.io): affected from 0.13.0; fixed in 0.13.2\n- yamux (crates.io): affected from 0.13.0; fixed in 0.13.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-32984/ (Markdown: https://insights.sbomify.com/CVE-2024-32984/index.md)","id":"CVE-2024-32984","markdown":"https://insights.sbomify.com/CVE-2024-32984/index.md","name":"CVE-2024-32984","record":{"aliases":["GHSA-3999-5ffv-wp2r"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust Yamux library","requires_auth":"none","summary":"Remote attackers can exhaust memory in applications using the Rust Yamux library by blocking TCP transmission, causing process termination.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Yamux Memory Exhaustion Vulnerability via Active::pending_frames property","id":"CVE-2024-32984","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Stellar-core's Overlay - security fix for DDoS mitigation","id":"CVE-2024-32985"},"packages":[{"ecosystem":"crates.io","fixed":["0.13.2"],"introduced":["0.13.0"],"last_affected":[],"package":"yamux","purl":null,"source":"GHSA-3999-5ffv-wp2r"},{"ecosystem":"crates.io","fixed":["0.13.2"],"introduced":["0.13.0"],"last_affected":[],"package":"yamux","purl":"pkg:cargo/yamux","source":"GHSA-3999-5ffv-wp2r"}],"prev":{"headline":"Misskey allows the impersonation and takeover of remote accounts with unnormalized signed activities","id":"CVE-2024-32983"},"products":["rust-yamux"],"published":"2024-05-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["libp2p"]},"summary":"Remote attackers can exhaust memory in applications using the Rust Yamux library by blocking TCP transmission, causing process termination.","url":"https://insights.sbomify.com/CVE-2024-32984/"}