mailing list archives
Re: www.google.com xss vulnerability Using mhtml
From: Valdis.Kletnieks () vt edu
Date: Thu, 27 Jan 2011 03:56:02 -0500
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?
Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia - http://secunia.com/
Re: www.google.com xss vulnerability Using mhtml Juha-Matti Laurio (Jan 30)