Google Android 4.4.3/5.0.1/5.1/6.0 Mediaserver input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Google Android 4.4.3/5.0.1/5.1/6.0. This affects an unknown part of the component Mediaserver. Executing a manipulation can lead to input validation. This vulnerability is handled as CVE-2016-3830. It is possible to launch the attack on the local host. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Google Android 4.4.3/5.0.1/5.1/6.0 (Smartphone Operating System). It has been declared as problematic. This vulnerability affects an unknown code block of the component Mediaserver. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect availability.
The weakness was released 08/01/2016 by Hao Sun as Android Security Bulletin - August 2016 as confirmed security bulletin (Website). The advisory is available at source.android.com. This vulnerability was named CVE-2016-3830 since 03/30/2016. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
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 vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92221†). Entries connected to this vulnerability are available at VDB-90455, VDB-90456, VDB-90457 and VDB-90458. 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: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Input validationCWE: CWE-20
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
03/30/2016 🔍08/01/2016 🔍
08/01/2016 🔍
08/01/2016 🔍
08/05/2016 🔍
08/06/2016 🔍
09/12/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - August 2016
Researcher: Hao Sun
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3830 (🔍)
GCVE (CVE): GCVE-0-2016-3830
GCVE (VulDB): GCVE-100-90466
SecurityFocus: 92221 - Google Android Mediaserver Multiple Denial of Service Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 08/06/2016 14:02Updated: 09/12/2022 07:19
Changes: 08/06/2016 14:02 (57), 03/19/2019 08:35 (13), 09/12/2022 07:19 (4)
Complete: 🔍
Cache ID: 216::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.