What's the problem with Microsoft Word?

In 2006 and 2007, major security flaws were discovered in Microsoft Word.
2008 HowStuffWorks

In the last two months of 2006 alone, at least four major security flaws involving Microsoft Word were revealed. All are "zero day" flaws, meaning Microsoft and security organizations became aware of them at the same time that destructive hackers became aware of them. In many "zero day" cases, it's the exploitation of the flaw that brings it to the attention of the software companies; in other cases, the software companies announce the flaw and hackers immediately take advantage of it before a patch can be released. The strange thing about these Word problems is that almost eight weeks after the flaws were exploited by attackers, Microsoft still hadn't released a patch to fix it.

The first in this string of security holes popped up in early December 2006. This flaw affects computers running Word 2000, 2002 and 2003; Word 2004 for Mac and Word 2004 version X for Mac; Word Viewer 2003; and Microsoft Works 2004, 2005 and 2006. An attacker hides a piece of code in a Word document and puts it on a Web site for download or sends it out as an e-mail attachment. When a user downloads or opens the document, the attacker can remotely control the user's computer and execute a wide array of codes under the user's own login. This flaw came to Microsoft's attention on December 5, 2006, when people started reporting attacks.


A second, previously unknown flaw started to draw attention just a week later, this one also allowing a remote attacker to take control of a user's PC. According to Microsoft, though, this flaw exploits a entirely different security hole -- one that opens when Word undergoes a specific error. Apparently, this attack doesn't require a user to download a malicious file; it only requires the Word program on the person's computer to experience this error, at which point an attacker can enter the system and run malicious code. It affects Word 2000, 2002 and 2003 and Word Viewer 2003.

2008 HowStuffWorks Software flaws can cause a lot problems through malicious hacking.

Security experts have attributed these two security holes to memory-corruption flaws

in the Word programs. Days later, a third flaw was revealed. This one also allows for remote access and control of a user's machine and has been tied to a buffer-overflow problem in Word. It came to public attention when a software expert called "Disco Johnny" published a proof-of-concept code on the Web that showed how a malicious hacker could exploit it, essentially providing instructions for running an attack in addition to showing Microsoft it has yet another problem.

And about five weeks later, on January 25, a fourth security hole became the subject of a malicious attack that begins when a user opens a rigged Word file sent as an e-mail attachment and has similar results to the previous attacks: Remote access and control of an entire system if it's running Word 2000. If the computer is running Word 2003 or Word XP, it only crashes the computer, as opposed to opening it up to remote control.

These four issues were only the latest in a series of attacks exploiting previously undiscovered flaws in a wide array of Microsoft Office applications. In September 2006, hackers started exploiting another zero-day Word flaw, this one only affecting Word 2000. A user had to open an infected Word 2000 document using the Word 2000 program in order for the virus, MDropper.Q, to drop a piece of code in the user's PC. This allowed a remote attacker to take control of the infected PC.

Microsoft recommends installing multiple layers of security software and updating the versions vigilantly. Beyond that, we can only use the wariness we've become accustomed to when opening attachments or downloading files, with an extension into a traditionally safer area: Now, if it ends with .doc, don't touch it unless you know and trust the source.

For more information on Microsoft security holes and related topics, check out the following page.


Lots More Information

Related HowStuffWorks Articles

More Great Links

  • Evers, Joris. "Another Word zero-day bug used in attacks." CNET News.com. Jan. 25, 2007. http://news.zdnet.com/2100-1009_22-6153562.html?tag=nl.e589
  • Evers, Joris. "No fix yet for Word 2000 flaw." CNET News.com. Sept. 12, 2006. http://news.zdnet.com/2100-1009_22-6114932.html?tag=nl
  • Evers, Joris. "Word hole exploited in zero-day attacks." CNET News.com. Dec. 5, 2006. http://news.zdnet.com/2100-1009_22-6141221.html?tag=nl
  • Kawamoto, Dawn. "Attack code published for third Word flaw." CNET News.com. Dec. 14, 2006. http://news.zdnet.com/2100-1009_22-6143853.html?tag=nl
  • Kawamoto, Dawn. "Second zero-day flaw found in Word." CNET News.com. Dec. 11, 2006. http://news.zdnet.com/2100-1009_22-6142531.html?tag=nl
  • Kawamoto, Dawn. "Word flaw hit with zero-day attack." CNET News.com. Sept. 5, 2006. http://news.zdnet.com/2100-1009_22-6112265.html?tag=nl