Apple watchOS up to 3.1.2 CoreText 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.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Apple watchOS up to 3.1.2. Affected by this vulnerability is an unknown functionality of the component CoreText. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2016-7595. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Apple watchOS up to 3.1.2 (Smartwatch Operating System). Affected by this vulnerability is an unknown functionality of the component CoreText. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.

The bug was discovered 12/13/2016. The weakness was disclosed 01/23/2017 by daybreaker@Minionz with Trend Micro as HT207487 as confirmed advisory (Website). It is possible to read the advisory at support.apple.com. This vulnerability is known as CVE-2016-7595 since 09/09/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The advisory points out:

Multiple memory corruption issues existed in the handling of font files. These issues were addressed through improved bounds checking.

The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $5k-$25k. 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 3.1.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 (95917) and SecurityFocus (BID 94905†). The entries VDB-87463, VDB-91385, VDB-91659 and VDB-93261 are pretty similar. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.4

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

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

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: 801105
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: watchOS 3.1.3

Timelineinfo

09/09/2016 🔍
12/13/2016 +95 days 🔍
12/13/2016 +0 days 🔍
12/16/2016 +3 days 🔍
01/23/2017 +38 days 🔍
01/23/2017 +0 days 🔍
01/25/2017 +2 days 🔍
02/20/2017 +26 days 🔍
09/19/2024 +2768 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT207487
Researcher: daybreaker@Minionz
Organization: Trend Micro
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-7595 (🔍)
GCVE (CVE): GCVE-0-2016-7595
GCVE (VulDB): GCVE-100-95887
SecurityFocus: 94905 - Apple macOS/watchOS/iOS/tvOS Multiple Security Vulnerabilities
OSVDB: - CVE-2016-7595 - Apple - Multiple Products - Memory Corruption Issue
SecurityTracker: 1037469

See also: 🔍

Entryinfo

Created: 01/25/2017 11:21
Updated: 09/19/2024 21:02
Changes: 01/25/2017 11:21 (76), 07/31/2020 09:11 (8), 11/03/2022 12:13 (4), 09/19/2024 21:02 (16)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!