Google Android up to 5.1.1 LMY49C/6.0 Widevine QSEE TrustZone Application access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Android up to 5.1.1 LMY49C/6.0 and classified as critical. The affected element is an unknown function of the component Widevine QSEE TrustZone Application. Performing a manipulation results in access control. This vulnerability is reported as CVE-2015-6639. The attack requires a local approach. Moreover, an exploit is present. The affected component should be upgraded.
Details
A vulnerability was found in Google Android up to 5.1.1 LMY49C/6.0 (Smartphone Operating System). It has been classified as critical. This affects an unknown part of the component Widevine QSEE TrustZone Application. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The Widevine QSEE TrustZone application in Android 5.x before 5.1.1 LMY49F and 6.0 before 2016-01-01 allows attackers to gain privileges via a crafted application that leverages QSEECOM access, aka internal bug 24446875.
The weakness was disclosed 01/06/2016 by Marco Grassi with KeenTeam as 24446875 as confirmed bug report (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2015-6639 since 08/21/2015. The exploitability is told to be difficult. 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. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
A public exploit has been developed by laginimaineb and been published 5 months after the advisory. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k.
Upgrading to version 5.1.1 LMY49F or 6.0 2016-01-01 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (39757), SecurityFocus (BID 79846†) and Vulnerability Center (SBV-55613†). The entries VDB-80093, VDB-80094, VDB-80095 and VDB-80096 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 1.0
- 1.1
- 1.5
- 1.6
- 2.0
- 2.0.1
- 2.1
- 2.2
- 2.2.1
- 2.2.2
- 2.2.3
- 2.3
- 2.3.1
- 2.3.2
- 2.3.3
- 2.3.4
- 2.3.5
- 2.3.6
- 2.3.7
- 3.0
- 3.1
- 3.2
- 3.2.1
- 3.2.2
- 3.2.3
- 3.2.4
- 3.2.5
- 3.2.6
- 4.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.0.4
- 4.1
- 4.1.1
- 4.1.2
- 4.2
- 4.2.1
- 4.2.2
- 4.3
- 4.3.1
- 4.4
- 4.4.1
- 4.4.2
- 4.4.3
- 4.4.4
- 5.0
- 5.0.1
- 5.0.2
- 5.1
- 5.1.1
- 5.1.1 LMY49C
- 6.0
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.8
VulDB Temp Score: 7.0
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-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: laginimaineb
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Upgrade: Android 5.1.1 LMY49F/6.0 2016-01-01
Timeline
08/21/2015 🔍01/01/2016 🔍
01/04/2016 🔍
01/04/2016 🔍
01/06/2016 🔍
01/06/2016 🔍
01/07/2016 🔍
01/11/2016 🔍
05/02/2016 🔍
05/02/2016 🔍
06/10/2024 🔍
Sources
Vendor: google.comAdvisory: 24446875
Researcher: Marco Grassi
Organization: KeenTeam
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2015-6639 (🔍)
GCVE (CVE): GCVE-0-2015-6639
GCVE (VulDB): GCVE-100-80097
SecurityFocus: 79846 - Google Android Widevine QSEE TrustZone Multiple Privilege Escalation Vulnerabilities
SecurityTracker: 1034592
Vulnerability Center: 55613 - Google Android 5.0, 5.1.1, 6.0 and 6.0.1 Remote Privilege Escalation in Widevine QSEE TrustZone - CVE-2015-6639, Critical
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 01/07/2016 09:44Updated: 06/10/2024 19:56
Changes: 01/07/2016 09:44 (65), 06/20/2018 08:51 (19), 07/02/2022 14:10 (3), 06/10/2024 19:56 (15)
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.