SCO Unixware is a Unix operating system that runs on many OEM platforms.
More information about the product is available from:
Local exploitation of an access validation error in SCO Unixware allows
attackers to gain root privileges.
The vulnerability specifically exists due to a failure to check
permissions on traced executables. The ptrace() system call provides an
interface for debugging other processes on the system. SCO Unixware's
implementation of the ptrace system call fails to check for setuid
permissions on binaries before attaching to the process. This results
in the complete control of memory and execution for the traced process
with root privileges. Attackers can inject data into the running setuid
process and execute arbitrary code with root permissions.
Exploitation of this vulnerability is trivial. Simply placing shellcode
in the environment and changing the instruction pointer via ptrace() is
enough to elevate privileges.
iDefense has confirmed the existence of this vulnerability in SCO
Unixware versions 7.1.3 and 7.1.4. All previous versions of SCO Unixware
are suspected to be vulnerable.
It is not possible to reduce the impact of this vulnerability other
than to restrict access to the affected systems.
The vendor has released the following advisory to address this issue:
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CAN-2005-2934 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org), which standardizes names for
09/15/2005 Initial vendor notification
10/13/2005 Initial vendor response
02/24/2006 Public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Free tools, research and upcoming events
Copyright © 2006 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
email customerservice@iDefense.com 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,