Bugs fixes in "chromium-browser"
| Origin | Bug number | Title | Date fixed |
|---|---|---|---|
| CVE | CVE-2020-6473 | Insufficient policy enforcement in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to obtain potentially sensitive information | 2020-06-03 |
| CVE | CVE-2020-6472 | Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malic | 2020-06-03 |
| CVE | CVE-2020-6471 | Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malic | 2020-06-03 |
| CVE | CVE-2020-6470 | Insufficient validation of untrusted input in clipboard in Google Chrome prior to 83.0.4103.61 allowed a local attacker to inject arbitrary scripts o | 2020-06-03 |
| CVE | CVE-2020-6469 | Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malic | 2020-06-03 |
| CVE | CVE-2020-6468 | Type confusion in V8 in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | 2020-06-03 |
| CVE | CVE-2020-6467 | Use after free in WebRTC in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML p | 2020-06-03 |
| CVE | CVE-2020-6466 | Use after free in media in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had compromised the renderer process to potentially perf | 2020-06-03 |
| CVE | CVE-2020-6465 | Use after free in reader mode in Google Chrome on Android prior to 83.0.4103.61 allowed a remote attacker who had compromised the renderer process to | 2020-06-03 |
| CVE | CVE-2020-6491 | Insufficient data validation in site information in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof security UI via a crafted | 2020-06-03 |
| CVE | CVE-2020-6490 | Insufficient data validation in loader in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had been able to write to disk to leak cr | 2020-06-03 |
| CVE | CVE-2020-6489 | Inappropriate implementation in developer tools in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had convinced the user to take c | 2020-06-03 |
| CVE | CVE-2020-6488 | Insufficient policy enforcement in downloads in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a | 2020-06-03 |
| CVE | CVE-2020-6487 | Insufficient policy enforcement in downloads in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a | 2020-06-03 |
| CVE | CVE-2020-6486 | Insufficient policy enforcement in navigations in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via | 2020-06-03 |
| CVE | CVE-2020-6485 | Insufficient data validation in media router in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had compromised the renderer proces | 2020-06-03 |
| CVE | CVE-2020-6484 | Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a | 2020-06-03 |
| CVE | CVE-2020-6483 | Insufficient policy enforcement in payments in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypass navigation restrictions via a | 2020-06-03 |
| CVE | CVE-2020-6482 | Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malic | 2020-06-03 |
| CVE | CVE-2020-6481 | Insufficient policy enforcement in URL formatting in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to perform domain spoofing via a c | 2020-06-03 |
About
-
Send Feedback to @ubuntu_updates
