Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. 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.This update includes
9 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the
Chrome Security Page for more information.
[TBD][
365376497] High CVE-2024-8904: Type Confusion in V8. Reported by Popax21 on 2024-09-08
[$8000][
359949835] Medium CVE-2024-8905: Inappropriate implementation in V8. Reported by Ganjiang Zhou(@refrain_areu) of ChaMd5-H1 team on 2024-08-15
[$2000][
352681108] Medium CVE-2024-8906: Incorrect security UI in Downloads. Reported by @retsew0x01 on 2024-07-12
[$1000][
360642942] Medium CVE-2024-8907: Insufficient data validation in Omnibox. Reported by Muhammad Zaid Ghifari on 2024-08-18
[$1000][
337222641] Low CVE-2024-8908: Inappropriate implementation in Autofill. Reported by Levit Nudi from Kenya on 2024-04-26
[$1000][
341353783] Low CVE-2024-8909: Inappropriate implementation in UI. Reported by Shaheen Fazim on 2024-05-18
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.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
[
367390865] Various fixes from internal audits, fuzzing and other initiatives
Many of our security bugs are detected using
AddressSanitizer,
MemorySanitizer,
UndefinedBehaviorSanitizer,
Control Flow Integrity,
libFuzzer, or
AFL.
