Often, bugs of this sort will cause the software to crash completely, by messing up calculations or memory access in an unrecoverable way. …only to carry on using that memory anyway, thus potentially causing one part of Chrome to rely on data it thought it could trust, without realising that another part of the software might still be tampering with that data.

CVE-2022-2861: Inappropriate implementation in Extensions API.Īs you can see, seven of these bugs were caused by memory mismanagement.Ī use-after-free vulnerability means that one part of Chrome handed back a memory block that it wasn’t planning to use any more, so that it could be reallocated for use elsewhere in the software….CVE-2022-2860: Insufficient policy enforcement in Cookies.CVE-2022-2859: Use after free in Chrome OS Shell.CVE-2022-2856: Insufficient validation of untrusted input in Intents.CVE-2022-2853: Heap buffer overflow in Downloads.

CVE-2022-2858: Use after free in Sign-In Flow.CVE-2022-2857: Use after free in Blink.CVE-2022-2855: Use after free in ANGLE.CVE-2022-2854: Use after free in SwiftShader.CVE-2022-2852: Use after free in FedCM.Details about the updates are scant, given that Google, in common with many other vendors these days, restricts access to bug details “until a majority of users are updated with a fix”.īut Google’s release bulletin explicitly enumerates 10 of the 11 bugs, as follows:

Google chrome security update