Pion DTLS uses random nonce generation with AES GCM ciphers risks leaking the authentication key
pion dtls
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/pion/dtls/v3 Go |
|
|
| github.com/pion/dtls/v2 Go |
|
pion dtls
| Product | Affected | Fixed in |
|---|---|---|
| github.com/pion/dtls/v3 Go |
|
|
| github.com/pion/dtls/v2 Go |
|
all versions| No fix yet |
| github.com/pion/dtls Go |
| No fix yet |
Pion DTLS is a Go implementation of Datagram Transport Layer Security. Pion DTLS versions v1.0.0 through v3.0.10 and 3.1.0 use random nonce generation with AES GCM ciphers, which makes it easier for remote attackers to obtain the authentication key and spoof data by leveraging the reuse of a nonce in a session and a "forbidden attack". Upgrade to v3.0.11, v3.1.1, or later.
From the CVE record · GitHub_M
Affected Pion DTLS versions generate random nonces for AES-GCM ciphers. A remote attacker can exploit nonce reuse within a session to obtain the authentication key and spoof data. The input does not specify whether authentication or user interaction is required.
Engineers using Go packages github.com/pion/dtls/v3 (3.0.10 or 3.1.0), github.com/pion/dtls/v2 (all versions), or github.com/pion/dtls (all versions) should check their deployments.