CVE-2022-29222: Client Certificates Accepted Without CertificateVerify in Pion DTLS
Summary
CVE-2022-29222: Pion/DLTS Accepts Client Certificates Without CertificateVerify. Affects github.com/pion/dtls versions < 2.1.5. Fixed in 2.1.5. How to fix ↓
Also tracked for
- github.com/pion/dtls/v2 · Go
- snowflake · Debian:12
The same CVE-2022-29222 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Pion DTLS is a Go library that provides Datagram Transport Layer Security (DTLS) functionality. It allows secure communication over unreliable transport protocols such as UDP. DTLS is commonly used in applications that require low-latency and real-time communication, such as VoIP and video streaming. Pion DTLS supports client certificates for authentication purposes.
Vulnerability Detail
The vulnerability (CVE-2022-29222) in Pion DTLS allows a DTLS client to provide a certificate that it does not possess the private key for, and Pion DTLS does not reject it. This issue affects users who are using client certificates only. While the connection itself is still secure, the certificate provided by clients cannot be trusted when using a Pion DTLS server prior to version 2.1.5. This vulnerability has a CVSS score of 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).
How To Fix
Latest published version: v1.5.4 as of 23 Oct 2026
go get github.com/pion/dtls@v1.5.4Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2.1.5
This is the first release that contains the fix.
go get github.com/pion/dtls@v2.1.5Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There are no known workarounds for this vulnerability. Upgrading to Pion DTLS version 2.1.5 is the recommended solution.
Conclusion
The vulnerability (CVE-2022-29222) in Pion DTLS allows a DTLS client to provide a certificate without the corresponding private key, and Pion DTLS does not reject it. This can lead to untrusted client certificates. To fix this vulnerability, it is recommended to upgrade to Pion DTLS version 2.1.5 or later. There are no known workarounds for this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/pion/dtls →
FAQ
Pion DTLS is a Go library that provides Datagram Transport Layer Security (DTLS) functionality for secure communication over unreliable transport protocols.
The impact of this vulnerability is that a DTLS client can provide a certificate without the corresponding private key, and Pion DTLS will accept it. This means that the certificate provided by clients cannot be trusted.
This vulnerability was discovered and reported by Juho Nurminen and the Mattermost team.
This vulnerability has a severity rating of MODERATE.
No, there are no known workarounds for this vulnerability. Upgrading to Pion DTLS version 2.1.5 is the recommended solution.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/pion/dtls.
