News for hackers. Stuff that matters.
Re:Pwn2Own results for Wednesday (Day One) by rwg on Friday March 14, 2014 @02:43PM (#7400910)
At Pwn4Fun, Google delivered a very impressive exploit against Apple Safari launching Calculator as root on Mac OS X.

I'll bet it was ocspd they exploited. The CRL handling code in libsecurity is awful, and ocspd runs as root without a sandbox profile.

Re:Pwn2Own results for Wednesday (Day One) by bfish510 on Friday March 14, 2014 @03:29PM (#7401191)
How can you tell if a process runs as root or is run within a sandbox?
Re:Pwn2Own results for Wednesday (Day One) by rwg on Friday March 14, 2014 @04:21PM (#7401555)
"ps" will show the effective uid ocspd is running as:

    % ps aux|grep ocspd
    root              534   0.0  0.0  2442712   2036   ??  Ss    3:53PM   0:00.04 /usr/sbin/ocspd
I don't know how to show the sandbox a running process is contained in, but it's easy enough to show that launchd runs ocspd directly, without sandbox-exec:

    % grep -A3 ProgramArguments /System/Library/LaunchDaemons/com.apple.ocspd.plist
            <key>ProgramArguments</key>
            <array>
                    <string>/usr/sbin/ocspd</string>
            </array>
It's possible for a process to programmatically place itself in a sandbox (see /usr/include/sandbox.h), but a quick look at the source to ocspd and a quick disassembly of what actually ships with OS X 10.9.2 shows ocspd does not do that.
Re:Pwn2Own results for Wednesday (Day One) by yukichan on Friday March 14, 2014 @04:00PM (#7401426)
On a mac Activity Monitor will show you that, also there are also things like top, ps aux and pgrep. These would work:

pgrep -lf -U root | grep processname

or:

ps aux | grep root | grep processname