full-disclosure - Re: IPS Evasion with the Apache HTTP Server

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

Message-ID: <4ef5fec60706191244y6893bbf7sa545d9464a0668ef@mail.gmail.com>
Date: Tue, 19 Jun 2007 12:44:00 -0700
From: coderman <coderman@...il.com>
To: "H D Moore" <fdlist@...italoffense.net>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: IPS Evasion with the Apache HTTP Server

On 6/19/07, H D Moore <fdlist@...italoffense.net> wrote:
> ...
> Many commercial IPS products fail to decode HTTP requests which use 0x0c,
> 0x0b, and 0x0d instead of the normal 0x20/0x09 separators.
> ...
> A request which contains multiple CRLF sequences instead of a valid method
> is processed by Apache, yet ignored by most IPS engines

you can use many more than that.  fill spaces with non printable and
apache (and a few others) will eat it fine.  \x01-\x1f, except ESC,
maybe CR/LF depending on placement...

is there a page somewhere that details which web servers handle sloppy
input?  (i bet the embedded httpd's are the most resistant)

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/