CVE-2022-29222: Improper validation of client certificates in github.com/pion/dtls/v2

github.com/pion/dtls/v2 Updated 02 Oct 2025

Summary

01/07/2022
Yes i
Unrated
Not published

CVE-2022-29222: Improper validation of client certificates in github.com/pion/dtls/v2. Affects github.com/pion/dtls/v2 versions < 2.1.5. Fixed in 2.1.5. How to fix ↓

Also tracked for

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.

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The github.com/pion/dtls/v2 package is a Go implementation of the Datagram Transport Layer Security (DTLS) protocol. It provides functionality for establishing secure communication channels over unreliable transport protocols, such as UDP. The package includes client and server implementations, as well as utilities for handling DTLS handshakes and data transmission. However, a vulnerability has been identified in the package's handling of client certificates, which could lead to the acceptance of invalid certificates.

Vulnerability Detail

The vulnerability in github.com/pion/dtls/v2 arises from improper validation of client certificates. DTLS client certificates are expected to be accompanied by proof that the client possesses the private key for the certificate. However, the Pion DTLS server does not correctly validate this proof, allowing an attacker to present any certificate and have it accepted as valid. This can lead to unauthorized access, man-in-the-middle attacks, and other security breaches.

How To Fix

Minimum fixed version

2.1.5

This is the first release that contains the fix.

go get github.com/pion/dtls/v2@v2.1.5

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to update to the latest version of github.com/pion/dtls/v2 as soon as possible.

Conclusion

The vulnerability in github.com/pion/dtls/v2's handling of client certificates can lead to unauthorized access and other security breaches. It is crucial for developers to update to the latest version of the package (2.1.5 or later) to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for github.com/pion/dtls/v2 →

Share this vulnerability

FAQ

github.com/pion/dtls/v2 is a Go package that implements the Datagram Transport Layer Security (DTLS) protocol. It allows for secure communication over unreliable transport protocols, such as UDP.

This vulnerability allows an attacker to present any client certificate as valid, potentially leading to unauthorized access, man-in-the-middle attacks, and other security breaches.

To fix this vulnerability, update your usage of github.com/pion/dtls/v2 to version 2.1.5 or later.

There are no known workarounds for this vulnerability. It is recommended to update to the latest version of github.com/pion/dtls/v2.

You can find more information about this vulnerability in the Open Source Vulnerability database at https://pkg.go.dev/vuln/GO-2022-0462.

References

Related vulnerabilities

Recent vulnerabilities recorded for github.com/pion/dtls/v2.

How To Fix

Minimum fixed version

2.1.5

This is the first release that contains the fix.

go get github.com/pion/dtls/v2@v2.1.5

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback