Netty: Memory Exhaustion in SctpMessageCompletionHandler
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.4%
exploitation probability
0.4%top 69% of all CVEs
observed exploitation
nono source reports it
Netty is an asynchronous, event-driven network application framework. Prior to 4.1.137.Final and 4.2.17.Final, io.netty.handler.codec.sctp.SctpMessageCompletionHandler limits incomplete messages and fragment counts but not maxBufferedBytes, allowing unauthenticated peers to exhaust memory with large SCTP fragments. This issue is fixed in versions 4.1.137.Final and 4.2.17.Final.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
netty · nettyReferences
https://github.com/netty/netty/commit/1b5abc6443b63726c72cdd285af2feb7ddbb8ff7https://github.com/netty/netty/pull/17213https://github.com/netty/netty/pull/17217https://github.com/netty/netty/releases/tag/netty-4.1.137.Finalhttps://github.com/netty/netty/releases/tag/netty-4.2.17.Finalhttps://github.com/netty/netty/security/advisories/GHSA-2qj4-mmr9-4v2f