Google Android up to 4.4.3/5.0.1/5.1.0/6.x Mediaserver AudioSource.cpp information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Google Android up to 4.4.3/5.0.1/5.1.0/6.x. This impacts an unknown function of the file AudioSource.cpp of the component Mediaserver. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2016-2499. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Google Android up to 4.4.3/5.0.1/5.1.0/6.x (Smartphone Operating System). Affected by this vulnerability is some unknown processing of the file AudioSource.cpp of the component Mediaserver. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
AudioSource.cpp in libstagefright in mediaserver in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-06-01 does not initialize certain data, which allows attackers to obtain sensitive information via a crafted application, aka internal bug 27855172.
The weakness was disclosed 06/13/2016 as 27855172 as confirmed advisory (Website). The advisory is shared at android.googlesource.com. This vulnerability is known as CVE-2016-2499 since 02/18/2016. An attack has to be approached locally. Required for exploitation is a single authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 4.4.4, 5.0.2, 5.1.1 or 6.0 2016-06-01 eliminates this vulnerability.
The entries VDB-87840, VDB-87841, VDB-87842 and VDB-87843 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
- 1.0
- 1.1
- 1.5
- 1.6
- 2.0
- 2.0.1
- 2.1
- 2.2
- 2.2.1
- 2.2.2
- 2.2.3
- 2.3
- 2.3.1
- 2.3.2
- 2.3.3
- 2.3.4
- 2.3.5
- 2.3.6
- 2.3.7
- 3.0
- 3.1
- 3.2
- 3.2.1
- 3.2.2
- 3.2.3
- 3.2.4
- 3.2.5
- 3.2.6
- 4.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.0.4
- 4.1
- 4.1.1
- 4.1.2
- 4.2
- 4.2.1
- 4.2.2
- 4.3
- 4.3.1
- 4.4
- 4.4.1
- 4.4.2
- 4.4.3
- 4.4.4
- 5.0
- 5.0.1
- 5.1.0
- 6.x
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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: 🔍
Upgrade: Android 4.4.4/5.0.2/5.1.1/6.0 2016-06-01
Timeline
02/18/2016 🔍06/12/2016 🔍
06/13/2016 🔍
06/13/2016 🔍
01/18/2019 🔍
Sources
Vendor: google.comAdvisory: 27855172
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-2499 (🔍)
GCVE (CVE): GCVE-0-2016-2499
GCVE (VulDB): GCVE-100-87877
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 06/13/2016 10:17Updated: 01/18/2019 08:31
Changes: 06/13/2016 10:17 (62), 01/18/2019 08:31 (2)
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.