Apple Mac OS X up to 10.11.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.
6.6$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Apple Mac OS X up to 10.11.1. Impacted is an unknown function of the component IOAcceleratorFamily. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2015-7109. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Apple Mac OS X up to 10.11.1 (Operating System). It has been classified as critical. This affects some 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 summary by CVE is:

IOAcceleratorFamily in Apple OS X before 10.11.2 and tvOS before 9.1 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via a crafted app.

The weakness was disclosed 12/08/2015 by Xin Li with TrendMicro as HT205637 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2015-7109 since 09/16/2015. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The advisory points out:

A memory corruption issue existed in IOAcceleratorFamily. This issue was addressed through improved memory handling.

The vulnerability scanner Nessus provides a plugin with the ID 87314 (Mac OS X 10.11.x < 10.11.2 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 124389 (Apple Mac OS X v10.11.2 and Security Update 2015-008 Not Installed (APPLE-SA-2015-12-08-3)).

Upgrading to version 10.11.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 Tenable (87314), SecurityFocus (BID 78733†) and Vulnerability Center (SBV-55239†). The entries VDB-79541, VDB-79545, VDB-79546 and VDB-79547 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Support

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

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: No
Local: No
Remote: Yes

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

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

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

Upgrade: Mac OS X 10.11.2

Timelineinfo

09/16/2015 🔍
12/08/2015 +83 days 🔍
12/08/2015 +0 days 🔍
12/08/2015 +0 days 🔍
12/08/2015 +0 days 🔍
12/09/2015 +1 days 🔍
12/10/2015 +1 days 🔍
12/11/2015 +1 days 🔍
12/15/2015 +4 days 🔍
11/12/2024 +3255 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT205637
Researcher: Xin Li
Organization: TrendMicro
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2015-7109 (🔍)
GCVE (CVE): GCVE-0-2015-7109
GCVE (VulDB): GCVE-100-79557
SecurityFocus: 78733 - Apple Mac OS X and tvOS Multiple Security Bypass and Memory Corruption Vulnerabilities
SecurityTracker: 1034344
Vulnerability Center: 55239 - Apple MacOS X <10.11.2 Remote Code Execution in IOAcceleratorFamily, Critical

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

Entryinfo

Created: 12/09/2015 14:04
Updated: 11/12/2024 07:45
Changes: 12/09/2015 14:04 (64), 05/14/2018 10:49 (15), 06/29/2022 13:11 (3), 06/29/2022 13:16 (1), 11/12/2024 07:45 (22)
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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!