Google Android 4.4.3/5.0.1/5.1.0 Mediaserver memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as very critical was found in Google Android 4.4.3/5.0.1/5.1.0. The impacted element is an unknown function of the component Mediaserver. Such manipulation leads to memory corruption. This vulnerability is referenced as CVE-2016-2429. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as very critical, has been found in Google Android 4.4.3/5.0.1/5.1.0 (Smartphone Operating System). Affected by this issue is an unknown function of the component Mediaserver. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability.
The weakness was published 05/02/2016 as Android Security Bulletin - May 2016 as confirmed advisory (Website). The advisory is available at source.android.com. This vulnerability is handled as CVE-2016-2429 since 02/18/2016. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of 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.
As 0-day the estimated underground price was around $100k and more.
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.
Similar entries are available at VDB-80659, VDB-80660, VDB-80661 and VDB-83098. If you want to get best quality of vulnerability data, you may have to visit 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: 9.9VulDB Meta Temp Score: 9.6
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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-2429 (🔍)
GCVE (CVE): GCVE-0-2016-2429
GCVE (VulDB): GCVE-100-83090
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 05/03/2016 10:57Updated: 07/27/2022 15:04
Changes: 05/03/2016 10:57 (62), 11/07/2018 16:24 (2), 07/27/2022 15:04 (3)
Complete: 🔍
Cache ID: 216:CF1: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.