"Chrome 114 Released With 18 Security Fixes"

Google recently announced the release of Chrome 114 to the stable channel with a total of 18 security fixes inside, including 13 that resolve vulnerabilities reported by external researchers.  Of the externally reported flaws, eight have a severity rating of "high," with six of them being memory safety bugs.  Google noted that the most important of these flaws fixed is CVE-2023-2929, an out-of-bounds write issue in Swiftshader. Security researcher Jaehun Jeong received a $15,000 reward for reporting the flaw.  Next in line is CVE-2023-2930, a use-after-free bug in Extensions, for which Google handed out a $10,000 bug bounty.  Google noted that security researchers with Viettel Cyber Security reported three use-after-free vulnerabilities in the browser's PDF component, and each of them issued a $9,000 bug bounty reward.  The remaining externally reported high-severity issues addressed with this Chrome update include an out-of-bounds memory access flaw in Mojo and two type confusion bugs in the V8 JavaScript and WebAssembly engine.  All three issues were reported by Google Project Zero researchers, and per Google's policy, no bug bounty reward will be issued for any of them.  Google stated that Chrome 114 also resolves four medium-severity defects reported by external researchers, including three inappropriate implementation flaws in Picture and Downloads and one insufficient data validation bug in Installer.  A low-severity inappropriate implementation issue in the Extensions API was also addressed in this browser release.  In total, Google handed out more than $65,000 in bug bounty rewards to the security researchers who reported these vulnerabilities.  Google noted that the latest Chrome iteration is rolling out as version 114.0.5735.90 for Linux and macOS and as versions 114.0.5735.90/91 for Windows.  Google did not mention if these flaws were being exploited in malicious attacks.

 

SecurityWeek reports: "Chrome 114 Released With 18 Security Fixes"

Submitted by Anonymous on