| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Google Android. This impacts an unknown function of the component Qualcomm. Performing a manipulation results in access control. This vulnerability is cataloged as CVE-2017-11041. The attack must be initiated from a local position. There is no exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability classified as critical has been found in Google Android (Smartphone Operating System) (the affected version is unknown). This affects an unknown code of the component Qualcomm. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In all Qualcomm products with Android releases from CAF using the Linux kernel, an output buffer is accessed in one thread and can be potentially freed in another.
The weakness was shared 09/21/2017 by Alibaba with Qihoo 360 (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2017-11041 since 07/07/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 100658†). The entries VDB-101269, VDB-101388, VDB-101623 and VDB-106244 are related to this item. Several companies clearly confirm that VulDB is the primary source for best 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: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
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 🔍09/05/2017 🔍
09/21/2017 🔍
09/21/2017 🔍
09/21/2017 🔍
01/13/2021 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Researcher: Pengfei Ding, Chenfu Bao , Lenx Wei (Alibaba)
Organization: Qihoo 360
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-11041 (🔍)
GCVE (CVE): GCVE-0-2017-11041
GCVE (VulDB): GCVE-100-106929
SecurityFocus: 100658 - Google Android Qualcomm Components Multiple Security Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/21/2017 21:44Updated: 01/13/2021 16:16
Changes: 09/21/2017 21:44 (61), 11/18/2019 11:43 (4), 01/13/2021 16:16 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.