News for hackers. Stuff that matters.
Re:Microsoft: 0Day Exploit Targeting Word, Outlook by Sniffnoy on Monday March 24, 2014 @09:27PM (#7463120)
I'm confused by the idea that there could be a vulnerability while reading RTFs, of all things. Annoying; I frequently send out documents in RTF format to make sure everyone can read them...
Re:Microsoft: 0Day Exploit Targeting Word, Outlook by bananas on Tuesday March 25, 2014 @05:23AM (#7464737)
Any data format that is read by an unsafe language (i.e. C/C++ here most likely) is prone to remote execution. They are pretty much like wandering around with a machine gun with the safety off. This is perfectly fine if you're trained for years to do this (Queens guard for example) but some drunk redneck (which is most of us, me included) will inevitably kill people.

Typical example of a buffer overflow that leads to execution specific to this case, although I'm sure this has been posted a million times here:

1. RTF parser allocates char[15] on the stack for storing the font family from {\fonttbl\...

2. Joe hacker shifts out a font definition of 15 chars plus a return address to some arbitrary code and the code itself.

3. The parser reads until the end of the fonttbl definition ;} which is longer than the buffer specified.

4. This blindly overwrites the return address by writing beyond the end of the buffer and pokes some arbitrary code on the end. If you're lucky this won't cause a bus error / MMU trap

5. The function returns and the malicious return address is jumped to executing Joe Hackers code.

Ultimately anyone can make this mistake when programming in C/C++ and they frequently do. It takes considerable skill to not blow your toes off like this.

There are certain mitigation method which prevent this but they aren't universally enabled or available or 100% effective.

I've pretty much given up on C these days but I spent a lot of time making sure stuff like this was impossible and most importantly avoided parsing anything myself when nice tools like lex/yaxx are around that have all this stuff safely wrapped up. I didn't win every time.

Re:Microsoft: 0Day Exploit Targeting Word, Outlook by aric on Tuesday March 25, 2014 @12:25AM (#7463786)
There have been countless (known) RTF vulnerabilities for over a decade.
Re:Microsoft: 0Day Exploit Targeting Word, Outlook by ne0codex on Monday March 24, 2014 @09:58PM (#7463266)
I stick with .pdf files

However, that might be bad practice.

Re:Microsoft: 0Day Exploit Targeting Word, Outlook by mpyne on Monday March 24, 2014 @10:37PM (#7463446)
With Adobe Reader it's probably even worse, to be honest.
Re:Microsoft: 0Day Exploit Targeting Word, Outlook by rplnt on Tuesday March 25, 2014 @03:45AM (#7464445)
For the past few years I've been using Chrome as a PDF reader (I don't use it as my primary browser, but have it nonetheless). I'm not saying Chrome can't be vulnerable... it's just good to get rid of such pointless software as PDF reader. Especially if the case is the bloated Acrobat Reader (though I think the UX was great with that one).