Apple iOS up to 10 libxml2 use after free

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.9$5k-$25k0.00

Summaryinfo

A vulnerability was found in Apple iOS up to 10. It has been classified as critical. This impacts an unknown function of the component libxml2. Performing a manipulation results in use after free. This vulnerability was named CVE-2016-5131. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Apple iOS up to 10 (Smartphone Operating System). It has been classified as critical. This affects an unknown code block of the component libxml2. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Use-after-free vulnerability in libxml2 through 2.9.4, as used in Google Chrome before 52.0.2743.82, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the XPointer range-to function.

The bug was discovered 07/20/2016. The weakness was presented 09/20/2016 by Nick Wellnhofer (Cloudfuzzer) with Tencent as HT207143 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2016-5131 since 05/31/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 12/04/2025). 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 was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $100k and more. The vulnerability scanner Nessus provides a plugin with the ID 92628 (Google Chrome < 52.0.2743.82 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 370091 (Google Chrome Prior to 52.0.2743.82 Multiple Vulnerabilities).

Upgrading 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 (92628) and SecurityFocus (BID 92053†). See VDB-90229, VDB-90230, VDB-90231 and VDB-90232 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.9

VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Use after free
CWE: CWE-416 / 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: 92628
Nessus Name: Google Chrome < 52.0.2743.82 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 801105
OpenVAS Name: Apple Mac OS X Multiple Vulnerabilities-01 September-2016
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: 🔍

Timelineinfo

05/31/2016 🔍
07/20/2016 +50 days 🔍
07/20/2016 +0 days 🔍
07/23/2016 +3 days 🔍
07/29/2016 +6 days 🔍
09/20/2016 +53 days 🔍
09/20/2016 +0 days 🔍
09/26/2016 +6 days 🔍
12/04/2025 +3356 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT207143
Researcher: Nick Wellnhofer (Cloudfuzzer)
Organization: Tencent
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-5131 (🔍)
GCVE (CVE): GCVE-0-2016-5131
GCVE (VulDB): GCVE-100-92013

OVAL: 🔍

SecurityFocus: 92053 - Google Chrome Prior to 52.0.2743.82 Multiple Security Vulnerabilities
SecurityTracker: 1036428

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

Entryinfo

Created: 09/26/2016 10:50
Updated: 12/04/2025 18:25
Changes: 09/26/2016 10:50 (68), 07/17/2019 15:39 (20), 09/20/2022 14:04 (3), 12/04/2025 18:25 (15)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!