| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been declared as critical. The impacted element is an unknown function of the component WLAN FW. Executing a manipulation can lead to array index. This vulnerability is handled as CVE-2018-11299. It is possible to launch the attack on the local host. There is not any exploit available. A patch should be applied to remediate this issue.
Details
A vulnerability has been found in Google Android (Smartphone Operating System) (version now known) and classified as critical. This vulnerability affects some unknown processing of the component WLAN FW. The manipulation with an unknown input leads to a array index vulnerability. The CWE definition for the vulnerability is CWE-129. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. As an impact it is known to affect availability. CVE summarizes:
In all android releases(Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the linux kernel, when WLAN FW has not filled the vdev id correctly in stats events then WLAN host driver tries to access interface array without proper bound check which can lead to invalid memory access and as a side effect kernel panic or page fault.
The bug was discovered 09/04/2018. The weakness was released 09/18/2018 (Website). The advisory is available at source.codeaurora.org. This vulnerability was named CVE-2018-11299 since 05/18/2018. Local access is required to approach this attack. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
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.
Entries connected to this vulnerability are available at VDB-124189, VDB-124188, VDB-124187 and VDB-124185. 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.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: Array indexCWE: CWE-129 / 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
05/18/2018 🔍09/04/2018 🔍
09/18/2018 🔍
09/18/2018 🔍
09/19/2018 🔍
05/16/2023 🔍
Sources
Vendor: google.comAdvisory: source.codeaurora.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-11299 (🔍)
GCVE (CVE): GCVE-0-2018-11299
GCVE (VulDB): GCVE-100-124186
SecurityFocus: 107770
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/19/2018 06:49Updated: 05/16/2023 19:24
Changes: 09/19/2018 06:49 (60), 03/24/2020 19:54 (2), 05/16/2023 19:24 (5)
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.