Google Android Linux Kernel wma_radio_chan_stats_event_handler integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Android and classified as critical. Affected by this issue is the function wma_radio_chan_stats_event_handler of the component Linux Kernel. This manipulation causes integer overflow.
This vulnerability is registered as CVE-2017-15854. The attack needs to be launched locally. No exploit is available.
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 unknown). Affected by this vulnerability is the function wma_radio_chan_stats_event_handler of the component Linux Kernel. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The value of fix_param->num_chans is received from firmware and if it is too large, an integer overflow can occur in wma_radio_chan_stats_event_handler() for the derived length len leading to a subsequent buffer overflow in all Android releases from CAF (Android for MSM, Firefox OS for MSM, QRD Android) using the Linux Kernel.
The bug was discovered 05/11/2018. The weakness was published 06/12/2018 (Website). It is possible to read the advisory at source.android.com. This vulnerability is known as CVE-2017-15854 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 32 days. During that time the estimated underground price was around $25k-$100k.
Applying a patch is able to eliminate this problem.
Similar entries are available at VDB-117580, VDB-117581, VDB-119393 and VDB-119394. 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: Integer overflowCWE: CWE-190 / CWE-189
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
10/24/2017 🔍05/11/2018 🔍
06/12/2018 🔍
06/12/2018 🔍
06/13/2018 🔍
02/18/2020 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
CVE: CVE-2017-15854 (🔍)
GCVE (CVE): GCVE-0-2017-15854
GCVE (VulDB): GCVE-100-119395
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 06/13/2018 08:29Updated: 02/18/2020 13:48
Changes: 06/13/2018 08:29 (60), 02/18/2020 13:48 (1)
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.