Google Android Qualcomm integer overflow

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.
9.6$5k-$25k0.08

Summaryinfo

A vulnerability was found in Google Android. It has been classified as problematic. The impacted element is an unknown function of the component Qualcomm Component. This manipulation causes integer overflow. This vulnerability is handled as CVE-2016-5080. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in Google Android (Smartphone Operating System) (unknown version) and classified as critical. Affected by this vulnerability is an unknown code block of the component Qualcomm Component. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect confidentiality, integrity, and availability.

The bug was discovered 05/26/2016. The weakness was released 01/05/2017 as Android Security Bulletin - January 2017 as confirmed advisory (Website). The advisory is shared at source.android.com. The public release was coordinated with Google. This vulnerability is known as CVE-2016-5080 since 05/26/2016. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/13/2025). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability was handled as a non-public zero-day exploit for at least 54 days. During that time the estimated underground price was around $100k and more.

Upgrading 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 91836†). Entries connected to this vulnerability are available at VDB-90138, VDB-90260, VDB-90449 and VDB-91385. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.6

VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Integer overflow
CWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
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: 🔍

Timelineinfo

05/26/2016 🔍
05/26/2016 +0 days 🔍
07/19/2016 +54 days 🔍
07/19/2016 +0 days 🔍
01/04/2017 +169 days 🔍
01/05/2017 +1 days 🔍
01/05/2017 +0 days 🔍
01/13/2025 +2930 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Android Security Bulletin - January 2017
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2016-5080 (🔍)
GCVE (CVE): GCVE-0-2016-5080
GCVE (VulDB): GCVE-100-94981
CERT: 🔍
SecurityFocus: 91836 - Objective Systems ASN1C CVE-2016-5080 Heap Based Buffer Overflow Vulnerability
OSVDB: - CVE-2016-5080 - Objective Systems - ASN1C - Integer Overflow Issue
SecurityTracker: 1036386

scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍

Entryinfo

Created: 01/04/2017 18:43
Updated: 01/13/2025 04:02
Changes: 01/04/2017 18:43 (58), 07/14/2020 09:33 (14), 10/27/2022 11:30 (4), 01/13/2025 04:02 (15)
Complete: 🔍
Cache ID: 216:C25:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!