First published: Tue Dec 03 2019(Updated: )
When setting a thread name on Windows in WebRTC, an incorrect number of arguments could have been supplied, leading to stack corruption and a potentially exploitable crash. Note: this issue only occurs on Windows. Other operating systems are unaffected.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Mozilla Thunderbird | <68.3 | 68.3 |
<71 | 71 | |
<68.3 | 68.3 | |
<68.3 | 68.3 | |
Google Chrome | <79.0.3945.79 | 79.0.3945.79 |
Google Chrome | <79.0.3945.79 | |
Microsoft Windows |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
(Found alongside the following vulnerabilities)
The vulnerability ID is CVE-2019-13722.
The title of the vulnerability is 'Inappropriate implementation in WebRTC in Google Chrome prior to 79.0.3945.79 allowed a remote attac…'
The vulnerability occurs when setting a thread name on Windows in WebRTC, an incorrect number of arguments could have been supplied, leading to stack corruption and a potentially exploitable crash. It only affects Windows operating system.
Mozilla Thunderbird 68.3, Mozilla Firefox ESR 68.3, and Google Chrome up to version 79.0.3945.79 are affected by this vulnerability.
The severity of this vulnerability is high with a CVSS score of 6.5.