bugtraq - Re: Buffer overflow/privilege escalation in MacOS X

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <C8B8BCD5-2F50-11D8-BB15-000A957DA3A8@atstake.com>
Date: Mon, 15 Dec 2003 17:48:21 -0500
From: Dave G. <daveg@...take.com>
To: Max <rusmir@...a.net>
Cc: bugtraq@...urityfocus.com
Subject: Re: Buffer overflow/privilege escalation in MacOS X

> Date: Mon, 15 Dec 2003 11:54:02 -0800
> From: Max <rusmir@...a.net>
> To: bugtraq@...urityfocus.com
> Subject: Buffer overflow/privilege escalation in MacOS X
>
> Hi,
>
> It appears that parts of MacOSX that didn't come from BSD are
> not very well written and have significant security issues.
>
> An example is a /System/Library/Filesystems/cd9660.fs/cd9660.util
> utility. It is suid root and it is vulnerable to a classic buffer
> overflow due to the lack of input validation.
>

Indeed.  However, due to several mitigating factors, this issue doe not 
appear to be exploitable (at least not with any of the techniques I am 
aware of).  The overflow occurs in main() and there is an unavoidable 
exit() at the end of the function.  So while you can overwrite the 
return stack frame, the process will never use your new value.

Cheers,

Dave G.