Google Android 4.4.3/5.0.1/5.1.0 Mediaserver access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android 4.4.3/5.0.1/5.1.0. This affects an unknown function of the component Mediaserver. This manipulation causes access control. This vulnerability appears as CVE-2016-2448. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in Google Android 4.4.3/5.0.1/5.1.0 (Smartphone Operating System). It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component Mediaserver. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was presented 05/02/2016 as Android Security Bulletin - May 2016 as confirmed advisory (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2016-2448 since 02/18/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/27/2022). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 4.4.4, 5.0.2, 5.1.1, 6.0 or 6.0.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
See VDB-80659, VDB-80660, VDB-80661 and VDB-83098 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
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: 🔍
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Android 4.4.4/5.0.2/5.1.1/6.0/6.0.1
Timeline
02/18/2016 🔍05/02/2016 🔍
05/02/2016 🔍
05/03/2016 🔍
05/09/2016 🔍
07/27/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - May 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-2448 (🔍)
GCVE (CVE): GCVE-0-2016-2448
GCVE (VulDB): GCVE-100-83113
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 05/03/2016 10:57Updated: 07/27/2022 15:43
Changes: 05/03/2016 10:57 (62), 11/06/2018 08:11 (2), 07/27/2022 15:43 (4)
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.