netty-codec-stomp is vulnerable to Memory Leak
75
High Risk
StompSubframeDecoder allocates a buffer once the content-length is satisfied but parks it while awaiting the terminating NUL byte, and overrides neither handlerRemoved0 nor channelInactive. A remote peer that sends a well-formed frame body without its trailing NUL leaks one buffer per connection, and with pooled allocators that memory never returns to the pool. Sustained connections accumulate leaked buffers for the process lifetime, exhausting memory. The fix releases the parked buffer on handler removal.
You are affected if you are using a version that falls within the vulnerable range and your application decodes STOMP frames from untrusted peers.
netty-codec-stomp is vulnerable to Memory Leak in versions 4.1.0.Final - 4.1.137.Final and 4.2.0.Final - 4.2.17.Final.
Upgrade the io.netty:netty-codec-stomp library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.