| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/pion/dtls | < 2.1.5 | 2.1.5 |
| github.com/pion/dtls/v2 | < 2.1.5 | 2.1.5 |
| dtls | < 2.1.5 | 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 v2.1.5
Upgrade to Pion DTLS v2.1.5
No workarounds available, upgrade to Pion DTLS v2.1.5
Thank you to Juho Nurminen and the Mattermost team for discovering and reporting this.
If you have any questions or comments about this advisory:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free