Vulnerability Development mailing list archives

Re: Possible syslogd DoS ?


From: Petr Baudis <pasky () pasky ji cz>
Date: Thu, 4 Oct 2001 13:48:52 +0200

well that wouldnt work to well as syslog likes to do "message repeating X
number of times" , so trying to fill it up would prove boring and pointless.
as i said those messages would be each different in order to prevent this.

..snip..

something as simple as that works, but for some reason when i run it on my
box it seems to exit after awhile even tho i capture all signal's maybe
syslog() has a exit() in the function , i cant be bothered looking into it,
i did this code on the fly for proof of concept
didn't study the code, but at a glance it seems somewhat broken to me
(buffer[strlen(buffer)-1]='\0'; looks very strange to me :)

-- 

                                Petr "Pasky" Baudis
.                                                                       .
        n = ((n >>  1) & 0x55555555) | ((n <<  1) & 0xaaaaaaaa);
        n = ((n >>  2) & 0x33333333) | ((n <<  2) & 0xcccccccc);
        n = ((n >>  4) & 0x0f0f0f0f) | ((n <<  4) & 0xf0f0f0f0);
        n = ((n >>  8) & 0x00ff00ff) | ((n <<  8) & 0xff00ff00);
        n = ((n >> 16) & 0x0000ffff) | ((n << 16) & 0xffff0000);
                -- C code which reverses the bits in a word.
.                                                                       .
My public PGP key is on: http://pasky.ji.cz/~pasky/pubkey.txt
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++:++ a--- C+++ UL++++$ P+ L+++ E--- W+ N !o K- w-- !O M-
!V PS+ !PE Y+ PGP+>++ t+ 5 X(+) R++ tv- b+ DI(+) D+ G e-> h! r% y?
------END GEEK CODE BLOCK------


Current thread: