8 matches found
DEBIAN-CVE-2022-0289
Use after free in Safe browsing in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page...
CVE-2022-0289
Use after free in Safe browsing in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page...
CVE-2022-0289
Use after free in Safe browsing in Google Chrome prior to 97.0.4692.99 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page...
CVE-2022-0289
The CVE-2022-0289 entry affects Google Chrome’s Safe Browsing component, with a Use-After-Free vulnerability that could lead to heap corruption via a crafted HTML page. Affected version prior to 97.0.4692.99 is fixed in Chrome’s January 2022 update; the Chrome release notes list this as a critica...
MGASA-2022-0043 Updated chromium-browser-stable packages fix security vulnerability
CVE-2022-0096: Use after free in Storage. CVE-2022-0097: Inappropriate implementation in DevTools. CVE-2022-0098: Use after free in Screen Capture. CVE-2022-0099: Use after free in Sign-in. CVE-2022-0100: Heap buffer overflow in Media streams API. CVE-2022-0101: Heap buffer overflow in Bookmarks...
[SECURITY] [DSA 5054-1] chromium security update
------------------------------------------------------------------------- Debian Security Advisory DSA-5054-1 [email protected] https://www.debian.org/security/ Moritz Muehlenhoff January 23, 2022 https://www.debian.org/security/faq -...
Update now! Chrome patches critical RCE vulnerability in Safe Browsing
Google has issued an update for the Chrome browser which includes 26 security fixes. What stands out is that one of these fixes is rated as "critical". The critical vulnerability is a use after free bug in the Safe Browsing feature. The Stable channel has been updated to 97.0.4692.99 for Windows,...
Chromium: CVE-2022-0289 Use after free in Safe browsing
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...