The internet giant made no mention of any of these vulnerabilities being exploited in attacks. Per Google’s policy, no bug bounty reward will be issued for these flaws, as they were reported by Google Project Zero security researchers. The latest Chrome 111 update also brings patches for two out-of-bounds read issues in GPU Video and ANGLE. The internet giant says it paid out a $7,000 bounty for the PDF flaw, but has yet to determine the amounts to be paid for the other two bugs. Three other use-after-free issues were addressed in PDF, in the ANGLE graphics engine, and in WebProtect. This can be used to define which reports have some data and to filter out reports without data,” Walters said. When these reports are received, the report buffer should contain only the report ID byte and no other data. It’s possible for a HID device to define its report descriptor so that one or more reports have no data fields within the report.
“The vulnerability can handle empty input reports. Next in line is CVE-2023-1529, an out-of-bounds memory access in WebHID, for which Google paid an $8,000 bug bounty. An attacker can gain access to the vulnerable password,” Action1 VP Mike Walters told SecurityWeek in an emailed comment. “It hides the password leak detection dialog before displaying the account selector, which means that the password leak detection dialog shouldn’t be opened before you have selected your Google account. Google this week announced a Chrome 111 update that brings patches for eight vulnerabilities, including seven flaws that were reported by external researchers.Īll seven of the externally reported issues are high-severity memory safety bugs, with four of them described as use-after-free vulnerabilities, a type of bug that could lead to arbitrary code execution, data corruption, or denial of service.īased on the bug bounty reward handed out ($10,000), the most important of these vulnerabilities is CVE-2023-1528, a use-after-free flaw in Chrome’s Passwords component.
0 kommentar(er)
