Google has released Chrome 112, which includes patches for 16 vulnerabilities, 14 of which were reported by external researchers. Two of these vulnerabilities were rated as ‘high severity’, while nine were ranked as ‘medium’ and three were low-severity issues. The most serious vulnerability was a heap buffer overflow bug in Visuals, which could allow a compromised renderer to register multiple things with the same FrameSinkId, violating ownership assumptions.
At the same time, this vulnerability earned the reporting researcher a $5,000 bug bounty reward.
The use-after-free flaw in Frames, tracked as CVE-2023-1811, was another high-severity issue, which Google awarded a $3,000 bug bounty.
Furthermore, this flaw could lead to a crash or malicious code execution. The resolved medium-severity vulnerabilities include out-of-bounds memory access, inappropriate implementation, insufficient validation of untrusted input, use-after-free, incorrect security UI, insufficient policy enforcement, out-of-bounds read, and heap buffer overflow issues.
Several Chrome components were impacted by these vulnerabilities, including DOM Bindings, Extensions, Safe Browsing, Networking APIs, Picture In Picture, Intents, Vulkan, Accessibility, and Browser History.
Additionally, Google said it paid roughly $26,000 in bug bounty rewards for the reported vulnerabilities, but the final amount might be higher as the company has yet to determine the amount to be handed out for two of the bugs. Google’s policies stipulate that no rewards will be issued for two other vulnerabilities, which were reported by Microsoft researchers.
There is no indication that any of these vulnerabilities have been exploited in attacks. The latest version of Chrome, 112.0.5615.49/50 for Windows and 112.0.5615.49 for Linux and macOS, is now available.
