Google Android 4.4.4/5.0/5.1.1/6.0/6.0.1 Broadcom Wi-Fi Driver input validation

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.3$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Google Android 4.4.4/5.0/5.1.1/6.0/6.0.1. This vulnerability affects unknown code of the component Broadcom Wi-Fi Driver. The manipulation leads to input validation. This vulnerability is referenced as CVE-2016-0801. Remote exploitation of the attack is possible. Furthermore, an exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Google Android 4.4.4/5.0/5.1.1/6.0/6.0.1 (Smartphone Operating System). It has been rated as critical. This issue affects some unknown processing of the component Broadcom Wi-Fi Driver. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.

The weakness was published 02/01/2016 as Nexus Security Bulletin - February 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2016-0801 since 12/15/2015. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.

A public exploit has been developed by AbdSec and been published 4 months after the advisory. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 99 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 105133 (Fedora 26 : linux-firmware (2017-a253644369)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176821 (Debian Security Update for firmware-nonfree (DLA 1573-1)).

Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Exploit-DB (39801), Tenable (105133), SecurityFocus (BID 97367†) and Vulnerability Center (SBV-56315†). Similar entries are available at VDB-80766, VDB-80767, VDB-80768 and VDB-80769. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

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.3

VulDB Base Score: 9.8
VulDB Temp Score: 8.8
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: Input validation
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: AbdSec
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 105133
Nessus Name: Fedora 26 : linux-firmware (2017-a253644369)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 801105
OpenVAS Name: Apple Mac OS X Multiple Vulnerabilities-01 March-2016
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Timelineinfo

10/25/2015 🔍
10/25/2015 +0 days 🔍
12/15/2015 +51 days 🔍
02/01/2016 +47 days 🔍
02/01/2016 +0 days 🔍
02/01/2016 +0 days 🔍
02/02/2016 +0 days 🔍
02/06/2016 +4 days 🔍
05/11/2016 +94 days 🔍
05/11/2016 +0 days 🔍
12/10/2017 +579 days 🔍
06/08/2024 +2371 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: Nexus Security Bulletin - February 2016
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-0801 (🔍)
GCVE (CVE): GCVE-0-2016-0801
GCVE (VulDB): GCVE-100-80765
SecurityFocus: 97367
SecurityTracker: 1035353
Vulnerability Center: 56315 - Google Android Remote Code Execution due to Vulnerability in Broadcom Wi-Fi Driver - CVE-2016-0801, High

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

Entryinfo

Created: 02/02/2016 16:37
Updated: 06/08/2024 01:09
Changes: 02/02/2016 16:37 (63), 07/23/2018 07:35 (31), 07/06/2022 17:51 (5), 06/08/2024 01:09 (15)
Complete: 🔍
Cache ID: 216:98C: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 ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!