Apple iOS up to 9.2 AppleUSBNetworking memory corruption

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

Summaryinfo

A vulnerability was found in Apple iOS up to 9.2. It has been classified as critical. This affects an unknown function of the component AppleUSBNetworking. The manipulation leads to memory corruption. This vulnerability is referenced as CVE-2016-1734. It is possible to launch the attack on the physical device. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Apple iOS up to 9.2 (Smartphone Operating System). It has been rated as critical. This issue affects an unknown code block of the component AppleUSBNetworking. 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 confidentiality, integrity, and availability. The summary by CVE is:

AppleUSBNetworking in Apple iOS before 9.3 and OS X before 10.11.4 allows physically proximate attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via a crafted USB device.

The weakness was published 03/21/2016 as HT206166 as confirmed advisory (Website). The advisory is shared at support.apple.com. The identification of this vulnerability is CVE-2016-1734 since 01/13/2016. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/11/2022). It is expected to see the exploit prices for this product increasing in the near future. The advisory points out:

A memory corruption issue existed in the parsing of data from USB devices. This issue was addressed through improved input validation.

The vulnerability scanner Nessus provides a plugin with the ID 90096 (Mac OS X 10.11.x < 10.11.4 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family MacOS X Local Security Checks and running in the context c. The commercial vulnerability scanner Qualys is able to test this issue with plugin 124842 (Apple Mac OS X v10.11.4 and Security Update 2016-002 Not Installed (APPLE-SA-2016-03-21-5)).

Upgrading to version 9.3 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 Tenable (90096), SecurityFocus (BID 71820†) and Vulnerability Center (SBV-57522†). Similar entries are available at VDB-68484, VDB-73556, VDB-80199 and VDB-81414. 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: 6.8
VulDB Meta Temp Score: 6.6

VulDB Base Score: 6.8
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Yes
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 90096
Nessus Name: Mac OS X 10.11.x < 10.11.4 Multiple Vulnerabilities
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: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: iOS 9.3

Timelineinfo

01/13/2016 🔍
03/21/2016 +68 days 🔍
03/21/2016 +0 days 🔍
03/21/2016 +0 days 🔍
03/22/2016 +1 days 🔍
03/22/2016 +0 days 🔍
03/23/2016 +1 days 🔍
03/23/2016 +0 days 🔍
07/11/2022 +2301 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT206166
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-1734 (🔍)
GCVE (CVE): GCVE-0-2016-1734
GCVE (VulDB): GCVE-100-81485
SecurityFocus: 71820
SecurityTracker: 1035353
Vulnerability Center: 57522 - Apple iOS <9.3 Local Code Execution in AppleUSBNetworking, High

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

Entryinfo

Created: 03/23/2016 12:43
Updated: 07/11/2022 10:23
Changes: 03/23/2016 12:43 (71), 02/02/2019 10:57 (15), 07/11/2022 10:23 (3)
Complete: 🔍
Cache ID: 216::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 know what is going to be exploited?

We predict KEV entries!