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: <69799.1296118562@localhost>
Date: Thu, 27 Jan 2011 03:56:02 -0500
From: Valdis.Kletnieks@...edu
To: Michal Zalewski <lcamtuf@...edump.cx>
Cc: Yigit Turgut <y.turgut@...il.com>, full-disclosure@...ts.grok.org.uk
Subject: Re: www.google.com xss vulnerability Using mhtml

On Wed, 26 Jan 2011 21:43:28 PST, Michal Zalewski said:

> 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").

Geez. It's 2011, and people are *still* doing that same basic error?

/me tries to remember the first "ignore the Content-Type header and handle it
based on guessing based on filename/extension" bug.  CA-2001-36 seems to
qualify, but I think there were ones before that.  Anybody able to remember
that far back?

Content of type "application/pgp-signature" skipped

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