Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Exploits-HackingTools
[Top] [All Lists]

[NEWS] Mac OS X malloc() Local Privilege Escalation

Subject: [NEWS] Mac OS X malloc() Local Privilege Escalation
Date: 29 Sep 2005 11:06:14 +0200
The following security advisory is sent to the securiteam mailing list, and can 
be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion

The SecuriTeam alerts list - Free, Accurate, Independent.

Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html 

- - - - - - - - -



  Mac OS X malloc() Local Privilege Escalation
------------------------------------------------------------------------


SUMMARY

The Mac OS X malloc() function uses environment variables that can be 
modified by a local attacker and used to perform a privilege escalation 
attack.

DETAILS

Vulnerable Systems:
 * Mac OS X prior to Apple security update 2005-008

The malloc() function within the libSystem library on Mac OS X uses 
several environment variables to enable various logging functionality. The 
description of one of these variables, "MallogLogFile" taken from the 
manual page is shown below:

       MallocLogFile <f>             Create/append messages to the given 
file
                                     path <f> instead of writing to the 
standard
                                     error.

An error exists in the fact that malloc() will still pay attention to this 
variable when an application is suid root.

The following code taken from libSystem (libc) illustrates this:
flag = getenv("MallocLogFile");
      if (flag) {
             fd = open(flag, O_WRONLY|O_APPEND|O_CREAT, 0644);
             if (fd >= 0) {
                   malloc_debug_file = fd;
                   fcntl(fd, F_SETFD, 0); // clear close-on-exec flag XXX 
why?
             } else {
                   malloc_printf("Could not open %s, using stderr\n", 
flag);
             }
      }

A malicious user can set this variable before running a suid application 
in order to modify any file on the system. This can be used in order to 
trivially escalate privileges on the system.

Vendor Status:
The vendor has issued a fix to the issue in Security Update 2005-008.

CVE Information:
 <http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-2748> 
CAN-2005-2748


ADDITIONAL INFORMATION

The information has been provided by  <mailto:advisories@suresec.org> 
Suresec Advisories.
The original article can be found at:  
<http://www.suresec.org/advisories/adv7.pdf> 
http://www.suresec.org/advisories/adv7.pdf



======================================== 


This bulletin is sent to members of the SecuriTeam mailing list. 
To unsubscribe from the list, send mail with an empty subject line and body to: 
list-unsubscribe@securiteam.com 
In order to subscribe to the mailing list, simply forward this email to: 
list-subscribe@securiteam.com 


==================== 
==================== 

DISCLAIMER: 
The information in this bulletin is provided "AS IS" without warranty of any 
kind. 
In no event shall we be liable for any damages whatsoever including direct, 
indirect, incidental, consequential, loss of business profits or special 
damages. 




<Prev in Thread] Current Thread [Next in Thread>
  • [NEWS] Mac OS X malloc() Local Privilege Escalation, SecuriTeam <=