Google Android Linux Kernel wma_p2p_noa_event_handler memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Google Android. Affected by this issue is the function wma_p2p_noa_event_handler of the component Linux Kernel. This manipulation causes memory corruption.
This vulnerability appears as CVE-2017-15821. The attack requires local access. There is no available exploit.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as critical was found in Google Android (Smartphone Operating System) (the affected version is unknown). Affected by this vulnerability is the function wma_p2p_noa_event_handler of the component Linux Kernel. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, in the function wma_p2p_noa_event_handler(), there is no bound check on a value coming from firmware which can potentially lead to a buffer overwrite.
The bug was discovered 03/05/2018. The weakness was presented 03/15/2018 (Website). It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2017-15821 since 10/24/2017. The exploitation appears to be easy. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 10 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 103254†). See VDB-114373, VDB-114375, VDB-114638 and VDB-114639 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: 🔍
Patch: source.codeaurora.org
Timeline
10/24/2017 🔍03/05/2018 🔍
03/05/2018 🔍
03/15/2018 🔍
03/15/2018 🔍
03/16/2018 🔍
02/22/2023 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-15821 (🔍)
GCVE (CVE): GCVE-0-2017-15821
GCVE (VulDB): GCVE-100-114643
SecurityFocus: 103254 - Google Android Qualcomm Component Multiple Security Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/16/2018 08:11Updated: 02/22/2023 07:54
Changes: 03/16/2018 08:11 (62), 01/14/2020 08:16 (4), 02/22/2023 07:54 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.