Google Android WMA Roam Synchronization memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android. This affects an unknown part of the component WMA Roam Synchronization Handler. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2018-11863. The attack needs to be approached locally. There is no available exploit. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability, which was classified as critical, was found in Google Android (Smartphone Operating System) (affected version not known). This affects some unknown functionality of the component WMA Roam Synchronization Handler. 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. The summary by CVE is:
In all android releases(Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the linux kernel, lack of check of input received from firmware to calculate the length of WMA roam synch buffer can lead to buffer overwrite during memcpy.
The bug was discovered 09/04/2018. The weakness was presented 09/18/2018 (Website). It is possible to read the advisory at source.codeaurora.org. This vulnerability is uniquely identified as CVE-2018-11863 since 06/07/2018. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/17/2023). It is expected to see the exploit prices for this product increasing in the near future.
The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
See VDB-124205, VDB-124204, VDB-124202 and VDB-124201 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
06/07/2018 🔍09/04/2018 🔍
09/18/2018 🔍
09/18/2018 🔍
09/19/2018 🔍
05/17/2023 🔍
Sources
Vendor: google.comAdvisory: source.codeaurora.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-11863 (🔍)
GCVE (CVE): GCVE-0-2018-11863
GCVE (VulDB): GCVE-100-124203
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/19/2018 06:56Updated: 05/17/2023 07:21
Changes: 09/19/2018 06:56 (59), 03/24/2020 21:41 (2), 05/17/2023 07:21 (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.