[Esa-l] Serious Microsoft File Association Bug (fwd)

John D. Hardin jhardin at wolfenet.com
Fri Sep 1 07:01:15 PDT 2000

So much for mangling Office atachment filenames...

 John Hardin KA7OHZ   ICQ#15735746   http://www.wolfenet.com/~jhardin/
 jhardin at wolfenet.com      pgpk -a finger://gonzo.wolfenet.com/jhardin
  768: 0x41EA94F5 - A3 0C 5B C2 EF 0D 2C E5  E9 BF C8 33 A7 A9 CE 76 
 1024: 0xB8732E79 - 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
  "Bother," said Pooh as he struggled with /etc/sendmail.cf, "it never
  does quite what I want. I wish Christopher Robin was here."
				-- Peter da Silva in a.s.r
   58 days until Daylight Savings Time ends

---------- Forwarded message ----------
Date: Tue, 31 Aug 0100 09:03:43 -0500
From: jandrews at SQA-EXTERNAL.DTTUS.COM
Reply-To: joandrews at dttus.com
Subject: Serious Microsoft File Association Bug


While working on a virus issue that we have come across, we have discovered a serious issue with Microsoft's association of file types.  Normally, when you open a file of an unknown type, it will prompt you for an application to use to open the file.  This does not prove true for Microsoft Office documents.  If you rename an Office document to an unknown extension, Windows will still use the Office application to open the file.  It seems that Windows uses the header information contained in a file to determine if it is an Office document before offering a list of applications.

Potential Risk:

Someone with malicious intent could create a macro virus embedded in an Office document, then rename the file with a .VIR extension.  Since most anti-virus software have an exclusion of .VI* this file would never be scanned by Norton.  If a user opens the file, Windows will detect that this .VIR file has MS Office header information and open it in the cooresponding application.  Given the correct circumstances, this would infect the machine and replicate to other users.

Systems Affected:

These scenarios have been tested on the following systems:
	Windows NT 4 SP5 running Office 97
	Windows 2000 running Office 2000
	Windows 2000 SP1 running Office 2000
	Windows 98 SE running Office 97

I have not tested all variations, but you can draw your own conclusions as to the extent of the problem.

Potential Solutions:

In the case of virus defense, make sure that your anti-virus software does NOT include .VI* in its exclusion list.  This is a short-term solution until a fix can be created.

Jonathan Andrews, CISSP
Network Security Group
Deloitte & Touche
joandrews at dttus.com

**Please Note***
The opinions expressed above are my own and have no relation
to those of Deloitte & Touche.  No warranties, expressed or implied,
are given about the solutions provided.

More information about the esd-l mailing list