Skip to content

Pion/DLTS Accepts Client Certificates Without CertificateVerify

Moderate severity GitHub Reviewed Published May 16, 2022 in pion/dtls • Updated Aug 29, 2023

Package

gomod github.com/pion/dtls (Go)

Affected versions

< 2.1.5

Patched versions

2.1.5
gomod github.com/pion/dtls/v2 (Go)
< 2.1.5
2.1.5

Description

Impact

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

Patches

Upgrade to Pion DTLS v2.1.5

Workarounds

No workarounds available, upgrade to Pion DTLS v2.1.5

References

Thank you to Juho Nurminen and the Mattermost team for discovering and reporting this.

For more information

If you have any questions or comments about this advisory:

References

@Sean-Der Sean-Der published to pion/dtls May 16, 2022
Published by the National Vulnerability Database May 21, 2022
Published to the GitHub Advisory Database May 25, 2022
Reviewed May 25, 2022
Last updated Aug 29, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.072%
(32nd percentile)

Weaknesses

CVE ID

CVE-2022-29222

GHSA ID

GHSA-w45j-f832-hxvh

Source code

github.com/pion/dtls
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.