Google Android Linux Kernel get_metadata memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Google Android. This issue affects the function get_metadata of the component Linux Kernel. The manipulation results in memory corruption.
This vulnerability is reported as CVE-2017-11019. The attack requires a local approach. No exploit exists.
A patch should be applied to remediate this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version unknown). It has been classified as problematic. Affected is the function get_metadata of the component Linux Kernel. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on 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, the fd allocated during the get_metadata was not closed even though the buffer allocated to the fd was freed. This resulted in a failure during exit sequence.
The bug was discovered 12/06/2017. The weakness was disclosed 12/05/2017 (Website). The advisory is available at source.android.com. This vulnerability is traded as CVE-2017-11019 since 07/07/2017. The exploitability is told to be easy. Local access is required to approach this attack. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 12/21/2019). 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 entries VDB-101212, VDB-102646, VDB-110201 and VDB-110203 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit 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.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.9
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
07/07/2017 🔍12/05/2017 🔍
12/05/2017 🔍
12/05/2017 🔍
12/06/2017 🔍
12/21/2019 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-11019 (🔍)
GCVE (CVE): GCVE-0-2017-11019
GCVE (VulDB): GCVE-100-110202
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 12/05/2017 21:40Updated: 12/21/2019 08:40
Changes: 12/05/2017 21:40 (59), 12/21/2019 08:40 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.