| CVE-2020-16034 |
Inappropriate implementation in WebRTC in Google Chrome prior to 87.0.4280.66 allowed a local attacker to bypass…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16033 |
Inappropriate implementation in WebUSB in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to spoof…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16031 |
Insufficient data validation in UI in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to spoof the…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16030 |
Insufficient data validation in Blink in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to inject…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16032 |
Insufficient data validation in sharing in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to spoof the…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16029 |
Inappropriate implementation in PDFium in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to bypass…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16028 |
Heap buffer overflow in WebRTC in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to potentially exploit…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16027 |
Insufficient policy enforcement in developer tools in Google Chrome prior to 87.0.4280.66 allowed an attacker who…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16026 |
Use after free in WebRTC in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to potentially exploit heap…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16025 |
Heap buffer overflow in clipboard in Google Chrome prior to 87.0.4280.66 allowed a remote attacker who had compromised…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16024 |
Heap buffer overflow in UI in Google Chrome prior to 87.0.4280.66 allowed a remote attacker who had compromised the…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16023 |
Use after free in WebCodecs in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to potentially exploit heap…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16022 |
Insufficient policy enforcement in networking in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16021 |
Race in image burner in Google Chrome on ChromeOS prior to 87.0.4280.66 allowed a remote attacker who had compromised…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16020 |
Inappropriate implementation in cryptohome in Google Chrome on ChromeOS prior to 87.0.4280.66 allowed a remote…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16019 |
Inappropriate implementation in filesystem in Google Chrome on ChromeOS prior to 87.0.4280.66 allowed a remote…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16018 |
Use after free in payments in Google Chrome prior to 87.0.4280.66 allowed a remote attacker who had compromised the…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16017 |
Exploitée
Google Chrome Use-After-Free Vulnerability
|
9.6
Critique
|
8 janv. 2021 |
| CVE-2020-16016 |
Inappropriate implementation in base in Google Chrome prior to 86.0.4240.193 allowed a remote attacker who had…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16015 |
Insufficient data validation in WASM in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to potentially…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16014 |
Use after free in PPAPI in Google Chrome prior to 87.0.4280.66 allowed a remote attacker who had compromised the…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16012 |
Side-channel information leakage in graphics in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to leak…
|
Non notée
|
8 janv. 2021 |
| CVE-2020-16013 |
Exploitée
Google Chromium V8 Incorrect Implementation Vulnerabililty
|
8.8
Élevée
|
8 janv. 2021 |
| CVE-2020-6557 |
Inappropriate implementation in networking in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to perform…
|
Non notée
|
3 nov. 2020 |
| CVE-2020-16011 |
Heap buffer overflow in UI in Google Chrome on Windows prior to 86.0.4240.183 allowed a remote attacker who had…
|
Non notée
|
3 nov. 2020 |