CyberRota Analysis
AI-GeneratedThe vulnerability in libsoup's HTTP/2 implementation allows a remote, unauthenticated attacker to exploit memory management issues during stream termination, leading to incremental heap allocation consumption. This can result in a denial of service (DoS) by causing the application to crash due to out-of-memory (OOM) conditions. Organizations utilizing libsoup in their applications should prioritize addressing this vulnerability to mitigate potential service disruptions.
Original NVD Description
A vulnerability was found in libsoup's HTTP/2 protocol implementation. The library fails to correctly release memory context blocks under specific stream termination conditions, such as when an HTTP/2 connection encounters window exhaustion or explicit stream resets. A remote, unauthenticated attacker acting as a malicious network peer can trick the connection engine into allocating stream states that are subsequently leaked during cleanup. Over a sustained period, this flaw allows the remote attacker to consume the system's heap allocations incrementally, triggering a denial of service (DoS) through an ultimate Out-of-Memory (OOM) application crash.