Apple macOS up to 10.12.1 IOAcceleratorFamily Memory information disclosure

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Apple macOS up to 10.12.1. This impacts an unknown function of the component IOAcceleratorFamily. Performing a manipulation results in information disclosure (Memory). This vulnerability is cataloged as CVE-2016-7624. The attack must be initiated from a local position. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Apple macOS up to 10.12.1 (Operating System). It has been classified as problematic. This affects an unknown functionality of the component IOAcceleratorFamily. The manipulation with an unknown input leads to a information disclosure vulnerability (Memory). CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

An issue was discovered in certain Apple products. macOS before 10.12.2 is affected. The issue involves the "IOAcceleratorFamily" component. It allows local users to obtain sensitive kernel memory-layout information via unspecified vectors.

The bug was discovered 12/13/2016. The weakness was shared 12/13/2016 by daybreaker@Minionz with Zero Day Initiative as HT207423 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2016-7624 since 09/09/2016. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue. The advisory points out:

A shared memory issue was addressed through improved memory handling.

The vulnerability scanner Nessus provides a plugin with the ID 95917 (macOS 10.12.x < 10.12.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 370262 (Apple macOS Sierra Security Update 10.12.2 Not Installed (APPLE-SA-2016-12-13-1)).

Upgrading to version 10.12.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 (95917) and SecurityFocus (BID 94903†). The entries VDB-87463, VDB-91385, VDB-91659 and VDB-93261 are related to this item. 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: 3.3
VulDB Meta Temp Score: 3.2

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.3
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Name: Memory
Class: Information disclosure / Memory
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 95917
Nessus Name: macOS 10.12.x < 10.12.2 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 59236
OpenVAS Name: Apple Mac OS X Multiple Vulnerabilities-01 February-2017
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: macOS 10.12.2

Timelineinfo

09/09/2016 🔍
12/13/2016 +95 days 🔍
12/13/2016 +0 days 🔍
12/13/2016 +0 days 🔍
12/13/2016 +0 days 🔍
12/14/2016 +1 days 🔍
12/16/2016 +2 days 🔍
02/20/2017 +66 days 🔍
09/21/2024 +2769 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT207423
Researcher: daybreaker@Minionz
Organization: Zero Day Initiative
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-7624 (🔍)
GCVE (CVE): GCVE-0-2016-7624
GCVE (VulDB): GCVE-100-94389
SecurityFocus: 94903 - Apple macOS APPLE-SA-2016-12-13-1 Multiple Security Vulnerabilities
SecurityTracker: 1037469

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

Entryinfo

Created: 12/14/2016 13:45
Updated: 09/21/2024 01:54
Changes: 12/14/2016 13:45 (71), 07/06/2019 22:00 (14), 10/08/2022 06:29 (2), 09/21/2024 01:54 (16)
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!