![]() ![]() High CVE-2023-4764: Incorrect security UI in BFCache. High CVE-2023-4763: Use after free in Networks. High CVE-2023-4762: Type Confusion in V8. High CVE-2023-4761: Out of bounds memory access in FedCM. ![]() 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. Google decided to make the change to push security updates quicker to user devices and reduce the time that malicious actors have to exploit reported vulnerabilities in the web browser.Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. The list of fixed security issues is shorter in individual releases and updates have doubled. Google switched to a weekly update schedule for its Chrome web browser recently, and it shows. It powers the browser's back and forward buttons and the linked functionality. The four issues address an out of bounds memory access in FedCM, type confusion in V8, use after free in Networks, and in incorrect security UI in BFCache issue.īFCache stands for Back Forward Cache. Google makes no mention of exploits in the wild, but users should still consider updating as soon as possible to avoid attacks that may come at a later point. ![]() Google lists four security updates on the official Chrome Releases blog and confirms that these are the only security issues fixed in the release.Īll of the four patched vulnerabilities are rated high, which is second only to critical.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |