Fully patched Pixel 2 devices, even those running Android 10 preview, are impacted by a vulnerability that has already been abused in attacks, a Google Project Zero security researcher has discovered.
The issue, tracked as CVE-2019-2215, is a use-after-free in the binder driver that could result in an exploitable crash, Project Zero researcher Maddie Stone reveals.
The flaw was discovered during code review on a Pixel 2 with the most recent security patches, but was previously addressed in December 2017 in the 4.14 Linux kernel, the Android Open Source Project (AOSP) 3.18 kernel, AOSP 4.4 kernel, and AOSP 4.9 kernel.
In addition to Pixel 2 with Android 9 and Android 10 preview, source code review also revealed additional devices that are vulnerable, including Huawei P20; Xiaomi Redmi 5A, Redmi Note 5, and A1; Oppo A3; Motorola Moto Z3; LG phones running Android 8 Oreo; and Samsung Galaxy S7, S8 and S9.
The vulnerability, the researcher reveals, is being exploited in the wild. The available information, she says, points to an Android exploit attributed to the Israeli spyware company NSO, the developer of the infamous iOS malware Pegasus.
Stone explains that technical details she has received include information on the bug and exploit methodology, such as the fact that the exploit is “a kernel privilege escalation using a use-after free vulnerability, accessible from inside the Chrome sandbox.”
The security flaw was allegedly being used or sold by NSO and is said to work on Pixel 1 as well, although it does not impact Pixel 3 and 3a.
The bug was apparently addressed in version 4.14 of the Linux kernel without a CVE being assigned, and is exploitable in Chrome’s renderer processes under Android’s ‘isolated_app’ SELinux domain.
By comparing the information with her own discovery, the researcher concluded that the bug targeted by the NSO exploit “is almost certainly” the same use-after-free she discovered.
“I ruled out other potential candidates by comparing patches. […] We do not currently have a sample of the exploit. Without samples, we have neither been able to confirm the timeline nor the payload,” Stone points out.
An attacker able to exploit the vulnerability to escalate privileges could fully compromise the target device. Exploitation requires the presence of a malicious application on the vulnerable system.
“If the exploit is delivered via the web, it only needs to be paired with a renderer exploit, as this vulnerability is accessible through the sandbox,” she explains.
Google has apparently acknowledged the flaw as High severity and plans on addressing it with the October 2019 set of patches.