Apple watchOS up to 3.1 ImageIO 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.9$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in Apple watchOS up to 3.1. This affects an unknown part of the component ImageIO. The manipulation results in memory corruption. This vulnerability is identified as CVE-2017-2432. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Apple watchOS up to 3.1 (Smartwatch Operating System). It has been classified as critical. Affected is an unknown function of the component ImageIO. 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 bug was discovered 03/27/2017. The weakness was released 03/27/2017 by John Villamil with Qihoo 360 Vulcan Team as HT207602 as confirmed advisory (Website) via ZDI (Zero Day Initiative). The advisory is available at support.apple.com. This vulnerability is traded as CVE-2017-2432 since 12/01/2016. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The advisory points out:

A memory corruption issue was addressed through improved input validation.

The vulnerability scanner Nessus provides a plugin with the ID 99134 (macOS 10.12.x < 10.12.4 Multiple Vulnerabilities (httpoxy)), 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 370348 (Apple Mac OS X Security Update Sierra 10.12.4, El Capitan 2017-001 and Yosemite 2017-001 Not Installed (APPLE-SA-2017-03-27-3)).

Upgrading to version 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 Tenable (99134) and SecurityFocus (BID 97137†). Entries connected to this vulnerability are available at VDB-93752, VDB-94628, VDB-95275 and VDB-98611. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 6.7

VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 99134
Nessus Name: macOS 10.12.x < 10.12.4 Multiple Vulnerabilities (httpoxy)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 801105
OpenVAS Name: Apple Mac OS X Multiple Memory Corruption Vulnerabilities-HT207615
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

Timelineinfo

12/01/2016 🔍
03/27/2017 +116 days 🔍
03/27/2017 +0 days 🔍
03/27/2017 +0 days 🔍
03/27/2017 +0 days 🔍
03/28/2017 +1 days 🔍
03/31/2017 +3 days 🔍
04/01/2017 +1 days 🔍
10/29/2024 +2767 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT207602
Researcher: John Villamil
Organization: Qihoo 360 Vulcan Team
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-2432 (🔍)
GCVE (CVE): GCVE-0-2017-2432
GCVE (VulDB): GCVE-100-98826
SecurityFocus: 97137 - Apple iOS/tvOS/macOS/watchOS Multiple Security Vulnerabilities
OSVDB: - CVE-2017-2432 - Apple - Multiple Products - Memory Corruption Issue
SecurityTracker: 1038138

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

Entryinfo

Created: 03/28/2017 11:59
Updated: 10/29/2024 00:10
Changes: 03/28/2017 11:59 (67), 08/22/2020 11:25 (17), 11/21/2022 13:40 (4), 11/21/2022 13:47 (1), 10/29/2024 00:10 (21)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

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!