Slashdot Mirror


Zero-day Exploit in PDF With Adobe Reader

hankwang writes "Security researcher Petko Petkov, who is known for his recent discovery of a vulnerability with Quicktime in Firefox, claims to have discovered an exploit that allows arbitrary code execution when a maliciously crafted PDF document is opened in any version of Adobe Reader. Petkov did not disclose any technical details other than a video, but claims on his blog that Adobe has acknowledged the vulnerability. If this exploit goes wild, it could cause some serious problems, as PDFs are usually automatically opened from web browsers and widely used and trusted by corporate users."

7 of 188 comments (clear)

  1. xpdf etc by eneville · · Score: 5, Funny

    my xpdf brings all the boys to the yard and they're like, its better than yours

    1. Re:xpdf etc by kebes · · Score: 5, Insightful

      Lacking features can be a good thing.

      I think the sensible strategy, in terms of performance and security, is to use a lightweight minimalist PDF reader for 99% of your PDF needs, and then to only open up Adobe Acrobat when you absolutely need its extra features. Acrobat is a rather large program (some might say "bloated") and it supports a wide variety of features, plugins, etc. It's a fact of life that supporting all those additional features (which are rarely used in a document) increases the program's resource requirements, and make security vulnerabilities "more likely" (for every feature you add, there's another chance for a bug, and another attack vector).

      So, again, I think the sensible strategy is to use a fast, minimalist PDF reader (which, hopefully, is simple enough that it fairly secure: that is, no plugins that can run arbitrary code). Then, when you encounter those PDFs that need those extra features, you load them using a Acrobat, assuming you trust them. In my experience, PDFs that use anything beyond the basic features are rare enough that this isn't much of a burden. It's a fallacy to think that every program that supports a given filetype needs to "do it all"--different programs have different uses.

    2. Re:xpdf etc by eggnoglatte · · Score: 5, Informative

      what corporation actually makes use of forms? Only every single one I've ever worked for. Some government offices here in Canada also provide PDF forms for situations where you have to submit a printed version of the form in the end. You could achieve something similar with web forms, except the printed version would look different depending on browser. Sometimes a consistent formatting is a real advantage. So it is either PDF forms or Word, and given a choice between the two, I definitely vote for PDF.
  2. Re:The vulnerability is in Reader not the PDF form by Nimey · · Score: 5, Informative

    Foxit Reader is the canonical 3rd-party viewer for Windows: http://www.foxitsoftware.com/pdf/rd_intro.php

    Macs have Preview, Linux has Evince and others.

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
  3. Re:Foxit reader is a good substitute. by Arkaic · · Score: 5, Insightful

    That may not be much better. According to a follow up comment by the discoverer of the exploit.

    "Foxit is vulnerable as well, although the user is required to interact with the document in order to launch the exploit."

  4. Re:smug by astrosmash · · Score: 5, Funny

    A lot of things don't work with Ubuntu's pdf viewer.

    --
    ENDUT! HOCH HECH!
  5. This was never a 0Day... by JRHelgeson · · Score: 5, Informative

    This was an announcement of a vulnerability that was discovered in Adobe Acrobat. There is nothing 0day about it, and it will not ever and can not ever be a 0day. Period.

    The defining characteristic of 0day is the day an EXPLOIT is RELEASED, where such exploit also serves as the ONLY vendor notification of a bug being discovered. Every adult on this list understands the definition, but the kids can't seem to grasp the not-so-subtle nuance between a 0day and the discovery of a bug in someone else's code.

    This supposedly serious disclosure referred to in the article is a non-event, there was a "press release" about a supposedly serious flaw in PDF, there were no details, so therefore it doesn't even count as disclosure of a vulnerability as a whole.

    --
    Good security is based upon reality and common sense. Common sense is a function of having common knowledge.