Google addresses two new Chrome zero-day flaws

Google has released Chrome version 86.0.4240.198 that addresses two additional zero-day vulnerabilities that were exploited in the wild.

Google has addressed two zero-day vulnerabilities, actively exploited in the wild, with the release of Chrome version 86.0.4240.198.

The IT giant has fixed a total of five Chrome zero-day vulnerabilities in only three weeks.

Both zero-day flaws, tracked as CVE-2020-16013 and CVE-2020-16017, were reported by anonymous sources. Google experts did not disclose the way the flaws have been exploited in the attacks, for example, it is not clear if they were chained by threat actors.

“Google is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild.” reads the Chrome 86.0.4240.198 changelog.

“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.”

The CVE-2020-16013 flaw is an inappropriate implementation in V8 Chrome component, it was reported by anonymous on November 9, 2020.

The CVE-2020-16017 flaw is a use after free memory corruption bug in Site Isolation, it was reported by anonymous on November 7, 2020.

It is interesting to note that one of the vulnerabilities was reported to Google the same day the company released the new version of the popular browser.

The other three zero-days patched by Google in the last weeks were:

CVE-2020-15999 – The flaw is a memory corruption bug that resides in the FreeType font rendering library, which is included in standard Chrome releases.

– The flaw is a memory corruption bug that resides in the FreeType font rendering library, which is included in standard Chrome releases. CVE-2020-16009 – is a Heap buffer overflow in Freetype in Google Chrome.

– is a Heap buffer overflow in Freetype in Google Chrome. CVE-2020-16010 – affects the browser’s user interface (UI) component in Chrome for Android.

“Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.” concludes the Chrome changelog for the version 86.0.4240.198.

Source

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s