| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been rated as problematic. The affected element is an unknown function of the component Mediaserver. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2016-3881. Local access is required to approach this attack. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability was found in Google Android (Smartphone Operating System) and classified as problematic. This issue affects 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 availability.
The weakness was disclosed 09/06/2016 by Security Team (Oliver) with Google Chrome Security Team as Android Security Bulletin - September 2016 as confirmed security bulletin (Website). It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2016-3881 since 03/30/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1 or 7.0 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 92821†). The entries VDB-91415, VDB-91416, VDB-91417 and VDB-91418 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
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: Memory corruptionCWE: CWE-119
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/7.0
Timeline
03/30/2016 🔍09/06/2016 🔍
09/06/2016 🔍
09/07/2016 🔍
09/11/2016 🔍
09/11/2016 🔍
09/15/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - September 2016
Researcher: Security Team (Oliver)
Organization: Google Chrome Security Team
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3881 (🔍)
GCVE (CVE): GCVE-0-2016-3881
GCVE (VulDB): GCVE-100-91427
SecurityFocus: 92821 - Google Android Mediaserver Multiple Denial of Service Vulnerabilities
SecurityTracker: 1036763
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/11/2016 12:29Updated: 09/15/2022 13:14
Changes: 09/11/2016 12:29 (54), 04/14/2019 06:52 (15), 09/15/2022 13:14 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.