Mach ports are used to provide inter-process communication (IPC) facilities on Mac OS X. More information can be found on the vendor's site at the following URL.
Local exploitation of an access validation vulnerability in Apple Inc.'s Mac OS X could allow an attacker to execute arbitrary code with root privileges.
When executing a setuid-root binary, the Mach kernel does not reset the current thread Mach port, or the current thread Mach Exception Port. By first creating and obtaining write access to a Mach port, and then executing a set-uid root binary, an attacker can write arbitrary data into the address space of the process running as root. This leads to arbitrary code execution in the privileged process.
Successful exploitation of this vulnerability results in the execution of arbitrary code with root privileges. All an attacker needs is a setuid-root binary and permission to execute it. In a default install, there are numerous binaries that meet these requirements.
iDefense has confirmed the existence of this vulnerability in Mac OS X version 10.4.10, both Server and Workstation. Previous versions may also be affected.
iDefense is currently unaware of any workaround for this issue.
Apple addressed this vulnerability within their Mac OS X 2007-008 security update. More information is available at the following URL.
The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2007-3749 to this issue. This is a candidate for inclusion in the CVE list (http://cve.mitre.org/), which standardizes names for security problems.
09/07/2007 Initial vendor notification
09/10/2007 Initial vendor response
11/14/2007 Coordinated public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Free tools, research and upcoming events
Copyright © 2007 Verisign, Inc.
Permission is granted for the redistribution of this alert electronically. It may not be edited in any way without the express written consent of iDefense. If you wish to reprint the whole or any part of this alert in any other medium other than electronically, please e-mail customer service for permission.
Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.