Google Android GPS Location Wireless Interface use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.4 | $5k-$25k | 0.00 |
Summary
A vulnerability described as critical has been identified in Google Android. The affected element is an unknown function of the component GPS Location Wireless Interface. Executing a manipulation can lead to use after free. This vulnerability appears as CVE-2017-14918. The attack may be performed from remote. There is no available exploit. Applying a patch is advised to resolve this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (unknown version). It has been declared as very critical. This vulnerability affects an unknown code block of the component GPS Location Wireless Interface. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. 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, in the GPS location wireless interface, a Use After Free condition can occur.
The weakness was presented 12/05/2017 (Website). The advisory is shared for download at securityfocus.com. This vulnerability was named CVE-2017-14918 since 09/28/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/25/2021). It is expected to see the exploit prices for this product increasing in the near future.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 102072†). See VDB-110232, VDB-110233, VDB-110243 and VDB-110244 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: 9.8VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
09/28/2017 🔍12/04/2017 🔍
12/05/2017 🔍
12/05/2017 🔍
12/06/2017 🔍
01/25/2021 🔍
Sources
Vendor: google.comAdvisory: securityfocus.com⛔
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-14918 (🔍)
GCVE (CVE): GCVE-0-2017-14918
GCVE (VulDB): GCVE-100-110248
SecurityFocus: 102072
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 12/06/2017 08:11Updated: 01/25/2021 18:50
Changes: 12/06/2017 08:11 (40), 11/09/2019 13:02 (20), 01/25/2021 18:48 (2), 01/25/2021 18:50 (2)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.