[31541] in bugtraq

home help back first fref pref prev next nref lref last post

RE: BAD NEWS: Microsoft Security Bulletin MS03-032

daemon@ATHENA.MIT.EDU (Nathan Wallwork)
Wed Sep 10 17:56:10 2003

Date: Tue, 9 Sep 2003 14:17:33 -0600 (MDT)
From: Nathan Wallwork <owen@pungent.org>
To: Drew Copley <dcopley@eeye.com>
Cc: ADBecker@chmortgage.com, "'GreyMagic Software'" <security@greymagic.com>,
        "'Bugtraq'" <bugtraq@securityfocus.com>,
        <full-disclosure@lists.netsys.com>, <http-equiv@excite.com>,
        "'NTBugtraq'" <NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM>,
        "'Microsoft Security Response Center'" <secure@microsoft.com>,
        <vulnwatch@vulnwatch.org>
In-Reply-To: <000001c37653$e2a197f0$2b02a8c0@dcopley>
Message-ID: <Pine.LNX.4.44.0309091413040.19314-100000@pungent.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 8 Sep 2003, Drew Copley wrote:
> The only sure way to detect this, I already wrote about [to Bugtraq]. That
> is by setting a firewall rule which blocks the dangerous mimetype string
> [Content-Type: application/hta]. Everything else in the exploit can change. 

Just so we are clear, the firewall wouldn't tbe he right place to catch 
this because that string could be split by packet fragmentation, so you'd 
need to look for it at an application level, after the data stream 
has been reassembled.  

Of course, if anyone thinks it is easier to protect their browser with a 
proxy than fix the browser they've got other issues.


home help back first fref pref prev next nref lref last post