Apple iOS up to 9.3.1 IOAcceleratorFamily 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.
7.9$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Apple iOS up to 9.3.1. The impacted element is an unknown function of the component IOAcceleratorFamily. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2016-1819. Additionally, an exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Apple iOS up to 9.3.1 (Smartphone Operating System). This affects an unknown functionality of the component IOAcceleratorFamily. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was released 05/16/2016 by Ian Beer (moony li) with Google Project Zero as HT206568 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2016-1819 since 01/13/2016. An attack has to be approached locally. The successful exploitation needs a authentication. Technical details are unknown but a public exploit is available. The advisory points out:

Multiple memory corruption issues were addressed through improved memory handling.

A public exploit has been developed by Google Security Research and been published 4 weeks after the advisory. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 91228 (Mac OS X 10.11.x < 10.11.5 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 122912 (Apple Mac OS X v10.11.5 and Security Update 2016-003 Not Installed (APPLE-SA-2016-05-16-4)).

Upgrading to version 9.3.2 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 (39928), Tenable (91228) and SecurityFocus (BID 90694†). Entries connected to this vulnerability are available at VDB-87425, VDB-87434, VDB-87435 and VDB-87436. 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: 8.3
VulDB Meta Temp Score: 7.9

VulDB Base Score: 8.8
VulDB Temp Score: 7.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.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: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Google Security Research
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 91228
Nessus Name: Mac OS X 10.11.x < 10.11.5 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 881901
OpenVAS Name: Apple Mac OS X Multiple Vulnerabilities-01 November-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: 🔍

Upgrade: iOS 9.3.2

Timelineinfo

01/13/2016 🔍
05/16/2016 +124 days 🔍
05/16/2016 +0 days 🔍
05/16/2016 +0 days 🔍
05/18/2016 +2 days 🔍
05/19/2016 +1 days 🔍
05/20/2016 +1 days 🔍
06/10/2016 +21 days 🔍
06/10/2016 +0 days 🔍
11/05/2024 +3070 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT206568
Researcher: Ian Beer (moony li)
Organization: Google Project Zero
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-1819 (🔍)
GCVE (CVE): GCVE-0-2016-1819
GCVE (VulDB): GCVE-100-87501
SecurityFocus: 90694 - Apple Mac OS X/watchOS/iOS Multiple Security Vulnerabilities
SecurityTracker: 1035890

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

Entryinfo

Created: 05/18/2016 12:18
Updated: 11/05/2024 20:19
Changes: 05/18/2016 12:18 (79), 12/01/2018 23:50 (13), 08/21/2022 08:57 (5), 11/05/2024 20:19 (16)
Complete: 🔍
Cache ID: 216:E50: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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!