Pion WebRTC before 3.0.15 didn't properly tear down the DTLS Connection when certificate verification failed. The PeerConnectionState was set to failed, but a user could ignore that and continue to use the PeerConnection. )A WebRTC implementation shouldn't allow the user to continue if verification has failed.)
References
Link | Resource |
---|---|
https://github.com/pion/webrtc/issues/1708 | Exploit Patch Third Party Advisory |
https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p | Third Party Advisory |
https://github.com/pion/webrtc/issues/1708 | Exploit Patch Third Party Advisory |
https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p | Third Party Advisory |
Configurations
History
21 Nov 2024, 06:00
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/pion/webrtc/issues/1708 - Exploit, Patch, Third Party Advisory | |
References | () https://github.com/pion/webrtc/security/advisories/GHSA-74xm-qj29-cq8p - Third Party Advisory |
Information
Published : 2021-03-18 04:15
Updated : 2024-11-21 06:00
NVD link : CVE-2021-28681
Mitre link : CVE-2021-28681
CVE.ORG link : CVE-2021-28681
JSON object : View
Products Affected
webrtc_project
- webrtc
CWE
CWE-863
Incorrect Authorization