full-disclosure - Re: Apache Illegal Request Handling Possible XSS Vulnerability

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

Date: Tue, 24 Apr 2007 12:40:44 +0100
From: Richard Moore <rich@...tpoint.ltd.uk>
To: KJKHyperion <hackbunny@...tpj.org>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Apache Illegal Request Handling Possible XSS
 Vulnerability

KJKHyperion wrote:
> Michal Majchrowicz wrote:
>> In this case I agree this is a solution. If Apache wouldn't accept any 'separators' then XSS (and other stuff) wouldn't be possible at all. Is there anywhere described which chars can be used in protocol "field"?
> There is no "flaw".

I agree, the only genuine hole here is that the script is printing
untrusted input without quoting it.

Lots cut here, but to add another example to your list of ways the
real parser differs from the grammar:

GET / HT

is accepted as a valid request by Apache too :-)

Cheers

Rich.

-- 
Richard Moore, Principal Software Engineer,
Westpoint Ltd,
Albion Wharf, 19 Albion Street, Manchester, M1 5LN, England
Tel: +44 161 237 1028
Fax: +44 161 237 1031

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