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 classified as critical has been found in Google Android 4.4.3/5.0.1/5.1.0. Affected by this issue is some unknown functionality of the component Mediaserver. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2016-2452. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Google Android 4.4.3/5.0.1/5.1.0 (Smartphone Operating System). This issue affects some unknown processing of the component Mediaserver. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 05/02/2016 as Android Security Bulletin - May 2016 as confirmed advisory (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2016-2452 since 02/18/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. 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.
The entries VDB-83098, VDB-83089, VDB-83106 and VDB-83105 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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
CVE: CVE-2016-2452 (🔍)
GCVE (CVE): GCVE-0-2016-2452
GCVE (VulDB): GCVE-100-83117
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 05/03/2016 10:57Updated: 07/27/2022 16:06
Changes: 05/03/2016 10:57 (62), 11/06/2018 08:10 (1), 07/27/2022 16:06 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.