Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Third Microsoft Word Code Execution Exploit Posted

Posted by CowboyNeal on Thu Dec 14, 2006 07:26 PM
from the doors-wide-open dept.
gregleimbeck writes "Exploit code for a third, unpatched vulnerability in Microsoft Word has been posted on the Internet, adding to the software maker's struggles to keep up with gaping holes in its popular word processing program. The attack code, available at Milw0rm.com, contains sample Word documents that have been rigged to launch code execution exploits when the file is opened."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Anonymous Coward on Thursday December 14 2006, @07:35PM (#17247392)
    I always suspected that Microsoft Word was Turing-complete.
  • by Rupan (723469) on Thursday December 14 2006, @07:36PM (#17247420) Homepage
    I tried to open the PoC with OpenOffice 2.0.4 and it crashed. Can someone confirm?

    ooffice2 12122006-djtest.doc /usr/lib/openoffice/program/soffice: line 236: 12793 Segmentation fault "$sd_prog/$sd_binary" "$@"

    This may not be a code execution bug; I'll try to trace it with gdb to see what happens.
    • Re: (Score:3, Interesting)

      It crashed OO 2.1 here
    • by Rupan (723469) on Thursday December 14 2006, @07:47PM (#17247580) Homepage
      The gdb backtrace shows that the crash occurs in SwIoSystem::IsFileFilter (). EIP may not have been overwritten; the value points into what appears to be a valid function (i.e. not the stack or heap):

      eip 0xb7286b4d 0xb7286b4d osl_getVolumeInformation+4487

      Of course, this is probably because the exploit was designed to crash MS Word in the first place, not execute arbitrary code.
      • Doesn't really match up with this stack trace though does it?

        Fatal exception: Signal 6
        Stack: /usr/lib/openoffice/program/libuno_sal.so.3[0xb754 651f] /usr/lib/openoffice/program/libuno_sal.so.3[0xb754 683f] /usr/lib/openoffice/program/libuno_sal.so.3[0xb754 68dd]
        [0xffffe420] /lib/tls/i686/cmov/libc.so.6(abort+0xe9)[0xb6f7a2b 9] /usr/lib/openoffice/program/libvcl680li.so[0xb7f5d a0b] /usr/lib/openoffice/program/libvcl680li.so(_ZN11Ap plication5AbortERK6String+0x17)[0xb7dbbf53] /usr/lib/openoffice/program/sof
    • by Rupan (723469) on Thursday December 14 2006, @08:00PM (#17247726) Homepage
      This is actually quite scary considering the size of Office documents. Store the executable code embedded in the metadata where user-supplied text would normally exist, using a nop slide of several kilobytes at the start. You have at least 26 kilobytes after all... imagine what could be done with 10k of executable code.
    • Whoopee OpenOffice is getting more and more compatible with MS Office by the day... ;)

      But as long as people write most of their complex stuff in C or C++ this will keep happening.

      People should switch to programming languages and frameworks that just won't run "arbitrary code of an attacker's choice" when something exceptional occurs.

      After all these decades aren't there any easy to learn, safe and fast programming languages?
      • Re: (Score:3, Insightful)

        You can't fault the programming language. The problem is in the application if it doesn't check buffer size against how much data is being read; it's in the OS if the problem is occurring when the application does a system call of some sort and is compromised in the process.

        However... it looks like there are Oo.org users digging into that side of the problem. Probably they'll have an accurate synopsis of the failure mechanism and a patch on the way in a few days. Unfortunately we can't say the same (with th
          • C++ (Score:4, Insightful)

            by Z34107 (925136) on Friday December 15 2006, @12:33AM (#17250542)

            Uh if that happens then the language used is obviously unsafe.

            The language isn't "unsafe" - it just lets you do some very, very nifty stuff that noobtard programmers are better off leaving alone.

            C++ has perfectly "safe" features - the Standard Template Library has container classes like strings and vectors that won't overflow no matter how careless you are.

            For those who insist on going down to the byte level and concatenating their strings themselves, Microsoft included "safe" versions of these functions in Visual Studio 2005, and will compile with warnings if you use the dangerous, buffer-overrun-producing variants.

            Why should potentially arbitrary code be executed because a program tries to put data somewhere it won't fit?

            Because a hacker's input and a programmer's overconfidence in his manual input validation (or lack thereof) put the hacker's code over the program itself. It fit just fine where the still-running program used to be.

            This can happen in any language - C++ programmers are simply notoriously bad at input validation.

  • Someof these bugs can penetrate macs, but is there an actual exploit the pentration on macs? For just one or all three?

    Are these fully macro virsues or are these actual binary executables being injected?

    If we have binary executables being injected by some sort of buffer overrun, then I wonder what happen on intel macs. Does the exploit inject i86 code or ppc code. Does Rosetta run the PPC injection or does the i86 injection run on it's own.

    • Microsoft Word malformed pointer vulnerability

      Overview

      A vulnerability in Microsoft Word could allow an attacker to compromise a vulnerable system.

      I. Description

      Data used by Microsoft Word to construct a destination address for a memory copy routine is embedded within a Word document itself. If an attacker constructs a Word document with a specially crafted value used to build this destination address, then that attacker may be able to overwrite arbitrary memory. An attacker could trigger this vulner

  • there is add for TechNet Security Center on that page
    http://www.microsoft.com/technet/security/default. mspx [microsoft.com]
  • by kbob88 (951258) on Thursday December 14 2006, @08:00PM (#17247722)
    Microsoft suggests that users "do not open or save Word files,"
    I really like this quote! That kind of limits the functionality of a word processor if you can't open or save files, right?

    What exactly does Microsoft suggest that I do with Word files? Besides using them to fragment my hard-disk? Maybe I can burn them to keep warm in the winter... um, no.

    Or perhaps I'll just use Word to create and save HTML files!!
  • by ZahnRosen (1040004) on Thursday December 14 2006, @08:24PM (#17247956) Homepage
    This goes under the category of basic internet security. Don't open files from people you don't know. And if you do get a wierd file from someone you don't know stop and think for 10 seconds about it before you open it. Or, buy a mac.
    • Network World reports that the exploit is being used in targeted attacks, for which the source and subject line could be made to appear plausible. If the spoofed From line is one of your coworkers's addresses, and the subject is something of current interest in the company, it would be easy to get fooled.

      How will buying a Mac help unless the team that coding Office for the Mac was much more security-conscious than the team that coded Office for Windows? The one thing that Mac has going for it is a good impl
  • Biggest problem with this sort of exploit, is it gets under the radar of people who actually know not to open executables etc that are sent to them - but a document? Unless they are aware of this emploit being "out there" people will recieve an email with "teh funny.doc", "invite to my birthday.doc" or "pics of brittany + paris.doc" and double click without thinking. Boom - instant zombie machine.

    So all those family, friends and colleagues who you've (finally) trained not to open funny.exe or funny.scr a
  • by keen (86192) on Thursday December 14 2006, @08:30PM (#17248018)
    http://en.wikipedia.org/wiki/Milw0rm [wikipedia.org]

    milw0rm is a group of "hacktivists" best known for penetrating the computers of the Bhabha Atomic Research Centre (BARC) in Bombay, the primary nuclear research facility of India, on June 3, 1998. The attack generated heated debate on the security of information in a world prevalent with countries developing nuclear weapons, the ethics of "hacker activists" or "hacktivists," and the importance of advanced security measures in a modern world filled with teenagers willing and able to break into insecure international websites.
  • Upside:

    Familar user interface
    Fast
    Cheap
    WYSIWYG

    Downsides:

    Replacing blocks of text with larger-sized blocks of text difficult to impossible.
    Cut-and-paste is messy, literally.
    No automated search.

    My Word Processor [sbac.edu]
  • Goddamn it (Score:4, Interesting)

    by spellraiser (764337) on Thursday December 14 2006, @08:34PM (#17248066) Journal

    From TFA:

    "Data used by Microsoft Word to construct a destination address for a memory copy routine is embedded within a Word document itself. If an attacker constructs a Word document with a specially crafted value used to build this destination address, then that attacker may be able to overwrite arbitrary memory," the US-CERT warned.

    So yet again it's a case of embedded code within a data file wreaking havoc. And as already been reported in comments here, this vulnerability also exists in OO.org.

    Seeing this kind of thing always blows my mind. I would be greatly interested in hearing the rationale behind the decision to incorporate this feature. What the hell did they need that for?

    • So they can spy on the user. If the holes are there by design,
      it would make sense there are other holes that have yet to
      be discovered.
    • Re:Goddamn it (Score:4, Interesting)

      by cascadingstylesheet (140919) on Friday December 15 2006, @09:30AM (#17254582)
      >So yet again it's a case of embedded code within a data
      >file wreaking havoc.
      >...
      >What the hell did they need that for?

      I don't know about the new XML-ish version, but the old DOC
      "format" was basically a Word memory dump. Not
      quite as surprising when you think of it that way ...
        • Re: (Score:3, Insightful)

          OLE, DDE, etc...

          People's pretty WordArt wouldn't work otherwise

          Wait until you see how Publisher files are constructed - AFAICR each text box is a mini Publisher OLE object and let's not start on the picture boxes

          I feel sick just thinking about it :S
  • Unbelievable (Score:4, Insightful)

    by AftanGustur (7715) on Friday December 15 2006, @04:26AM (#17252162) Homepage

    "Data used by Microsoft Word to construct a destination address for a memory copy routine is embedded within a Word document itself."

    If this is a standard practice at Microsoft, I'm beginning to understand why they are so relunctant to publish their protocols and standards.

    • Who the fuck got this past whatever committee was reviewing design specs, and why haven't they been clubbed to death like a baby seal?

      When the entire OS relies on the last three characters of a filename to handle filetypes, did nobody think this was a bad idea?


      ROFL. Bad design? Sure. However, this concept dates so far back and is so entrenched that I don't see it going away any time in the next decade. So the "design specs" you are referring to are non-existent, or simply say "make it compatible with the wa
          • by dsci (658278) on Thursday December 14 2006, @11:25PM (#17249796) Homepage
            And UNIX people know this, as it took decades to fix their OS.

            Speaking specifically about using file extensions, I think 'decades' is a little strong.

            From Wikipedia's FILE entry [wikipedia.org]:

            The original version of file originated in Unix Research Version 4 in 1973 ... file's position-sensitive tests are normally implemented by matching various locations within the file against a textual database of magic numbers (see the Usage section). This differs from other simpler methods such as file extensions and schemes like MIME.

            Even if you happen to believe that the real improvements to file were not made until System V, that was 1983...so not decadeS, but decade.

            So no, not a troll and not revisionist. You make it sound like Unix was not usable until the 1990's.
      • Some things aren't so harmless. .txt .rtf

        I tested both of those with word docs, and word opened. RTF is fine, since that was default to Word anyway. TXT is defaulted to notepad.
    • by phrasebook (740834) on Thursday December 14 2006, @08:02PM (#17247750)
      I tried switching my dad to Open Office when we couldn't find the MS Office CD - he immediately complained that the small fonts he was using in his spreadsheets (less than 8 points) didn't render nicely in OO compared to Excel, so he went and bought a copy of Office 2003.

      Little things like that count for a lot. OO might be more secure than MS Office, but it's terrible quality software in user-visible ways (i.e. it's ugly, slow and bloated). These things count to people. Little problems can't just be overlooked because it's free. My dad could pick it apart within minutes, and he doesn't normally care about software at all. He didn't care about paying for Office either, in fact he didn't think twice about it.

      That's why. Nothing to do with TCO, Microsoft being evil, security, monopoly or anything else. OpenOffice just isn't very good in the ways that count to regular users.
      • I totally agree with your contribution. But in my case, my dad found OpenOffice to be just ugly! "The icons are too big," he complained. Even after making them "smaller" the whole interface remained "ugly."
        • Then we have the long time it takes to load.
        • Heck even saving a simple document tales a long time.
        • The Gnome or GTK file dialog did not help matters at all. He found that he could not paste an HTTP link into this file dialog to have OpenOffice open the referenced file. In other words a file to be opened
        • Re: (Score:3, Interesting)

          I think one drawback is that many people who use free software in their professional lives use tools that are far superior to MS Word for writing documents, and these people never test OO.org and thus never give positive feedback to OO.org developers. When you know for certain that MS Word is useless for your endeavors, any app attempting to replace it will be considered really useless. I think people are mistaken when they claim OO.org will be the magic bullet that thrusts free software into the mainstre
        • by mcrbids (148650) on Thursday December 14 2006, @08:18PM (#17247904) Journal
          If you knew enough to download it for him you should have known enough to turn on antialiasing for font sizes 8 and lower in the options menu.

          And if you knew end-users enough to comment on them, you should have known enough that end-users won't know how to turn this on.

          See, software shouldn't "get in the way" of what you're trying to do.
          • If you knew enough to download it for him you should have known enough to turn on antialiasing for font sizes 8 and lower in the options menu.
            And if you knew end-users enough to comment on them, you should have known enough that end-users won't know how to turn this on.
            See, software shouldn't "get in the way" of what you're trying to do.

            Oh dear, looks like this Microsoft Word Code Execution Exploit just "got in the way". So the end user is still at risk, is out of pocket by $cost_of_office, and expose

    • by Vengeance_au (318990) on Thursday December 14 2006, @08:15PM (#17247880) Homepage Journal
      We use both Microsoft Office and OpenOffice in our company. OO is for all internal documents, and Microsoft Office is used for external client work - purely for interoperability with corporate / government clients. Open Office can save into Microsoft Office format, but there are invariably subtle differences in the final layout - and that is just plain unacceptable.

      In the past 12 months a few clients have started using OO and we now share OO documents with them - but they are by far the minority. Hopefully the new "Open" format Microsoft is coming out with will break the barrier down, and allow pixel-perfect interoperability, but until then it is very difficult to operate in a corperate world without the "de-facto" Microsoft Office standard.
          • by SnowZero (92219) on Thursday December 14 2006, @10:31PM (#17249124)
            If you want more of your clients to change to OO, just run "strings" on their .doc files and email them the parts that came from other documents. That should be enough to get them to change their minds about it.

            (For the uninitiated, As you edit a document in MS Word, it picks up bits of other documents you have open at the time or even previously opened. This is because it doesn't clear memory before using it, and the fast-save file format is really more a memory dump. This may have been fixed in the latest version of MS Word; I certainly hope so...)
    • by dc29A (636871) on Thursday December 14 2006, @08:51PM (#17248212) Homepage
      But seriously, why would anyone use anything M$ when there are non-stop bugs and security holes. Open Office / Google Writely anyone?

      (Insert random application name here) with vulnerability running as root is the problem. MS Word hole only amplifies it because it's widely used. But the problem is that everyone and their dog is running Windows as administrator.
      • To the contrary, OpenOffice requires significantly more hardware resources to run than usable versions of MS Office. I have run Office 2000 in a usable state on an old '486 laptop with 40M of ram.

        Open Office is unusable on such a machine. It's probably 'coded better' with C++ and what-not, creating bloated structures and resource piggishness. There is probably an old version of StarOffice that would run fine on the '486, but the notion that OpenOffice is magically 'less of a load on the machine' is just
        • Re: (Score:3, Informative)

          It's probably 'coded better' with C++ and what-not, creating bloated structures and resource piggishness.

          It is not. M$Office is much more optimized (by all means) product. StarOffice itself was based on previous work - so the code base was already split even before Sun acquisition. And then add development of Sun and OO.o which do not perfectly fit each other.

          And Sun's following development effort which threw in Java to the backet didn't help either.

          The result is buggy bloated mess. Don't argue w

      • OOo is nice because it is free. It is however the most bloated piece of software that I have seen in terms of resource consumption including MS products. True non-bloatedness comes with emacs+LaTeX. Now there are things which do not take up any significant resources (until they are done reading my 33K startup .emacs file and increasing buffer and undo limits to ungodly levels that is.).
    • There's simply no money to be made in a simple office suite. Too many people who use basic office features will either use open office, or downright crack MS Office. Even companies.

      The ones that will actualy shell out for Office are high end corporate customers. And beleive it or not, these features are very useful when you get to that point.