(Chromium security severity: Low) Published: Decem9:15:07 PM -0500 Inappropriate implementation in Web Browser UI in Google Chrome prior to 1.62 allowed a remote attacker to potentially spoof the contents of an iframe dialog context menu via a crafted HTML page. (Chromium security severity: High) Published: Decem5:15:44 PM -0500 Type confusion in V8 in Google Chrome prior to 1.109 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. Use after free in Blink in Google Chrome prior to 1.109 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. Use after free in libavif in Google Chrome prior to 1.109 allowed a remote attacker to potentially exploit heap corruption via a crafted image file. Use after free in WebRTC in Google Chrome prior to 1.109 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. Use after free in FedCM in Google Chrome prior to 1.109 allowed a remote attacker who convinced a user to engage in specific UI interaction to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium) Published: Decem5:15:44 PM -0500 Use after free in CSS in Google Chrome prior to 1.109 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High) Published: Decem11:15:09 AM -0500 Insufficient policy enforcement in ADB in Google Chrome on ChromeOS prior to 1.90 allowed a local attacker to bypass device policy restrictions via physical access to the device. (Chromium security severity: High) Published: Decem6:15:11 PM -0500 Heap buffer overflow in WebRTC in Google Chrome prior to 1.129 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |