MOOS‑IvP versions up to 24.8.1 contain a denial‑of‑service flaw in the Demuxer::addMuxPacket() function. The code blindly trusts the packet count field in incoming MUX headers and uses it to size a dynamic memory allocation. An attacker able to inject a packet with a fabricated, excessively large packet count can cause the program to attempt to allocate a correspondingly large buffer, exhausting system memory and ultimately halting the service.

All releases of the MOOS‑IvP open‑source project through version 24.8.1, as identified by the vendor identifier moos-ivp:moos-ivp. The vulnerability resides in the core library used by any MOOS‑IvP based application, and no particular deployment pattern is excluded.

The CVSS score of 8.7 indicates a high‑severity vulnerability. EPSS data is unavailable, and the issue is not listed in the CISA KEV catalog. The flaw requires an attacker to deliver a crafted packet to the Demuxer component, most likely over the network. Because the weakness lies in input parsing, an attacker with network connectivity to the application can trigger the denial of service without needing local privileges or additional exploits. Once activated, the unbounded allocation will consume all available memory, causing the MOOS‑IvP service to crash or become unresponsive.