Buffer for inbound DTLS fragments has no limit
pion dtls
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/pion/dtls Go |
|
|
| github.com/pion/dtls/v2 Go |
|
|
pion dtls
| Product | Affected | Fixed in |
|---|---|---|
| github.com/pion/dtls Go |
|
|
| github.com/pion/dtls/v2 Go |
|
|
Pion DTLS is a Go implementation of Datagram Transport Layer Security. Prior to version 2.1.4, a buffer that was used for inbound network traffic had no upper limit. Pion DTLS would buffer all network traffic from the remote user until the handshake completes or timed out. An attacker could exploit this to cause excessive memory usage. Version 2.1.4 contains a patch for this issue. There are currently no known workarounds available.
From the CVE record · GitHub_M
Before version 2.1.4, Pion DTLS places no upper limit on the buffer used for inbound network traffic during a handshake. A remote attacker can send traffic that remains buffered until the handshake completes or times out, causing excessive memory usage.
Engineers using Go packages github.com/pion/dtls or github.com/pion/dtls/v2 at versions earlier than 2.1.4 should check their deployments.