Apple macOS up to 10.12.1 curl double 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.
8.2$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in Apple macOS up to 10.12.1. This vulnerability affects unknown code of the component curl. Executing a manipulation can lead to double free. This vulnerability is tracked as CVE-2016-8619. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Apple macOS up to 10.12.1 (Operating System). It has been declared as very critical. This vulnerability affects an unknown code block of the component curl. The manipulation with an unknown input leads to a double free vulnerability. The CWE definition for the vulnerability is CWE-415. The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

The function `read_data()` in security.c in curl before version 7.51.0 is vulnerable to memory double free.

The bug was discovered 09/14/2016. The weakness was disclosed 12/13/2016 with Cure53 as HT207423 as confirmed advisory (Website). The advisory is shared for download at support.apple.com. This vulnerability was named CVE-2016-8619 since 10/12/2016. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/07/2022). It is expected to see the exploit prices for this product increasing in the near future. The advisory points out:

Multiple issues existed in curl. These issues were addressed by updating to curl version 7.51.0.

The vulnerability was handled as a non-public zero-day exploit for at least 51 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 94572 (SUSE SLES11 Security Update : curl (SUSE-SU-2016:2714-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 157987 (Oracle Enterprise Linux Security Update for curl (ELSA-2019-4652)).

Upgrading to version 10.12.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 Tenable (94572) and SecurityFocus (BID 94100†). The entries VDB-90449, VDB-91385, VDB-91680 and VDB-91681 are pretty similar. Once again VulDB remains the best source for 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: 8.3
VulDB Meta Temp Score: 8.2

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

NVD Base Score: 9.8
NVD Vector: 🔍

CNA Base Score: 5.3
CNA Vector (Red Hat, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Double free
CWE: CWE-415 / 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: 94572
Nessus Name: SUSE SLES11 Security Update : curl (SUSE-SU-2016:2714-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 801105
OpenVAS Name: Apple Mac OS X Multiple Vulnerabilities-01 February-2017
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: macOS 10.12.2

Timelineinfo

09/14/2016 🔍
10/12/2016 +28 days 🔍
11/02/2016 +21 days 🔍
11/04/2016 +2 days 🔍
12/13/2016 +39 days 🔍
12/13/2016 +0 days 🔍
12/16/2016 +3 days 🔍
08/01/2018 +592 days 🔍
10/07/2022 +1528 days 🔍

Sourcesinfo

Vendor: apple.com

Advisory: HT207423
Organization: Cure53
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-8619 (🔍)
GCVE (CVE): GCVE-0-2016-8619
GCVE (VulDB): GCVE-100-94372

OVAL: 🔍

SecurityFocus: 94100 - cURL CVE-2016-8619 Remote Security Vulnerability
SecurityTracker: 1037192

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

Entryinfo

Created: 12/16/2016 14:12
Updated: 10/07/2022 21:12
Changes: 12/16/2016 14:12 (73), 07/08/2019 14:43 (14), 10/07/2022 21:04 (3), 10/07/2022 21:12 (12)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for 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!