| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been classified as critical. Affected by this issue is some unknown functionality of the component Secure File System. Performing a manipulation results in race condition. This vulnerability is identified as CVE-2016-10242. The attack is only possible with local access. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical has been found in Google Android (Smartphone Operating System) (unknown version). This affects an unknown code block of the component Secure File System. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A time-of-check time-of-use race condition could potentially exist in the secure file system in all Android releases from CAF using the Linux kernel.
The bug was discovered 04/01/2017. The weakness was released 05/16/2017 (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2016-10242 since 03/01/2017. An attack has to be approached locally. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 45 days. During that time the estimated underground price was around $5k-$25k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 98555†). Entries connected to this vulnerability are available at VDB-99354, VDB-99375, VDB-99376 and VDB-99383. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.0
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
03/01/2017 🔍04/01/2017 🔍
05/16/2017 🔍
05/16/2017 🔍
05/16/2017 🔍
05/17/2017 🔍
12/24/2020 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-10242 (🔍)
GCVE (CVE): GCVE-0-2016-10242
GCVE (VulDB): GCVE-100-101421
SecurityFocus: 98555 - Google Android Qualcomm Components CVE-2016-10242 Unspecified Security Vulnerability
OSVDB: - CVE-2016-10242 - Google - Android - High
SecurityTracker: 1038201
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 05/17/2017 08:02Updated: 12/24/2020 15:20
Changes: 05/17/2017 08:02 (67), 12/24/2020 15:20 (2)
Complete: 🔍
Cache ID: 216:E3B:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.