Improper Certificate Validation in Pion DTLS
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.5, a DTLS Client could provide a Certificate that it doesn't posses the private key for and Pion DTLS wouldn't reject it. This issue affects users that are using Client certificates only. The connection itself is still secure. The Certificate provided by clients can't be trusted when using a Pion DTLS server prior to version 2.1.5. Users should upgrade to version 2.1.5 to receive a patch. There are currently no known workarounds.
From the CVE record · GitHub_M
Before version 2.1.5, Pion DTLS servers using client certificates may accept a certificate from a remote client that does not possess its private key. The client certificate therefore cannot be trusted, although the connection itself remains secure. This affects deployments using client certificates; no user interaction is described.
Check deployments using Go packages github.com/pion/dtls or github.com/pion/dtls/v2 before version 2.1.5, especially servers using client certificates.