Apple iOS up to 10.2.0 WebKit 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$5k-$25k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Apple iOS up to 10.2.0. The affected element is an unknown function of the component WebKit. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2017-2366. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Apple iOS up to 10.2.0 (Smartphone Operating System). It has been classified as critical. This affects some unknown functionality of the component WebKit. 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 01/19/2017. The weakness was disclosed 01/23/2017 by Kai Kang with Tencent as HT207482 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2017-2366 since 12/01/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/03/2022). It is expected to see the exploit prices for this product increasing in the near future. The advisory points out:

Multiple memory corruption issues were addressed through improved input validation.

The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $100k and more. The vulnerability scanner Nessus provides a plugin with the ID 97448 (Fedora 25 : webkitgtk4 (2017-0beb752b6e)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370283 (Apple Safari 10.0.3 Not Installed (APPLE-SA-2017-01-23-5)).

Upgrading to version 10.2.1 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 (97448) and SecurityFocus (BID 95733†). The entries VDB-95912, VDB-95921, VDB-95922 and VDB-95919 are pretty similar. 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.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: 97448
Nessus Name: Fedora 25 : webkitgtk4 (2017-0beb752b6e)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 802225
OpenVAS Name: Apple iCloud Multiple Code Execution Vulnerabilities Feb17 (Windows)
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: iOS 10.2.1

Timelineinfo

12/01/2016 🔍
01/19/2017 +49 days 🔍
01/23/2017 +4 days 🔍
01/23/2017 +0 days 🔍
01/23/2017 +0 days 🔍
01/25/2017 +2 days 🔍
02/20/2017 +26 days 🔍
03/01/2017 +9 days 🔍
11/03/2022 +2073 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT207482
Researcher: Kai Kang
Organization: Tencent
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-2366 (🔍)
GCVE (CVE): GCVE-0-2017-2366
GCVE (VulDB): GCVE-100-95937
SecurityFocus: 95733 - Apple iTunes/iCloud/Safari/iOS CVE-2017-2366 Multiple Memory Corruption Vulnerabilities
OSVDB: - CVE-2017-2366 - Apple - Multiple Products - Memory Corruption Issue
SecurityTracker: 1037668

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

Entryinfo

Created: 01/25/2017 11:35
Updated: 11/03/2022 15:32
Changes: 01/25/2017 11:35 (79), 07/31/2020 11:36 (8), 11/03/2022 15:32 (4)
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!