Google Android 8.0 diag_dbgfs_read_table race condition

Summaryinfo

A vulnerability was found in Google Android 8.0 and classified as problematic. This affects the function diag_dbgfs_read_table. Executing a manipulation can lead to race condition. This vulnerability is tracked as CVE-2017-9697. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability was found in Google Android 8.0 (Smartphone Operating System). It has been declared as problematic. This vulnerability affects the function diag_dbgfs_read_table. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, a race condition can allow access to already freed memory while reading command registration table entries in diag_dbgfs_read_table.

The bug was discovered 10/05/2017. The weakness was disclosed 10/10/2017 (Website). The advisory is shared for download at source.android.com. This vulnerability was named CVE-2017-9697 since 06/15/2017. The attack needs to be approached locally. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/16/2021). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $5k-$25k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 101160†). The entries VDB-98332, VDB-107387, VDB-107403 and VDB-107404 are pretty similar. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Smartphone Operating System

Vendor

• Google

Name

• Android

Version

• 8.0

License

• free

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion