Apple watchOS up to 3.2.1 Kernel race condition

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

Summaryinfo

A vulnerability has been found in Apple watchOS up to 3.2.1 and classified as critical. Affected by this vulnerability is an unknown functionality of the component Kernel. The manipulation leads to race condition. This vulnerability is documented as CVE-2017-2501. The attack needs to be performed locally. Additionally, an exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Apple watchOS up to 3.2.1 (Smartwatch Operating System). It has been rated as critical. This issue affects an unknown part of the component Kernel. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. Impacted is confidentiality, integrity, and availability.

The bug was discovered 05/10/2017. The weakness was released 05/15/2017 by Ian Beer (OSS-Fuzz) with Google Project Zero as HT207800 as confirmed advisory (Website). The advisory is shared at support.apple.com. The identification of this vulnerability is CVE-2017-2501 since 12/01/2016. An attack has to be approached locally. A simple authentication is necessary for exploitation. Technical details are unknown but a public exploit is available. The advisory points out:

A race condition was addressed through improved locking.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 100256 (Apple TV < 10.2.1 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Misc. and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370396 (Apple macOS Sierra Security Update 10.12.5, El Capitan 2017-002 and Yosemite 2017-002 Not Installed (2017-002)).

Upgrading to version 3.2.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 (42054), Tenable (100256) and SecurityFocus (BID 98468†). Entries connected to this vulnerability are available at VDB-101294, VDB-101254, VDB-101255 and VDB-101256. Several companies clearly confirm that VulDB is the primary source for best 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.9
VulDB Meta Temp Score: 7.5

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

NVD Base Score: 7.0
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 100256
Nessus Name: Apple TV < 10.2.1 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 801105
OpenVAS Name: Apple Mac OS X Multiple Vulnerabilities-HT207797
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: watchOS 3.2.2

Timelineinfo

12/01/2016 🔍
05/10/2017 +160 days 🔍
05/15/2017 +5 days 🔍
05/15/2017 +0 days 🔍
05/15/2017 +0 days 🔍
05/16/2017 +1 days 🔍
05/17/2017 +1 days 🔍
05/22/2017 +5 days 🔍
02/10/2025 +2821 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT207800
Researcher: Ian Beer (OSS-Fuzz)
Organization: Google Project Zero
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-2501 (🔍)
GCVE (CVE): GCVE-0-2017-2501
GCVE (VulDB): GCVE-100-101321
SecurityFocus: 98468 - Apple iOS/WatchOS/tvOS/macOS Multiple Security Vulnerabilities
OSVDB: - CVE-2017-2501 - Apple - Multiple Products - Code Execution Issue
SecurityTracker: 1038484

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

Entryinfo

Created: 05/16/2017 09:10
Updated: 02/10/2025 01:24
Changes: 05/16/2017 09:10 (80), 09/27/2020 17:59 (11), 12/24/2020 07:33 (4), 02/10/2025 01:24 (15)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!