Netty ByteBuf Leak in StompSubframeDecoder (CVE) - High Severity Memory Exhaustion

Vulnerability Summary: ByteBuf Leak Vulnerability Overview Vulnerability Name: ByteBuf Leak in StompSubframeDecoder When a Frame Body Is Never Terminated Vulnerability Type: Resource Leak (Memory Leak) Severity: High (CVSS 7.5) Description: The leaks allocators when the frame body is not properly terminated (i.e., the terminating NUL character is not received). When the frame content length ( ) is satisfied but the terminating character has not yet arrived, the decoder allocates a and stores it in the field while waiting for subsequent data. If the connection is disconnected or an error occurs, this buffer is not released, leading to a memory leak. An attacker can trigger this vulnerability by sending specifically crafted STOMP frames (with a length declaration but no terminating character), causing the server to run out of memory. Impact Scope Affected Component: Affected Versions: Fixed Versions: Remediation Recommended Fix: Release unused buffers in the method. Fix Code: Principle: calls when releasing its cumulation. This is the natural opportunity for the decoder to release internally parked buffers. only releases on the success path, whereas ensures that resources are properly released in cases of connection closure or exceptions. POC Code A complete POC code was not provided in the source; however, a test script named is mentioned for verifying the vulnerability. This script drives the released version using an and a counting allocator to track buffer allocations. POC Execution Command: Example Observed Output**:

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

Netty ByteBuf Leak in StompSubframeDecoder (CVE) - High Severity Memory Exhaustion

More from this source