full-disclosure - Re: www.google.com xss vulnerability Using mhtml

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: <AANLkTindQP6M-9QFWd5P0fLNSivVU_+8YTE1CP2Oxu7S@mail.gmail.com>
Date: Wed, 26 Jan 2011 21:43:28 -0800
From: Michal Zalewski <lcamtuf@...edump.cx>
To: IEhrepus <5up3rh3i@...il.com>
Cc: full-disclosure@...ts.grok.org.uk, Yigit Turgut <y.turgut@...il.com>
Subject: Re: www.google.com xss vulnerability Using mhtml

> 1.www.google.com app don't filter the CRLF

This is not strictly required; there are other scenarios where this
vulnerability is exploitable.

> 2.IE support mhtml protocol handler to render the mhtml file format,
> and this is the why mhtml: is designed

The real problem is that when mhtml: is used to fetch the container
over an underlying protocol, it does not honor Content-Type and
related headers (or even "nosniff").

/mz

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