full-disclosure - OS X DirectoryService DoS {@...ke adv: a041003-1}

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>] [day] [month] [year] [list]

Message-ID: <200304160006.h3G06nur026534@haackey.com>
From: neeko at haackey.com (Neeko Oni)
Subject: OS X DirectoryService DoS {@...ke adv: a041003-1}

(Ref: www.atstake.com/research/advisories/2003/a041003-1.txt)
(MacOS X DirectoryService Privilege Escalation and DoS attack)

>From the advisory:
>In order for an attacker to exploit this vulnerability, they must
>first cause DirectoryServices to terminate.  This can be done by
>simply connecting to port 625 repeatedly using an automated program. 

Ok, the PATH problem is self-explanatory (and has been exploited once
the DirectoryService process has crashed) but I've had some difficulty
reproducing the DoS attack claim.  I've got a 10.2.4 machine sitting
right next to me, I believe it's a stock install, but DirectoryService
doesn't bind 625.  DirectoryService doesn't bind any ports and
furthermore nothing binds 625 at all.

Has anyone reproduced the DoS in that advisory?

.Neeko Oni [neeko@...ckey.com]