Total
3085 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2017-5032 | 2 Google, Microsoft | 2 Chrome, Windows | 2018-01-04 | 6.8 MEDIUM | 8.8 HIGH |
PDFium in Google Chrome prior to 57.0.2987.98 for Windows could be made to increment off the end of a buffer, which allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. | |||||
CVE-2017-5018 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 6.1 MEDIUM |
Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, had an insufficiently strict content security policy on the Chrome app launcher page, which allowed a remote attacker to inject scripts or HTML into a privileged page via a crafted HTML page. | |||||
CVE-2017-5017 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 4.3 MEDIUM |
Interactions with the OS in Google Chrome prior to 56.0.2924.76 for Mac insufficiently cleared video memory, which allowed a remote attacker to possibly extract image fragments on systems with GeForce 8600M graphics chips via a crafted HTML page. | |||||
CVE-2017-5014 | 1 Google | 1 Chrome | 2018-01-04 | 6.8 MEDIUM | 6.3 MEDIUM |
Heap buffer overflow during image processing in Skia in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. | |||||
CVE-2017-5012 | 1 Google | 1 Chrome | 2018-01-04 | 6.8 MEDIUM | 8.8 HIGH |
A heap buffer overflow in V8 in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | |||||
CVE-2017-5011 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 6.5 MEDIUM |
Google Chrome prior to 56.0.2924.76 for Windows insufficiently sanitized DevTools URLs, which allowed a remote attacker who convinced a user to install a malicious extension to read filesystem contents via a crafted HTML page. | |||||
CVE-2017-5010 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 6.1 MEDIUM |
Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, resolved promises in an inappropriate context, which allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page. | |||||
CVE-2017-5009 | 1 Google | 1 Chrome | 2018-01-04 | 6.8 MEDIUM | 8.8 HIGH |
WebRTC in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | |||||
CVE-2017-5008 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 6.1 MEDIUM |
Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed attacker controlled JavaScript to be run during the invocation of a private script method, which allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page. | |||||
CVE-2017-5007 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 6.1 MEDIUM |
Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, incorrectly handled the sequence of events when closing a page, which allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page. | |||||
CVE-2017-5006 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 6.1 MEDIUM |
Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, incorrectly handled object owner relationships, which allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page. | |||||
CVE-2017-5020 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 6.1 MEDIUM |
Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to require a user gesture for powerful download operations, which allowed a remote attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted HTML page. | |||||
CVE-2017-5019 | 1 Google | 1 Chrome | 2018-01-04 | 6.8 MEDIUM | 6.3 MEDIUM |
A use after free in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. | |||||
CVE-2017-5041 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 4.3 MEDIUM |
Google Chrome prior to 57.0.2987.100 incorrectly handled back-forward navigation, which allowed a remote attacker to display incorrect information for a site via a crafted HTML page. | |||||
CVE-2017-5025 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 5.5 MEDIUM |
FFmpeg in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted video file. | |||||
CVE-2017-5024 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 5.5 MEDIUM |
FFmpeg in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted video file. | |||||
CVE-2017-5023 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 4.3 MEDIUM |
Type confusion in Histogram in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed a remote attacker to potentially exploit a near null dereference via a crafted HTML page. | |||||
CVE-2017-5021 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 4.3 MEDIUM |
A use after free in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. | |||||
CVE-2016-9650 | 1 Google | 1 Chrome | 2018-01-04 | 4.3 MEDIUM | 4.3 MEDIUM |
Blink in Google Chrome prior to 55.0.2883.75 for Mac, Windows and Linux, and 55.0.2883.84 for Android incorrectly handled iframes, which allowed a remote attacker to bypass a no-referrer policy via a crafted HTML page. | |||||
CVE-2016-7549 | 1 Google | 1 Chrome | 2018-01-04 | 6.8 MEDIUM | 8.8 HIGH |
Google Chrome before 53.0.2785.113 does not ensure that the recipient of a certain IPC message is a valid RenderFrame or RenderWidget, which allows remote attackers to cause a denial of service (invalid pointer dereference and application crash) or possibly have unspecified other impact by leveraging access to a renderer process, related to render_frame_host_impl.cc and render_widget_host_impl.cc, as demonstrated by a Password Manager message. |