![]() ![]() Users are happy to know they’re running an up-to-date and secure browser version including modern Web Platform features, browser features, and bug fixes at all times. One of Chrome’s most notable features is its ability to auto-update. # Auto-update: great for users, painful for developers Today, we’re announcing a change that hopefully eases some of this pain. At the same time, setting up an adequate browser testing environment is notoriously difficult, so much so that it’s consistently reported as a top web developer pain point. # Backgroundīrowser testing is a vital component of creating a high-quality web experience, regardless of whether it is done manually or automatically. Chrome for Testing has been created purely for browser automation and testing purposes, and is not suitable for daily browsing. Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL. We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. 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. Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |