Chrome 71 Patches 43 Vulnerabilities

Friday, December 07, 2018

Ionut Arghire

Fa42af438e58b799189dd26386f5870f

Google this week released Chrome 71 to the stable channel with 43 security fixes inside, as well as with a series of additional protections to improve the overall user experience.

The new browser release completely eliminates inline installation of extensions by stripping Chrome off the inline install API method. Google set off on the path to remove the inline installation from its browser in June, when it prevented newly published extensions from accessing the option.

Chrome 71 also notifies users of unclear subscription pages, but only when it detects that the accessed page does not provide sufficient billing information. The warning will be displayed to both desktop and mobile users, and Google will also contact the affected webmasters to address the issue.

To further improve the user experience, Google has added protections from websites that employ abusing ad experiences, which are often used by scammers and phishers to steal user information. Chrome 71 will remove all ads on sites with persistent abusive experiences.

The new application release also patches tens of security vulnerabilities, including 34 issues that were reported by external researchers. Of these, 13 were rated High severity, 15 were Medium risk bugs, and 6 were considered Low severity.

Some of the most important security bugs addressed in Chrome 71 include use after free issues in PDFium, Blink, WebAudio, and MediaRecorder; out of bounds writes in V8; heap buffer overflows in Skia, Canvas, and Blink; inappropriate implementation in Extensions, and various issues in SQLite via WebSQL.

The resolved Medium risk bugs include inappropriate implementations in Site Isolation, Navigation, Omnibox, Media, and Network Authentication; insufficient policy enforcement in Blink, Navigation, URL Formatter, and Proxy; incorrect security UI in Blink; insufficient data validation in Shell Integration; use after free in Skia; and out of bounds read in V8.

The Low severity issues included inappropriate implementation in PDFium and Navigation; use after free in Extensions; and insufficient policy enforcement in Navigation and URL Formatter.

In its advisory, Google revealed it paid nearly $60000 in bug bounties to the security researchers who reported these bugs. Rated Medium, the inappropriate implementation in Site Isolation (CVE-2018-18345) was awarded the highest bug bounty, at $8000.

Related: Google Removes Inline Installation of Chrome Extensions

Related: Chrome 70 Updates Sign-In Options, Patches 23 Flaws

11368
Vulnerabilities
Post Rating I Like this!
The views expressed in this post are the opinions of the Infosec Island member that posted this content. Infosec Island is not responsible for the content or messaging of this post.

Unauthorized reproduction of this article (in part or in whole) is prohibited without the express written permission of Infosec Island and the Infosec Island member that posted this content--this includes using our RSS feed for any purpose other than personal use.