Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

[ Create a new account ]

Adobe Confirms Unpatched PDF Backdoor

Posted by CmdrTaco on Mon Oct 08, 2007 09:29 AM
from the machines-wide-open dept.
50Mat writes "Adobe has fessed up to a dangerous code execution vulnerability affecting software programs installed on millions of Windows machines. The flaw, publicly disclosed more than three weeks ago, could allow hackers to use rigged PDF files to take control of Window XP computers with Internet Explorer 7 installed. It affects Adobe Reader, Adobe Acrobat Standard, Professional and Elements and Adobe Acrobat 3D."
security adobe foxit pdf !backdoor
it security
story

Related Stories

[+] Critical Vulnerability In Adobe Reader 10 comments
An anonymous reader writes "Core Security Technologies issued an advisory disclosing a vulnerability that could affect millions using Adobe's Reader PDF file viewing software. Engineers from CoreLabs determined that Adobe Reader could be exploited to gain access to vulnerable systems via the use of a specially crafted PDF file with malicious JavaScript content. Successful exploitation of the vulnerability requires that users open a maliciously crafted PDF file, thereby allowing attackers to gain access to vulnerable systems and assume the privileges of a user running Acrobat Reader."
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 | Login
Loading... please wait.
  • Is it really an Adobe vulnerability? Seems more like it's an IE vulnerability that has been blame-shifted to whoever writes the plugins that might expose it for what it is.

    • by JoelKatz (46478) on Monday October 08 2007, @09:58AM (#20898941)
      From what I understand, and there isn't much in the way of technical details available, this is not an IE flaw. IE, correctly, doesn't assume that a URI is invalid just because it looks odd. This is correct, because there is no way IE can know if an URI for another protocol is valid or invalid. It is the responsibility of the target program to sanitize its input, knowing full well that it comes from an untrusted source.
  • In a pre-patch advisory, Adobe offered a complicated (and unsupported) workaround for its customers
    So they want me to do what with my what? Isn't that like your mechanic telling you to do something but "if they ask, [they] didn't tell you"
  • Is that the same backdoor vulnerability as this one [michaeldaw.org]?

    To be honest, though, the subject sounds a lot like joke fodder [wikipedia.org]....
  • What About Foxit? (Score:5, Interesting)

    by Lagged2Death (31596) on Monday October 08 2007, @09:43AM (#20898771)
    I found Adobe Reader so slow, bloated, and annoying that I switched to Foxit Reader [foxitsoftware.com], which is much smaller and faster. Can anyone say if the vulnerability applies to Foxit as well?
  • by dioscaido (541037) on Monday October 08 2007, @09:44AM (#20898795)
    If it's also vulnerable on IE7 + Vista, luckily IE7 runs with such limited privileges that the code execution won't be able to do anything other than writing to the internet temp folder. That is, if you haven't turned off UAC.
    • If it's also vulnerable on IE7 + Vista, luckily IE7 runs with such limited privileges that the code execution won't be able to do anything other than writing to the internet temp folder. That is, if you haven't turned off UAC.
      get your free ringtones/[other garbage appealing to the less technically inclined] here!!!! and if you see a UAC window, just click ok to download!
  • Not a backdoor (Score:5, Informative)

    by Anonymous Coward on Monday October 08 2007, @09:44AM (#20898799)
    From the information available, this is just yet another security vulnerability.

    A backdoor is an intentional feature that one puts so that they can take over you computer.
  • URI and MIME type handling in both Windows and OSX is profoundly broken. It's second only to ActiveX in the opportunity for exploits... the basic problem is that when apps register handlers for local use (eg, 'help:' or '.chm') they are available to untrusted content by default. The fix is to have separate registries or separate flags that allow applications to explicitly register as handlers for internal use, or for use on untrusted documents.
    • by jonwil (467024) on Monday October 08 2007, @10:23AM (#20899265)
      Something else that IE (as of last time I looked anyway) and possibly other browsers get wrong is that they try to "guess" the content of the file instead of trusting that what the web server says the file is, the file actually is. If the web server says it is text/plain, it should be rendered as plain text even if it may happen to look like HTML. If the web server says it is image/gif, it should be fed to the gif image decoder.
      RFC 2161 (HTTP 1.1) section 7.2.1 clearly says that it is ok for a client to use the filename or content of a file to identify what file type it is (and therefore what to do with it) if and ONLY IF the server does not provide a Content-Type header.
      There have actually been security flaws in the past (and may still be even now) caused because different parts of IE have a different idea of what type the file is (in particular whether the file is executable or not)

      Then again, considering how many other standards Intercrap Exploder doesn't correctly follow (RFCs and otherwise), its hardly surprising that IE doesn't get this right.

      I do wonder if Gecko gets it right (and treats the Content-Type header as gospel) or if violates the RFC too.
        • Re: (Score:3, Interesting)

          Grr, that link should be opera:config#Trust%20Server%20Types -- Slashdot ate my #
  • Sklyarov? (Score:5, Funny)

    by Speare (84249) on Monday October 08 2007, @09:57AM (#20898921) Homepage

    The flaw, publicly disclosed more than three weeks ago, could allow hackers to use rigged PDF files to take control of Window XP computers with Internet Explorer 7 installed.

    Did Adobe ask the feds to lock up the person who publicly disclose this flaw? Or do they just save that treatment for the publication of flaws in eBook products that blind people can't use in Russia?

  • Control me (Score:4, Funny)

    by suv4x4 (956391) on Monday October 08 2007, @12:36PM (#20901049)
    The irony of this page [bayimg.com] (click for 100% scale) is astounding.

    I had to snap a shot before Adobe pulls their ad.
    • The browser should be secure by itself but when a plug-in is installed by the user (like Adobe Acrobat Reader) that plug-in can execute code and do pretty much what it what... so I would not blame IE7 for that. But I'm still happy to never have upgrade to IE7... yet.
          • Re:solution (Score:5, Informative)

            by Victor Antolini (725710) on Monday October 08 2007, @10:07AM (#20899049)
            Oh, I missed to point out what you missed. From http://www.foxitsoftware.com/pdf/rd_intro.php [foxitsoftware.com]

            Foxit Reader itself is free. As to add-ons, the critical add-ons are free while advanced add-ons are non-free. For example, you can use the following functions for free:

            * View or print PDF document
            * Basic PDF form operations i.e. filling out PDF forms and printing them out
            * Advanced PDF form operations, such as saving filled-out forms and import/export forms, free for personal usage only
            * View PDF as text
            * Critical add-ons, such as UI language package, JPEG2000/JBIG decoder, CJK package, GDI+ for early Windows version, etc

            The followings are several examples of non-free, advanced add-ons:

            * Foxit Reader Pro Pack is not free. It includes the following functions:
            o Annotation
            o Text viewer and text converter
            o Form filler
            o Spell checker
            o Advanced editing tools, including loupe tool, measure tools, image tool, file attachment tool, link tools, annotation selection tool, and more

            Actually without Pro Pack, you are still able to annotate a PDF document and print it out. However when you save the annotated document, it will be stamped with an evaluation mark on the top-right corner of the annotated pages. If you purchase a Pro Pack add-on, then there will be no evaluation mark.
    • Welcome... (Score:5, Funny)

      by sakdoctor (1087155) on Monday October 08 2007, @10:07AM (#20899061) Homepage
      ...to hyphen hell! The rules - of style that apply to dashes - and hyphens - have evolved to support ease of reading in complex constructions; editors - often accept deviations - from them that will support, rather than --- hinder, ease of reading.
    • Re: (Score:3, Informative)

      That also isnt 100% compliant.

      While i use it all the time since it is smaller and ligher ( acrobat reader is free too btw, so that isnt a good selling point ), i have noticed that somethings do NOT render properly.

      Have they fixed the weblink bug yet?