CVE-2016-1825 : Detail

CVE-2016-1825

7.8
/
High
Overflow
0.27%V3
Local
2016-05-20
08h00 +00:00
2016-11-29
15h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

IOHIDFamily in Apple OS X before 10.11.5 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via a crafted app.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

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

 [email protected]
V2 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C [email protected]

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 : 44237

Publication date : 2017-01-15 23h00 +00:00
Author : Brandon Azad
EDB Verified : No

## physmem <!-- Brandon Azad --> physmem is a physical memory inspection tool and local privilege escalation targeting macOS up through 10.12.1. It exploits either [CVE-2016-1825] or [CVE-2016-7617] depending on the deployment target. These two vulnerabilities are nearly identical, and exploitation can be done exactly the same. They were patched in OS X El Capitan [10.11.5] and macOS Sierra [10.12.2], respectively. [CVE-2016-1825]: https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1825 [CVE-2016-7617]: https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2016-7617 [10.11.5]: https://support.apple.com/en-us/HT206567 [10.12.2]: https://support.apple.com/en-us/HT207423 Because these are logic bugs, exploitation is incredibly reliable. I have not yet experienced a panic in the tens of thousands of times I've run a program (correctly) exploiting these vulnerabilities. ### CVE-2016-1825 CVE-2016-1825 is an issue in IOHIDevice which allows setting arbitrary IOKit registry properties. In particular, the privileged property IOUserClientClass can be controlled by an unprivileged process. I have not tested platforms before Yosemite, but the vulnerability appears in the source code as early as Mac OS X Leopard. ### CVE-2016-7617 CVE-2016-7617 is an almost identical issue in AppleBroadcomBluetoothHostController. This vulnerability appears to have been introduced in OS X El Capitan. It was reported by Ian Beer of Google's Project Zero (issue [974]) and Radu Motspan. [974]: https://bugs.chromium.org/p/project-zero/issues/detail?id=974 ### Building Build physmem by specifying your deployment target on the command line: $ make MACOSX_DEPLOYMENT_TARGET=10.10.5 ### Running You can read a word of physical memory using the read command: $ ./physmem read 0x1000 a69a04f2f59625b3 You can write to physical memory using the write command: $ ./physmem write 0x1000 0x1122334455667788 $ ./physmem read 0x1000 1122334455667788 You can exec a root shell using the root command: $ ./physmem root sh-3.2# whoami root ### License The physmem code is released into the public domain. As a courtesy I ask that if you reference or use any of this code you attribute it to me. Download: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/44237.zip

Products Mentioned

Configuraton 0

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

References

https://support.apple.com/HT206567
Tags : x_refsource_CONFIRM
http://www.securityfocus.com/bid/90696
Tags : vdb-entry, x_refsource_BID
http://www.securitytracker.com/id/1035895
Tags : vdb-entry, x_refsource_SECTRACK