New Outlook Bug Doesn't Require Users To Interact With Emails To Be Compromised (softpedia.com)
An anonymous reader writes: A new bug in Outlook allows attackers only to send you an email, and without clicking or downloading attachments, a user's computer can be compromised. The bug [PDF] is because Outlook allows Flash objects to be previewed without a sandbox. Flash files are demon spawns and attackers can put exploits in malicious files, which when previewed or viewed inside an Outlook application will automatically execute their payload.
How much better would the world be without Microcrap and Flash?
Pity, they are like a plague. Like Zombies. We don't seem to able to get rid of them.
The Melissa mail worm seems to be forgotten, but there's a new generation of coders now that weren't even in school when that occurred.
If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
Years ago we were warned to turn off Outlook previews, for exactly this reason. Also, my copy of Outlook doesn't download or render attachments (or even images) unless told to, for every individual email. As far as I know, that is the default behaviour. The danger is that you can whitelist senders so that their attachments are downloaded without confirmation, and spammers often use commonly used email addresses as the originator.
The summary is incorrect as well. FTA: "The only condition is that the user views or previews the email in which the attacker has embedded a malicious Flash file." So you still need to click. The only exception is if your Outlook is set to always download attachments, show a preview, and if the malicious email is the last one to arrive, since the mail will then be shown in the preview window upon opening Outlook.
Lastly, Flash needs to die
If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
Why doesn't the summary mention that this was fixed by an update released on patch tuesday dec 8?
* It's yet another flash bug,
It is not just Flash. If you read the article more carefully, you would have seen this (from the article):
We use Flash OLE object as an example since Flash (zero-day) exploits are easy to obtain by attackers, but please note that there are other OLE objects may be abused by attacker, as not only Flash but also a number of other OLE objects can be loaded in Outlook.
I am going to hit on a few of your points...
The problem is two pronged. Yes, having flash installed is a huge risk but the other part of the prong that keeps flash alive is the multitude of sites out there that require it for whatever reason. Until those sites stop requiring flash to operate correctly, you will see flash hanging in there.
You forgot to add in "and you view email in HTML." I have Outlook (at work) set to only use plain text for both receiving and sending. Allowing HTML in email is the stupidest thing ever implemented. That is what truly needs to die!
The headers won't tell you shit about embedded flash. So when 80 year old Aunt Marge gets pwned and used as a relay for this bug you still get it.
This is a sig. This is only a sig. Had this been an actual sig you would have been informed where to tune for more sigs.
Lastly, Flash needs to die
Just curious... why are people on a coding site declaring "Flash needs to die" instead of something like, Flash needs to be completely deconstructed and rewritten by the open source community using the most conservative style of programming, a system that forces a multi-person review of commits, hit with the best enumeration tools we have, so that arbitrary code execution is not possible? Which might be possible because processor speed has improved since it was first designed and the assembly level hacks that made it possible areno longer necessary? And when we are done, the worst thing that could ever happen is that someone might display goatse.cx inside a Flash window?
Instead of busting into the kitchen, grabbing pans off the wall and showing the chef how steak should be done, we sit at the table banging our forks and knives, shouting, "Down with meat!"
It's easy to make fun of Outlook, where with maliciously crafted embedded binary OLE blobs you can trigger exploits in many versions of Microsoft products. The faults lie in the products themselves not the Blob. But Flash self contained and lives inside a little rectangle. It is cross platform, amply documented and widely used today. Why must it die? So that generations of beloved Internet content can be 'destroyed' overnight? It almost smells like book-burning.
<blink>down the rabbit hole</blink>
I really don't understand why TFS starts with "A new bug in Outlook..." - after all, it's the SAME bug in Outlook -- since about 1997. Looks like the marketing department at Microsoft, in their endless desire for yet more whizzo shit has (potentially/inevitably) won yet another Pwnie Award. Whenever I see someone with a palm-shaped bruise on their forehead, I know they're a Windows sysadmin. This one reminds me of that Windows Explorer bug that executed arbitrary code from inside image (picture) files when you opened the directory they were stored in.
"As if millions of voices cried out 'DUH!!!' and were suddenly silenced."
Not really. The proposed new name is LookOut!
Well, the fortune cookie did say "Outlook not so good".
Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
That's actually a valid and important point. Flash files are executable code. How many dozens of significant vulnerabilities have been caused Outlook running macros, Flash, Javascript, and other types of executables embedded in emails? Outlook has at least three or four programming languages it can run from emails.
That's entirely unnecessary. Many people, including myself, have always used email clients that just read email - they don't, and can't, execute anything. If security is important to you, it makes sense to consider whether your email reader really needs to be able run code found within emails, whether your web browser needs to also be your desktop shell, as "a fundamental part of the Windows operating system", etc. There many are huge classes of vulnerabilities that can't happen if you choose software that simply does it's job, without hundreds of tangential features bolted on unnecessarily.
did you mean the magic 8ball?