full-disclosure - BadBlue 302 Status Message XSS

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: <00ef01c22f85$c10855e0$e62d1c41@kc.rr.com>
From: mattmurphy at kc.rr.com (Matthew Murphy)
Subject: BadBlue 302 Status Message XSS

BadBlue 1.74 (presumably earlier) is susceptible to a cross-site
scripting attack.  When BadBlue is passed a name of a non-existant
file path (or an existant folder) that does not end in a 0x2f character
("/") it returns a 302 status code containing some text:

HTTP/1.0 302 found
Location: /<SCRIPT>/

<html><body><pre>GET /<SCRIPT> HTTP/1.0

Obviously, if you pass in HTML markup, it continues on into the
reply un-filtered, resulting in a cross-site scripting attack.

This vulnerability cannot be exploited on Internet Explorer, or
any browser which ignores entities in HTTP redirect messages.

Successful exploitation may require a significant amount of
"garbage" HTML, as the entity is downloaded, displayed, and
then the redirect executed.

This vulnerability poses minimal risk, but should be taken very
seriously.

"The reason the mainstream is thought
of as a stream is because it is
so shallow."
                     - Author Unknown