CyberRota Analysis
AI-GeneratedThe vulnerability arises from improper memory allocation during the DTLS handshake process in versions of bc-csharp prior to 2.7.0, allowing a remote unauthenticated DTLS peer to exploit this flaw by sending specially crafted handshake message fragments. This can lead to a denial of service through memory exhaustion, as the system may allocate excessive memory for each fragment without proper validation against the maximum handshake message size. Organizations using DTLS servers or clients should prioritize patching to mitigate the risk of service disruption.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Memory allocation with excessive size value in the DTLS handshake reassembly (DtlsReliableHandshake, DtlsReassembler) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote unauthenticated DTLS peer to cause a denial of service through memory exhaustion via crafted handshake message fragments, because the reassembly buffer for each incoming handshake message was allocated at the 24-bit length declared in the fragment header, without the check against the peer's maximum handshake message size that TLS already applied. A fragment carrying no payload can force an allocation of almost 16 MB, for each of up to 16 pending messages per handshake, before the handshake is authenticated. DTLS servers and DTLS clients are both affected; TLS is not.