Webrtcproject Webrtc
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Webrtcproject Webrtc.
By the Year
In 2025 there have been 0 vulnerabilities in Webrtcproject Webrtc. Webrtc did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 1 | 8.80 |
| 2021 | 1 | 5.30 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Webrtc vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Webrtcproject Webrtc Security Vulnerabilities
Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.114
CVE-2022-2294
8.8 - High
- July 28, 2022
Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Memory Corruption
Pion WebRTC before 3.0.15 didn't properly tear down the DTLS Connection when certificate verification failed
CVE-2021-28681
5.3 - Medium
- March 18, 2021
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.)
AuthZ
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Webrtcproject Webrtc or by Webrtcproject? Click the Watch button to subscribe.
