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."
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!
to run scripts selectively ....
Which I do, and with no script the way I have... *shrugs* the little extra hassle is worth all the benefits!
So what servers were actually compromised by hackers? According to the article, Stephen Wellman, director of community and content for Ziff Davis Enterprise, says no ZD web sites were compromised and it "was not our fault." Whose fault was it? Does ZD use a third-party advertising service? If so, does anyone else use that same advertising service? If ZD runs its own ad servers, how is this not ZD's fault?
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
Our computers at work will probably get trashed from this. They only use Adobe reader, some old unpatched version, and only IE without any adblocking. Microsoft shop don't you know.
"He's lost in a 'floyd hole"
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.
I see no mention in the summary of a specific product. Since I'm not going to RTFA, should I just assume that, since I don't own Adobe stock, I'm not affected?
yup the UHA is laughing at you all now.
OH sorry but you have banned and filtered out the site, guess you cant look into the past and KNOW whats coming next can you.
GOOD ON THEM ALL AND DESERVEDLY SO
P.S. just to let your readership know there about 10 GOOD exploits a year that come back to life, and by good i mean those with really sweet luscious effects
Don't have anonymous sex with strangers in bath-houses. Or if you must have anonymous sex with strangers in bath-houses use a condom. This has been a public service message.
In other words, don't use AR. Use Evince (on Linux) or Sumatra PDF (Windows). If you must use AR, go to Edit, Preferences, JavaScript, and uncheck "Enable Acrobat JavaScript".
No, none of this has much to do with PDF's merits as a file format. Embedding JS in PDF was a mistake. The mistake won't hurt you if you take these elementary precautions.
Find free books.
Ads through most of Ziff-Davis are run through an Ad serving system called DART- made by Double Click and owned by Google. What is interesting is that DART has an internal checker that scans rich media and .swf files for security vulnerabilities. It is surprising that these were not caught from the start.
their ads....
Haven't they heard of protection? They should yousd tube of some adstroglide. I bet someone's ads will be busted. Talk about exPLOITUS enterRUPTus...
Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
Jeez people, get with the program already.
Sig this!
Yup, this happened to me. Browsed to one of their pages using Firefox. Immediately, without any user interaction, a file called doc.pdf was downloaded from feelyouinside.com. Since I was using Firefox 10 with evince, everything stopped there. --AA
I got hit before the weekend by a very similar one, but not exactly the same.
Browsing with fully patched FF & WinXP. But yeah, I have the little puppy updater from Adobe disabled (because it tries to shit everywhere). Why can't people make an updater that is just an updater and doesn't try to sneak in other shit?
Anyways, I was looking for some guitar cases, and a pop-under showed up (apparently this is another problem that can not be fixed a 100%...), and then a crash message saying "~.exe" had crashed. You try to google ~.exe, and see what you find...
Okay, so I realize this is not good and bring up task manager and see a task named "4.pr". Fuck, this is really not good.
So I unplug, go to another machine and figure some stuff out. There's two files in the c: root directory: p3.bat and 4.pr. Looks like also some rogue version of wdmaud.sys.
Looks like the crash caused the trojan to not install successfully, but still, this is the first time in my > 20 years messing with computers that I got p0wned.
So I'm mad as hell, and sure, I'm stupid. I know FF loads certain plugins automagically (which is something I really don't like) but I didn't really think of it loading AR... Normally I download PDFs first. As a matter of fact, I DON'T WANT to use AR as a plugin.
In any case, I've decided a couple of things:
- I will never install Acrobat Reader again. I will advise anyone that listens to do the same. Either find an alternative, or just forget about viewing the content. It can't be that important.
- For other plugins, especially those that are hard to do without like Flash, I will search for Open Source alternatives.
- VMs. I never liked VMs, but it seems like there's no way around it. I'm thinking three VMs: one for crazy browsing, one for the normal stuff (eBay/slashdot) and one for sensitive stuff (banks/paypal). The big advantage is that you can snapshot them, so that if one gets hit, you aren't immediately dead in the water. Instead you fire up the old snapshot.
- Again review what can be done to have a reasonable browsing experience while having plugins disabled by default.
- All (remotely) sensitive data goes on a truecrypt drive that automatically dismounts. I've been using it for really sensitive data and it works great.
But the other thing I have to say though: PLEASE Firefox developers, have a mode that does NOT load any plugins, but displays their content as an empty square first. Then if you want to see it, I can click on it or something. Maybe noscript is the thing; last time I looked it was too tedious to use. Maybe now I'll feel differently.
btw. Just for shits an grins, you should look at what plugins are installed for Firefox: Tools->Add-ons->Plugins tab. I was surprised to say the least.
Its the decision to allow the macro script do other things outside of a word doc that is the problem.
Who cares if accountants have macros that autosum three pages of figures. I just want to punch the idiot who thought that its ok to have a macro alter/save files other than the active file, or connect to outside data sources (e.g. teh intarwebz) without a big freaking' popup asking for a manual confirmation.
What probably happened is some clever punk thought it would be smart to just tie it to the VBScript engine, and let anything happen, rather than developing a special macro language for office.
HA! I just wasted some of your bandwidth with a frivolous sig!
"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." Is anybody else relieved that the word "interesting" was used instead of "irony?" This seems like the perfect place to misuse the word "irony."
Can someone please tell me how to change the font when I'm typing a document in microsoft?
Time zone converter
I have PDFs set to automatically download to my desktop in FF, since the Adobe plugin has a habit of crashing and it's very slow.
It seems that I was fortunate. I never opened them since I didn't know where they came from, they went straight to the bin.
Why is there scripting in an acrobat document anyway?
"Blocking scripts isn't guaranteed to protect you from this kind of attack - by Phroggy (441) on Tuesday February 24, @11:39PM (#26978685) Homepage
Correction: It is - but, it depends on WHERE (what app, specifically here) you blocking scripting @!
(AND, in this case? It's better to do in Adobe Acrobat Reader, itself, vs. your webbrowsers in this case)
SO... how to do that?
See here, 1st post @ the top of this page:
HOW TO SECURE Windows 2000/XP/Server 2003 & even VISTA, plus, make it "fun-to-do", via CIS Tool Guidance (&, beyond):
http://www.tcmagazine.com/forums/index.php?s=c4108cb7c8260643f003b1737cc429e4&showtopic=2662&st=25&start=25
----
SALIENT QUOTE/EXCERPT/DETAILS etc. et al:
(HOW TO TURN OFF JAVASCRIPT USAGE IN ADOBE ACROBAT READER)
1.) Use Adobe Acrobat's EDIT menu
2.) PREFERENCES submenu
3.) Javascript section (in left-hand side column of options)
4.) & uncheck "Enable Acrobat Javascript" in the right-hand side option for that.
----
THUS - By disabling scripting in Adobe Acrobat Reader, of most ANY (@ least recent) versions of it (&, I KNOW that versions 8 & 9 allow this, @ least)? You stall this type of attack, easily...
( &, no "chancing it" by ONLY using NoScript's DEFAULTS (which are NOT as "stringent" as it CAN be) or other means in a browser alone (though, layering those methods ontop of this one cannot hurt)).
----
IMPORTANT NOTE/EDITING MY ORIGINAL POST I INTENDED TO PUT UP W/ SAID "WORK-AROUND" METHOD I PUT UP ABOVE:
There IS a "home brewed patch" out there now, developed by a 3rd party via a HACKED DLL (filename -> AcroRdv9-Patch.zip -> http://www.snort.org/vrt/tools/AcroRdv9-Patch.zip ), for Adobe Acrobat 9 ONLY, but... he's also NOT guaranteeing it vs. other variants of THIS type of attack (run by Adobe's javascripting engines in Acrobat Reader), NOR, in earlier versions of Adobe Acrobat!
HOWEVER - the method I am extolling?
I, however/conversely, DO guarantee it works!
(AND, should even w/ Adobe Acrobat Reader Browser plugins/addons if any, assuming they too, utilize said .DLL/lib's function calls, & odds are in today's "Document Centric Model" & Object-Oriented designs? It does because MOST coders, myself included?? Don't "reinvent the wheel" generally to save time & effort - we USE these prebuilt lib/dll function calls when possible... & HOPE there are no bugs, like this lib/dll has)
Simply too, via the method noted above, & on THIS & other variants of this nature of attack (that exploit faults in Adobe Acrobat's native internal javascript parsing + processing methods) in this application, even in older models that support disabling of javascripting in Acrobat's .pdf extensioned (Windows) docs.
STILL, the "ideal" thing to HOPE & wait for? A patch from Adobe, of course... not workarounds like this.
APK
P.S.=> See, it's ONLY that I had the benefit/advantage of seeing this one coming a LONG time ago (more than a year ago @ least), as well as attacks being used via Adobe Acrobat Reader in the past (like many of you no doubt ALSO have) before this instance of it happening...
(& thus, I put up a SIMPLE method for anybody to utilize, in HOW to stall it @ THE SOURCE, above, more than 1 yr. ago wherever I posted that guide online in late 2007...)
AND, guys? IT WORKS, because "IF YOU CANNOT GO INTO THE scripted KITCHEN, YOU CANNOT GET BURNED" type thinking... apk
I guess you didn't bother reading Secunia yesterday.
Scripting disable is irrelevant.
help me i've cloned myself and can't remember which one I am
"I guess you didn't bother reading Secunia yesterday. - by SmurfButcher Bob (313810) on Wednesday February 25, @03:11PM (#26985967)
That's NOT quite true... read on!
See this quote, regarding the disabling of javascripting in Adobe:
----
http://secunia.com/blog/44/
"While this does prevent many of the currently seen exploits from successfully executing arbitrary code (as they rely on JavaScript), it does not protect against the actual vulnerability."
----
AND, I admit - it's JUST turning off the USE of the .DLL (lib) that has the problem, but, NOT FIXING IT!
(in disabling javascripting in Adobe Acrobat 9.x... you don't call on its functions, & especially with malicious script? NO problems SHOULD result).
(& who says it's NOT javascript inside these malicious .pdf files? AND YES, sure - admittedly, there ARE other ways to take advantage of a buffer overflow, but why, when javascripting is the easiest route, for MOST folks vs. say, firing up debug & compiling data in a memory address space afforded by a buffer overflow, for example (poor one)?)
After all - Javascript?
Hey, it IS the engine .pdf files run from Adobe Acrobat actually USE, in order to execute their macros ("arbitrary code", as 1 possible here, just like in a malicious word .doc file)!
----
AND STRAIGHT FROM ADOBE THEMSELVES:
http://www.adobe.com/support/security/advisories/apsa09-01.html
"Reports have been published that disabling JavaScript in Adobe Reader and Acrobat can protect users from this issue. Disabling JavaScript provides protection against currently known attacks. However, the vulnerability is not in the scripting engine and, therefore, disabling JavaScript does not eliminate all risk"
----
Thus, you can see, they DO admit it helps... even here, just NOT against "all possibles" (such as other means of exploiting buffer overflows I noted above)...
BUT, they do admit, however, that it DOES stall out the ability to execute arbitrary code (of the malware makers' choosing) & guess what? THAT IS THE ACTUAL MALWARE PAYLOAD detonator, in scripting, & in MOST of the attacks online, today...
----
IMPORTANT:
Also note, that later on in my post?
I do point folks to a FIXED .DLL file for this... but, it too, is NOT guaranteed as a permanent cure & it's NOT for any Adobe Acrobat versions earlier than 9.x though...
APK
P.S.=> AND, what I am noting here? Hey - This is NOT a 'cure', it's a protective work-around... as is the secondary method I noted, of a FIXED .DLL available from a 3rd party, also, as an alternative for Adobe Acrobat 9.x users... apk