Google Android 4.4.3/5.0.1/5.1.0 Mediaserver information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

A vulnerability, which was classified as problematic, 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 functionality of the component Mediaserver. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.

The weakness was released 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-2459 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 $0-$5k 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.This vulnerability is assigned to T1592 by the MITRE ATT&CK project.

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.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Android 4.4.4/5.0.2/5.1.1/6.0/6.0.1

Timelineinfo

02/18/2016 🔍
05/02/2016 +74 days 🔍
05/02/2016 +0 days 🔍
05/03/2016 +1 days 🔍
05/09/2016 +6 days 🔍
07/27/2022 +2270 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - May 2016
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-2459 (🔍)
scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfo

Created: 05/03/2016 10:57 AM
Updated: 07/27/2022 04:27 PM
Changes: 05/03/2016 10:57 AM (63), 11/06/2018 08:08 AM (2), 07/27/2022 04:27 PM (4)
Complete: 🔍
Cache ID: 34:27A:40

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!