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

Summaryinfo

A vulnerability was found in Apple iOS up to 9.2. It has been rated as critical. This affects an unknown part of the component libxml2. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2015-7500. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Apple iOS up to 9.2 (Smartphone Operating System). It has been classified as critical. This affects an unknown function of the component libxml2. 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 summary by CVE is:

The xmlParseMisc function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service (out-of-bounds heap read) via unspecified vectors related to incorrect entities boundaries and start tags.

The weakness was released 03/21/2016 by Kostya Serebryany with Google as HT206166 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2015-7500 since 09/29/2015. 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 07/11/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 87369 (Ubuntu 12.04 LTS / 14.04 LTS / 15.04 / 15.10 : libxml2 vulnerabilities (USN-2834-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Ubuntu Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 351588 (Amazon Linux Security Advisory for libxml2: ALAS2-2019-1220).

Upgrading to version 9.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 (87369), SecurityFocus (BID 79562†) and Vulnerability Center (SBV-57583†). Entries connected to this vulnerability are available at VDB-77250, VDB-79257, VDB-79258 and VDB-79334. 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: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: 87369
Nessus Name: Ubuntu 12.04 LTS / 14.04 LTS / 15.04 / 15.10 : libxml2 vulnerabilities (USN-2834-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 14611
OpenVAS Name: Amazon Linux Local Check: alas-2015-628
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
Patch: git.gnome.org

Timelineinfo

09/29/2015 🔍
12/12/2015 +74 days 🔍
12/14/2015 +2 days 🔍
12/15/2015 +0 days 🔍
03/21/2016 +97 days 🔍
03/21/2016 +0 days 🔍
03/21/2016 +0 days 🔍
03/22/2016 +1 days 🔍
03/23/2016 +1 days 🔍
07/11/2022 +2301 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT206166
Researcher: Kostya Serebryany
Organization: Google
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2015-7500 (🔍)
GCVE (CVE): GCVE-0-2015-7500
GCVE (VulDB): GCVE-100-81501

OVAL: 🔍

SecurityFocus: 79562 - libxml2 CVE-2015-7500 Denial of Service Vulnerability
SecurityTracker: 1034243
Vulnerability Center: 57583 - Apple iOS <9.3 Remote DoS in libxml2 - CVE-2015-7500, Medium

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

Entryinfo

Created: 03/23/2016 12:44
Updated: 07/11/2022 12:19
Changes: 03/23/2016 12:44 (78), 02/02/2019 11:08 (5), 07/11/2022 12:19 (4)
Complete: 🔍
Cache ID: 216:1C5: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!