Slashdot Mirror


Attackers Infect Ads With Old Adobe Vulnerability

thethibs writes "eWeek is reporting that just as everyone is buzzing about the latest Adobe vulnerability, someone poisoned ads hosted by Ziff-Davis with an older Adobe exploit (affecting versions 8.12 and earlier, and long since patched). Z-D fixed the problem less than 24 hours after its first appearance. The interesting bit of this is that a bunch of people probably got hit with the old Trojan when they browsed to a story about the new one."

4 of 70 comments (clear)

  1. Adobe what? by Anonymous Coward · · Score: 5, Informative

    While it's fairly evident that they're talking about Adobe Reader, nowhere in the summary does it state which Adobe product this affects. Adobe is a company, not a product, even if it's not called Adobe Acrobat anymore!

  2. Documents are not applications by Gothmolly · · Score: 5, Insightful

    If a "document" wants to _do_ anything, then it is not a document, and should be given the same trust as other programs. The Microsoftification of the world must stop.

    --
    I want to delete my account but Slashdot doesn't allow it.
  3. Re:another good reason...... by Phroggy · · Score: 5, Informative

    Blocking scripts isn't guaranteed to protect you from this kind of attack, since the article specifically mentioned that the attack used iframes. Loading a PDF into an iframe can be done with no scripting; this will either trigger a file download or will invoke the Adobe Reader plug-in (or whatever other plug-in your browser is configured to use to display PDF files).

    However, if the iframe is inserted into the DOM by a script (not uncommon with advertisements these days), then yeah, blocking scripts would prevent it.

    Of course, I imagine the attempt to install a rogue application would trigger a UAC prompt on VIsta, protecting anyone on that platform who isn't a moron.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  4. Re:another good reason...... by Akzo · · Score: 5, Insightful

    Unless the malicious code was placed on any one of the authors sites or another trusted site.

    --
    Sig is for Signature, so you don't have to manually sign every post.