NRDAX
CLI Submit

← registry

NRDAX-T0203 - Ping Flood Pending Frame OOM

Memory amplification · P2P and gossip · no bound · active · first seen 2026-07-11

provenance: Reproduced in NullRabbit's attack-reproduction pipeline

mechanism

CVE-2024-32984 (GHSA-3999-5ffv-wp2r): rust-yamux (0.13.0 .. <0.13.2) buffers frames-to-send in an unbounded `pending_frames` VecDeque. A remote peer floods Ping frames (each enqueues a Pong reply) and/or opens streams while stalling its own TCP receive window (never sending WindowUpdate), so the victim's outbound frame queue cannot drain and grows without bound → remote memory exhaustion (fixed in 0.13.2, which bounds the queue).

live exposure

No exposure data. Slashr ↗ has no risk signal mapped to this technique yet — absence of data is not absence of exposure.

instances (1)

chainprimitivefidelityoriginreproducer (bundle)source
libp2p yamux_ping_flood_pending_frames_oom lab reverse-engineered-cve yamux_ping_flood_pending_frames_oom GHSA-3999-5ffv-wp2r ↗

references

vendor-advisory: GHPR-MystenLabs-sui-27811

related (Memory amplification)

cite

https://nrdax.com/techniques/NRDAX-T0203

plain

NRDAX Registry. Technique NRDAX-T0203.

bibtex
@misc{nrdax_NRDAX_T0203,
  title = {Ping Flood Pending Frame OOM (NRDAX-T0203)},
  howpublished = {NRDAX Registry},
  url = {https://nrdax.com/techniques/NRDAX-T0203},
}
json (csl)
{
  "id": "nrdax-NRDAX-T0203",
  "type": "dataset",
  "title": "Ping Flood Pending Frame OOM (NRDAX-T0203)",
  "URL": "https://nrdax.com/techniques/NRDAX-T0203",
  "publisher": "NRDAX Registry"
}
badge

NRDAX-T0203 in the NRDAX registry

[![NRDAX-T0203 in the NRDAX registry](https://nrdax.com/badge/NRDAX-T0203.svg)](https://nrdax.com/techniques/NRDAX-T0203-ping-flood-pending-frame-oom)

use from the CLI

Retrieve or cite this technique from a script or the terminal with the NRDAX Python library & CLI.

Retrieve this technique
nrdax get NRDAX-T0203
Cite it (BibTeX)
nrdax cite NRDAX-T0203 --format bibtex

CLI guide → GitHub ↗