![]() ![]() ![]() High CVE-2023-6351: Use after free in libavif. High CVE-2023-6350: Out of bounds memory access in libavif. Reported by Huang Xilin of Ant Group Light-Year Security Lab on High CVE-2023-6346: Use after free in WebAudio. Reported by Leecraso and Guang Gong of 360 Vulnerability Research Institute on High CVE-2023-6347: Use after free in Mojo. Reported by Mark Brand of Google Project Zero on High CVE-2023-6348: Type Confusion in Spellcheck. Please see the Chrome Security Page for more information. Below, we highlight fixes that were contributed by external researchers. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. ![]() Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. A full list of changes in this build is available in the log. To update Chrome, head over to Settings in the Chrome menu, then About Chrome and check for a new update.The Stable channel has been updated to 1.199 for Mac and Linux and 1.199/.200 for Windows, which will roll out over the coming days/weeks. As Google explains, Chrome uses Skia for nearly all graphics operations, including text rendering, so it’s not so easy to avoid. Google says it is aware that an exploit for CVE-2023-6345 exists in the wild, meaning that an attacker has used the vulnerability to attack a computer. CVE-2023-6345: Reported by Benoît Sevens and Clément Lecigne of Google’s Threat Analysis Group.CVE-2023-6350: Reported by Fudan University.Description: Out of bounds memory access.CVE-2023-6346: Reported by Huang Xilin of Ant Group Light-Year Security Lab.CVE-2023-6347: Reported by Leecraso and Guang Gong of 360 Vulnerability Research Institute.CVE-2023-6348: Reported by Mark Brand of Google Project Zero. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |