Apple Mac OS X up to 10.11.1 libc 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.
8.8$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Apple Mac OS X up to 10.11.1. Affected is an unknown function of the component libc. This manipulation causes memory corruption. This vulnerability appears as CVE-2015-7039. The attack may be initiated remotely. In addition, an exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Apple Mac OS X up to 10.11.1 (Operating System) and classified as critical. Affected by this vulnerability is an unknown code of the component libc. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Buffer overflow in libc in Apple iOS before 9.2, OS X before 10.11.2, tvOS before 9.1, and watchOS before 2.1 allows remote attackers to execute arbitrary code via a crafted package, a different vulnerability than CVE-2015-7038.

The weakness was presented 12/08/2015 by Maksymilian Arciemowicz with CXsecurity as HT205637 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is known as CVE-2015-7039 since 09/16/2015. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. The advisory points out:

Multiple buffer overflows existed in the C standard library. These issues were addressed through improved bounds checking.

A public exploit has been developed by Maksymilian Arciemowicz and been published 1 days after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 87321 (Mac OS X Multiple Vulnerabilities (Security Updates 2015-005 / 2015-008)), 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 l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 124389 (Apple Mac OS X v10.11.2 and Security Update 2015-008 Not Installed (APPLE-SA-2015-12-08-3)).

Upgrading to version 10.11.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 Exploit-DB (38917), Tenable (87321) and SecurityFocus (BID 78719†). See VDB-68019, VDB-68020, VDB-78550 and VDB-78551 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

Support

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 8.8

VulDB Base Score: 9.8
VulDB Temp Score: 8.8
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: 🔍
Access: Public
Status: Proof-of-Concept
Author: Maksymilian Arciemowicz
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 87321
Nessus Name: Mac OS X Multiple Vulnerabilities (Security Updates 2015-005 / 2015-008)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

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: 🔍
Exploit Delay Time: 🔍

Upgrade: Mac OS X 10.11.2

Timelineinfo

09/16/2015 🔍
12/08/2015 +83 days 🔍
12/08/2015 +0 days 🔍
12/09/2015 +1 days 🔍
12/09/2015 +0 days 🔍
12/09/2015 +0 days 🔍
12/11/2015 +2 days 🔍
12/11/2015 +0 days 🔍
11/14/2024 +3261 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT205637
Researcher: Maksymilian Arciemowicz
Organization: CXsecurity
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2015-7039 (🔍)
GCVE (CVE): GCVE-0-2015-7039
GCVE (VulDB): GCVE-100-79573
SecurityFocus: 78719
SecurityTracker: 1034344

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

Entryinfo

Created: 12/09/2015 14:05
Updated: 11/14/2024 04:49
Changes: 12/09/2015 14:05 (43), 04/28/2018 23:58 (31), 06/29/2022 15:04 (2), 11/14/2024 04:49 (16)
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 ▸

Do you know our Splunk app?

Download it now for free!