A previously unseen Chrome bug has been caught being exploited “in the wild”, with Google pushing out a patch this week to its billions of users within a day of the vulnerability being reported to it by security researchers.
The first, CVE-2019-13720, is a “use-after-free” vulnerability (a class of memory corruption bug) in the browser’s audio component and was reported by Anton Ivanov and Alexey Kulaev from Kaspersky Labs on October 29.
A few days ago our technologies caught a new Chrome 0day exploit used in the wild and we reported it to Google. Just released-Chrome 78 patches it, credits to my colleagues @antonivanovm and Alexey Kulaev for finding the bug. https://t.co/Bgm0QtNO2d
— Costin Raiu (@craiu) November 1, 2019
The second, CVE-2019-13721 is a use-after-free bug in PDFium (an open source software library to view, search, and print PDF documents that is bundled into Chrome) and was reported by “bananapenguin” (a quick search by Computer Business Review suggests that this is may be a Japanese programmer) on 2019-10-12.
Google said it is “aware of reports that an exploit for CVE-2019-13720 exists in the wild”, thanking “all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
It is not disclosing further details about the bugs until “a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.”
As Travis Biehn, the research lead at Synopsys, told Computer Business Review earlier this year in response to another memory corruption bug in Chrome: “Google Chrome is some of the most robustly engineered C and C++ code on the planet, the security teams working on Chrome are world-class.”
He added: “[But] despite Google’s security program… it still suffers from memory corruption attacks related to the use of C and C++. Luckily for the public, Chrome ships with an effective mechanism for update and patching – one that can get a critical fix out to end users in real time.”
In other Chrome news, it is finally shipping its WebXR device API in the latest version of Chrome, 17 months after pushing out a beta release.
“Developers can now create immersive experiences for smartphones and head-mounted displays. Other browsers will be supporting these specs soon, including Firefox Reality, Oculus Browser, Edge and Magic Leap’s Helio browser” it said.
See also: Update Chrome “Right This Minute” Warns Google
