CVE-2020-16034: Inappropriate implementation in WebRTC
Published Oct 12, 2020
·Updated
Inappropriate implementation in WebRTC in Google Chrome prior to 87.0.4280.66 allowed a local attacker to bypass policy restrictions via a crafted HTML page.
Credit
vvmute (Benjamin Petermaier)
Affected Software
3 affected componentsFixes available
debian/chromium
90.0.4430.212-1~deb10u1116.0.5845.180-1~deb11u1120.0.6099.129-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.129-1~deb12u1120.0.6099.129-1
Google Chrome<87.0.4280.66
87.0.4280.66
Google Chrome<87.0.4280.66
Event History
Oct 12, 2020
CVE Published
12:00 AM
Jan 8, 2021
CVE Published
via MITRE·05:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2020-16018
- CVE-2020-16019
- CVE-2020-16020
- CVE-2020-16021
- CVE-2020-16022
- CVE-2020-16015
- CVE-2020-16014
- CVE-2020-16023
- CVE-2020-16024
- CVE-2020-16025
- CVE-2020-16045
- CVE-2020-16026
- CVE-2020-16027
- CVE-2020-16028
- CVE-2020-16029
- CVE-2020-16030
- CVE-2019-8075
- CVE-2020-16031
- CVE-2020-16032
- CVE-2020-16033
- CVE-2020-16035
- CVE-2020-16012
- CVE-2020-16036
Frequently Asked Questions
1
What is the severity of CVE-2020-16034?
CVE-2020-16034 has a medium severity rating due to its ability to allow local attackers to bypass policy restrictions.
2
How do I fix CVE-2020-16034?
To fix CVE-2020-16034, upgrade to Google Chrome version 87.0.4280.66 or later.
3
What systems are affected by CVE-2020-16034?
CVE-2020-16034 affects Google Chrome versions prior to 87.0.4280.66.
4
Who is the vendor associated with CVE-2020-16034?
The vendor associated with CVE-2020-16034 is Google.
5
What type of attack does CVE-2020-16034 involve?
CVE-2020-16034 involves a local attack that can bypass policy restrictions through a crafted HTML page.