Apple iOS up to 9.3.2 libxml2 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.
9.4$5k-$25k0.00

Summaryinfo

A vulnerability described as critical has been identified in Apple iOS up to 9.3.2. This affects an unknown part of the component libxml2. Such manipulation leads to memory corruption. This vulnerability is documented as CVE-2016-4447. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Apple iOS up to 9.3.2 (Smartphone Operating System). Affected by this issue is an unknown code block of the component libxml2. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:

The xmlParseElementDecl function in parser.c in libxml2 before 2.9.4 allows context-dependent attackers to cause a denial of service (heap-based buffer underread and application crash) via a crafted file, involving xmlParseName.

The weakness was released 07/18/2016 with Nanyang Technological University as HT206902 as confirmed advisory (Website). The advisory is shared for download at support.apple.com. This vulnerability is handled as CVE-2016-4447 since 05/02/2016. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 09/05/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 memory handling.

The vulnerability scanner Nessus provides a plugin with the ID 93154 (SUSE SLES11 Security Update : libxml2 (SUSE-SU-2016:1604-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 43650 (Juniper Junos Multiple vulnerabilities in libxml2 (JSA10916)).

Upgrading to version 9.3.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 (93154) and SecurityFocus (BID 90864†). Entries connected to this vulnerability are available at VDB-79335, VDB-79336, VDB-79337 and VDB-79338. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.4

VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

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: 93154
Nessus Name: SUSE SLES11 Security Update : libxml2 (SUSE-SU-2016:1604-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 14611
OpenVAS Name: Amazon Linux Local Check: alas-2016-719
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
Exposure Time: 🔍

Upgrade: iOS 9.3.3
Patch: git.gnome.org

Timelineinfo

05/02/2016 🔍
05/23/2016 +21 days 🔍
06/09/2016 +17 days 🔍
07/18/2016 +39 days 🔍
07/18/2016 +0 days 🔍
07/19/2016 +1 days 🔍
08/29/2016 +41 days 🔍
09/05/2022 +2198 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT206902
Organization: Nanyang Technological University
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-4447 (🔍)
GCVE (CVE): GCVE-0-2016-4447
GCVE (VulDB): GCVE-100-89696

OVAL: 🔍

SecurityFocus: 90864 - Libxml2 'xmlParseName' CVE-2016-4447 Remote Denial of Service Vulnerability
SecurityTracker: 1036348

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

Entryinfo

Created: 07/19/2016 16:33
Updated: 09/05/2022 13:55
Changes: 07/19/2016 16:33 (45), 03/03/2019 09:10 (31), 09/05/2022 13:55 (3)
Complete: 🔍
Cache ID: 216:6BE:103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!