No JavaScript Needed For New Adobe Exploits
bl8n8r writes "More woes for Adobe as a security firm creates a proof-of-concept attack that injects malicious code as part of the update process. The user only needs to click a dialog box to execute the code and no JavaScript is needed to launch the exploit. The exploit affects Foxit as well as Adobe Acrobat software. This exploit is made possible through the host software allowing execution of system binaries. Not clear if it's multi-platform, but seems plausible."
Since it's part of the PDF specs, it should work in Linux too. What's even worse than with Windows is that since 'rm' is just a normal binary the PDF can launch that, and if you run as root privileges, just issue a command like "rm -rf /". If you don't run as root, then for example Ubuntu should give you the sudo box to input password to. This of course being just one of the examples it could do. Remember that most malware doesn't even need root access to function.
Another reason why it would be even more serious on Linux is the way you can pipe commands and how most systems come pre-packaged with a ton of little utility apps. You can create the whole malware with a series of commands, or wget a bash script from the internet and start that to hide even more malware in the system. Since most Linux systems dont even have the kind of application firewalls or antiviruses that Windows does, and because the Internet accessing is actually done via wget, they don't even get any kind of a "Give internet access to this application?" dialog.
It also doesn't help at all that most Linux users (especially those who are told so by the geeks!) believe that Linux cannot get malware. In my opinion this is a really stupid thing to do from those promoting Linux or Mac OS X as it will just lead to false sense of security.
Is it any wonder that I uninstalled adobe reader entirely? Reading a lone pdf once in a while isn't worth having a massive security flaw exploitable with a no-click hacking trick.
Have the dialogue control specify that you are potentially allowing the PDF to alter other documents (maliciously or otherwise).
It's not exactly the first time a method of using social engineering to trick people has been part of a standard. Altering the status bar in JavaScript in order to aid phishing attacks was one.
I believe this exploit has already been patched in FoxIT, assuming this is the same exploit descibed here on SlashDot 2 weeks ago. Strangely, I haven't seen an update from Adobe ...
You clearly didn't read the article or even the summary. This exploit affects Foxit too. It's an exploit of the PDF standard itself
Doesn't the summary mention that Foxit is vulnerable to it as well?
"The exploit affects Foxit as well as Adobe Acrobat software."
As has alreay been pointed out, the worst this "exploit" can do is elevate to the same rights as the user. As anyone with a CS degree (or even any true IT experience) would know, these rights should be limited.
Now, Microsoft has for DECADES pushed the paradigm of giving the user administrative rights. Sure, they are making solf half-hearted attempts now to change this. But they created an environment of 3rd party software relying on this full rights model... and it is biting us all on the butt.
So, as usual, Microsoft is to blame.
See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
I wonder if Adobe Acrobat Reader 5.0 is affected.
Screw adobe and other client side PDF readers. Am I vulnerable if I use Google's PDF viewer to view PDFs?t
Really, throw that bloated, filthy piece of shitware to hell already and go with FoxIt.
You can at least RTFS.
The exploit affects Foxit as well as Adobe Acrobat software.
I mean, is yet another Adobe exploit story really that newsworthy? Next you'll post stories on /. index page saying that water is found to be wet as usual.
Colorless green Cthulhu waits dreaming furiously.
Linux is a lot different than running as root all the time on Windows. My security updates are pushed to me as they are fixed, not even pushing up to a month of vulnerability to patch unlike some systems meant to make corporate IT admins happy. All popular Linux distributions have an updating function: you get your security patches and patches to everything else in your repositories a lot more consistently than Windows. To deny this shows unfamiliarity with Linux. Thats even before you get into functions like selinux and apparmor which happen to be standard on my flavor. For everyone. This is also an Adobe bug, and doesn't affect most Linux PDF readers as far as I'm aware and even if it did I'd have a lot more faith that the Linux ones would be rendered immune more globally than the hodgepodge of updating (or lack of) systems on Windows. You're pointing the finger at Linux and saying: "You're vulnerable too!" But in the practical real world it is a case of not.
Shh.
Why can a document execute anything?
I want to delete my account but Slashdot doesn't allow it.
A little better than the crummy cnet write-up. http://blog.didierstevens.com/
boycott slashdot February 10th - 17th check out: altSlashdot.org
Presumably xpdf's "pdftotext" isn't vulnerable?
Really, throw that bloated, filthy piece of shitware to hell already and go with FoxIt. And, yes, I think my use of the word FUCK is warranted here.
I agree. Fuck is warranted here. You are too fucking lazy to read the summary or too fucking stupid to understand it.
The exploit affects Foxit as well as Adobe Acrobat software.
Turning to a Linux advocate for thoughts on Microsoft is like asking Hitler how he felt about the Jews.
"More woes for Adobe [i]as security firm[/i] creates proof-of-concept attack that injects"
"As security firm"? Who does the article mean, Jeremy Conway of NitroSecurity, or Didier Stevens, working for Contraste Europe? Also, it would've been nice if the article linked to an article Jeremy wrote titled "Implications of Recent PDF /Launch Hacks", this article can be found here: http://siemblog.com/2010/04/implications-of-recent-pdf-launch-hacks/
Dupe from Slashdot, March 31st
See http://slashdot.org/story/10/03/31/1834255/New-Method-Could-Hide-Malware-In-PDFs-No-Further-Exploits-Needed
The exploit was actually WORSE if you were using Foxit. Acrobat Reader would pop up a warning about running an executable, but Foxit wouldn't warn, it would just run it. On the other hand, Foxit has already issued an update.
As others may have stated -- but I definitely want to underline -- the broken security model of Microsoft Windows causes significant potential for harm by this exploit. I guess if you run Windows you're accustomed to grabbing your ankles though.
I'm at the point where if you run Windows and have the audacity to complain about the exploits, bugs, worms, trojans, et al, you get no sympathy from me. The world has known about Microsoft's crappy security for decades, and Microsoft has done little to improve it. How many unscheduled patches have rolled out their door lately? Why do they have a "malicious software removal tool" updated monthly? (Hint: it's not because Windows is well-designed)
To use a car analogy, Microsoft produces cars, all of which have this huge hole in their roofs. Instead of redesigning the roof or putting something over the hole, they want you to buy a carpet replacement subscription. Each time, you dole out the money for a new copy of Windows, thinking "this will be the one!" and each time you are disappointed. When will you get smart?
I'm not quite ready to say that Microsoft chooses to have broken security, but it's obvious -- if that's not the case -- that Microsoft clearly doesn't understand security. But is that really better? How many people do you know who have been infested with viruses, trojans, etc on Windows operating systems? How many of those got infected despite installing antivirus software and keeping their machines up-to-date? Nowadays having only antivirus on a Windows machine is just asking to be rooted, and I don't think it's the new computer users' fault. It's getting worse every day.
Nobody uses the root account in Linux for everyday activity.
Really? More than you think...
So no worries about the system in general.
Dangerous assumptions continue...
If you want news from today, you have to come back tomorrow.
As it’s apparently a standard PDF feature, giving it a shot to run whatever command line its author desires...
Yeah, it would affect anything that supported that feature.
Note that the clean pdf, after it is infected, pops up the window asking to run “firefox.exe sudosecure.net”. I’m not sure exactly how he did it, but note that there is a huge mass of text (judging from the scrollbar) above the “it’s okay, let me do this” message in the evil pdf. He’d have to somehow create a malicious binary and then execute it. One suspicion I have... a polyglot.
evil.txt:
Then...
Result: evil.pdf opens just fine in Acrobat Reader, but it has the injected code at the beginning, disguised as a comment.
No comment of whether it is specific to 32-bit or 64-bit versions of Windows... and why might that be significant, you ask? Because 64-bit versions of windows do not include DEBUG.EXE.
Alexander Peter Kristopeit bought his basement from his mommy for one dollar.
... to run multi-platform? >;->
http://developers.slashdot.org/story/10/04/04/1627226/Multi-Platform-App-Created-Using-Single-Code-Base
Would switching to a non-Adobe PDF viewer make you safer? I understand this exploit affects Foxit, but there are many other exploits and PDF viewers (MacOS X's Preview, Ghostview/GSView, CutePDF, Nitro, etc.).
Usually the headline says the exploits are in Acrobat; and given Adobe's much larger installed base, they are a much more likely target; but perhaps the exploits are really in PDFs (or JavaScript) in general.
This feature is in the PDF specification, and in fact in the youtube video you'll notice that the trust manager warning is pretty severe "only do this if you trust the PDF" sort of thing.
To me its akin to downloading an EXE from a website with a browser and clicking the open button...
You clearly didn't read the last week's Slashdot article. This exploit is already fixed in Foxit.
One of the tags says "saynotopdf" (Say no to PDF). I'm just curious to know if someone has knows or has need a useful alternative?
Between the format wars (.doc, .docx, open office .doc, .odt, etc) and between the HTML / Browser standards (ie6, ie7, ie8, firefox, safari, opera, etc), PDF seems to be the only consistent way to view things across all OS's. Sadly, it's very useful for that reason...
Quick google search didn't show anything useful except for a /. article from 2006 (Unipage) ... But the link on that page is dead now. Googling "unipage" didn't seem to show anything useful after 2007 (Investintect.com)
Any Ideas?
Why can't there be a standard of just layout, for a document. I don't want or need javascript, or embedded executable, or interactivity.
I always thought that's what PDF was, then all these exploits surfaced, mostly for stuff that I don't want or need (or even knew PDF had and allowed!)
I've also set up my browsers to open PDFs in GoogleDocs, which seems to be a tad safer.... maybe...
Can we please stop calling this an "exploit"?
As stated by numerous other individuals it's in the ISO spec, so it is literally a feature not an exploit. The hack is to change the warning message in a social engineering feat. Instead of Adobe's "Srsly d00d u want 2 open these hax.exe??" the user gets "Click allow to view this encrypted pdf" or even something more suitable for different social engineering attempts. The analogy to downloading a .exe from a website and clicking open is pretty accurate, but you can't change the message in that box to mask the executable about to be called.
So to sum this up:
-launching an executable from a PDF is a feature
-changing the warning message can be exploited in a social engineering attempt
With these weekly major security exploits coming out now, does anyone actually still use Acrobat Reader at their place of work!?!
I thought for the most part 3rd party readers were immune to this crap as well, but i've heard of foxit being exploitable as well for the last few
I've switched the company that I admin for to Sumatra PDF long ago because i got tired of chasing after the weekly updates and applying them to all the machines. Also because of the continued bloat of Acrobat Reader.
Something's really wrong when for the most part Sumatra can cover the major needed functionality in just a few MB, when reader has bloated up into the tripple digit MB
A user only gets Acrobat if they can prove a valid need such as a PDF that wont display properly in Sumatra.
Comment removed based on user account deletion
At least according to Didier:
http://blog.didierstevens.com/2010/04/06/update-escape-from-pdf/
You should stick to posting your faggoty copypasta about Kelvins, because everything else you post is as gay as AIDS.
You and sopssa (ASS POS, amirite?) need to die in a fire.
The summary is inaccurate. Foxit has already patched this problem in the current version.
Do what thou wilt shall be the whole of the Law
... well, yes, it does, rather...
so its a feature that can be exploited (easily). deal with it.
This seemed like a reasonable sig at the time.
Well... let's see what they understand by "fixing it" in FoxIt: they now give the warning dialog that Adobe's reader already gave.... except that for Adobe the default is "do not open" while for the "fixed" FoxIt the default is "open". Yeah, much more secure than Adobe, clearly.... In other news, let me remind you that all your web browsers are insecure: Someone can use "social engineering" techniques to get you to visit a web page, download a binary from there (trojan, maybe), and execute it. All you need to do is click a link, answer "Yes, run!" to the warning dialogs, and BAM! you're infected. Quite similar with this PDF "exploit", in fact.. So stop using your web browser, it exposes you to a serious security vulerability.... even if you disable Javascript! :D