IE 7.0/8.0b Code Execution 0-Day Released 131
SecureThroughObscure writes "Security blogger and researcher Nate McFeters blogged about a 0-day exploit affecting IE7 and IE8 beta on XP that was released by noted security researcher Aviv Raff. The flaw is a 'cross-zone scripting' flaw that takes advantage of the fact that printing HTML web pages occurs in the Local Machine Zone in IE rather than in the Internet Zone. Quoting McFeters's post: 'This is currently unpatched and in all of its 0-day glory, so for the time being, beware printing using the "print table of links" option when printing web pages.' McFeters and others will be presenting at Black Hat on the link between cross-site scripting and cross-zone. Rob Carter has been hitting this hard over at his blog, pointing out cross-zone weaknesses in Azureus, uTorrent, and the Eclipse platform."
0-day (Score:5, Insightful)
Re:0-day (Score:5, Informative)
Re:0-day (Score:5, Informative)
The whole point of coining the term in the first place was to be able to discuss the unknown; i.e., to be able to assess the potential danger of currently unknown threats. Day-1 refers to disclosure, as such there's no way to talk about a specific 0-day because if you know what it is than it has to at least be day-1.
Sure it's abstract, but it's an important concept for developing security technologies and security procedures.
Between product buzzwords and the abstract nature of the term it's almost lost all meaning.
Re: (Score:2)
Re: (Score:2)
But it got mutated because
Re: (Score:2)
Of course, that meaning is not very useful, because the vendor will need time to patch the exploit after it's known to it, and because unlike cracked software cop
Re: (Score:2, Insightful)
The whole "day thing" is about the time between disclosure and patch/signature release. Disclosure starts the clock: Day-1. Day-0 is for talking about the day before disclosure.
Re: (Score:2)
Re:0-day (Score:5, Informative)
> The whole "day thing" is about the time between disclosure and patch/signature release.
Do you have any citation for your assertion?
The term derives from warez "0-day boards". These were populated by the most elite crackers who had cracked software on the 0th-day of release; that is, the software hit the shelves and was already cracked.
Try doing a web search for ``0-day'' with a date threshold prior to, say, 1995. You won't find any hits for your interpretation:
http://www.alltheweb.com/search?advanced=1&cat=web&jsact=&_stype=norm&type=all&q=%220-day%22&itag=crv&l=en&ics=utf-8&cs=iso88591&wf%5Bn%5D=3&wf%5B0%5D%5Br%5D=%2B&wf%5B0%5D%5Bq%5D=&wf%5B0%5D%5Bw%5D=&wf%5B1%5D%5Br%5D=%2B&wf%5B1%5D%5Bq%5D=&wf%5B1%5D%5Bw%5D=&wf%5B2%5D%5Br%5D=-&wf%5B2%5D%5Bq%5D=&wf%5B2%5D%5Bw%5D=&dincl=&dexcl=&geo=&doctype=&dfr%5Bu%5D=on&dfr%5Bd%5D=1&dfr%5Bm%5D=1&dfr%5By%5D=1990&dto%5Bu%5D=on&dto%5Bd%5D=16&dto%5Bm%5D=5&dto%5By%5D=1995&hits=10 [alltheweb.com]
Try USENET for certainty ( blocked in work ).
Re: (Score:1)
Re:0-day (Score:5, Funny)
A Disturbing Trend, But Not Unforeseen... (Score:5, Insightful)
The more complex the software releases become, the more complex and insidious the exploits of them become also.
Re: (Score:2)
Exactly, this is why the most complex OS in history, Vista...
Oh wait, Vista is NOT affected.
(Sorry to the MS Haters Club, especially considering the obscurity of this exploit, compared to ANY of the last 5-10 major flaws found in FireFox.)
I'm not sure that holds up (Score:3, Interesting)
The more complex the software releases become, the more complex and insidious the exploits of them become also.
I'm not sure if that statement will hold up to scrutiny. If complex software is the issue, then you'd expect exploits to be consistent across platforms when comparing software of similar complexity. I haven't seen any research supporting that observation. I have seen research that says more complex software will likely contain more coding errors and potential exploits but haven't seen a correl
Re: (Score:2)
As far as security being an after-thought in Windows, that's not true. DOS and the Win9x line weren't designed to be networked, certainly not on an untrusted network. To some extent that was true of the earlier NT line as well; although security was needed and built in, it likely made the assumption that the network was at least somewhat safe.
Modern Windows (I'd say Win2000 and higher) ha
Re: (Score:2)
Re: (Score:2)
Amazing (Score:5, Funny)
Re:Amazing (Score:5, Insightful)
http://it.slashdot.org/comments.pl?sid=555236&op=Reply&threshold=1&commentsort=0&mode=nested&pid=23432544 [slashdot.org]
Why you would want that printed out on a piece of paper is beyond me. It might possibly somewhat work on a PDF printer, but even then, it's use is limited.
Re:Amazing (Score:5, Funny)
Re: (Score:3, Insightful)
Now for a real use? Well, maybe one. To save having to scribble them down, you could waste a couple reams of paper printing out, oh, maybe a dozen MS Sharepoint links to an overly-anal supervisor who demands that you include reference links in a printed report.
Proof (Score:5, Insightful)
Re:Proof (Score:5, Insightful)
Look, for most people, the zone idea actually makes sense. Basically, don't trust ANY web site to do the tricksy stuff, but add (for example) your company's intranet to the safe zone, where it can do more desktop-ish stuff. I don't think that's such an awkward concept, and it spares people from having to think through what to allow, or not, on a site by site basis, as they surf. Most people are not this audience. And being able to enforce zone policies at the enterprise level makes a lot of sense, since average users are routinely shown to be spineless and witless: they'll add a poisonous Russian casino spam site to the safe list if that site pops up a tutorial on the steps the have to take to do so, if they want their free emoticon package.
Fiddly, granular systems only work for fiddly, granular people.
Re:Proof (Score:4, Insightful)
I'll tell you why: because it has to. You can't access local devices in the Internet Zone. That's the point. Granular approaches would allow you to print without accidentally giving other permissions to something that shouldn't have them.
At the enterprise level, with something like NoScript, you can just allow entire domains, say intranet.example.com or whatever your organization uses.
Next thing you're gonna tell me is that you think Microsoft should do away with ACLs at the individual file level or even the directory because users are just too stupid to figure that out. They should just have "file zones" and people will just have to stick their files in the right zone. Pffft.
Re:Proof (Score:4, Funny)
Re:Proof (Score:4, Insightful)
Re: (Score:3, Interesting)
Re: (Score:1)
Furthermore, you can make it is as granular as you want. If you want list individual servers, do it, or if you want to control it by CA, do it that way.
Re:Proof (Score:5, Insightful)
Re: (Score:1, Funny)
Re: (Score:2)
Re: (Score:1)
yes, but which is more likely on a daily basis. When a internal employee attacks and is found, in most company's he gets no more chances to be a ass. When a external attack is found, one of his computers is blocked, a new IP address is all thats needed for him to try again...
At my work their about 10 people with the ability to do this intentionally, of course the more likely is that they got infected from the internet, but if that was blocked, how did that happen again?
of
Re: (Score:2)
At my last employer, setting up a webserver wouldn't have been necessary. Everyone could get read/write access to the real intranet servers via their C$ share. Oh, Windows.
Re:Proof (Score:5, Insightful)
The concept itself is okay, but the implementation could use a good, solid overhaul.
MySpace (Score:2)
he first time someone wants to diddle with a MySpace app and discovers that it won't work until you basically ratchet down the settings --often by hand in the advanced options--
You realize that MySpace is nothing but personal ads for child molesters, right?
If you're running apps from there... be careful
Re: (Score:2)
Its almost the last place on the web you should be "ratcheting down" IE's security settings.
Re: (Score:2)
Re: (Score:2)
If you're ratcheting down the zone settings for one site, you're NOT using zones correctly. What you'd want to do is add MySpace to your Trusted Sites zone. Now MySpace has the permissions it needs, but the rest of the internet still is kept on higher guard.
Thing is it ain't that easy (ref. a similar post to mine that explains it better). This could apply almost anywhere that has a ton of mixed content (for instance at my work, where one has to do it just to get some of the corp's more bone-headed ActiveX controls to behave normally).
The problem is, you and I can grok-out a way around it. My wife (or any other non-tech-oriented person) cannot, at least not without a lot of Googling and even more patience (or a more tech-oriented spouse to impose the issue
Re: (Score:2)
That said, for stuff like Facebook and MySpace, I'd use a virtual machine
Re: (Score:3, Insightful)
Also, having developed desktop applications that used embedded IE, I can tell you the zones system is completely screwed-up. It changes in every version, the APIs are inconsistent across different Windows OS's, and there are crazy looph
you wrong! (Score:1)
This is proof of what I've said from the beginning -- the whole concept 'zones' in IE is stupid and pointless.
IE's zones is a very good thing because it gives different level of security based on zones, "internet zone" has an higher security, "local zone" has a lower security, "restricted zone" has the maximum security.
Scripts should be allowed only what you allow them, period.
"allow or cancel" question for each site you visit? are you crazy???? scripting is not dangerous unless there's a flaw in javascript.
You should be able to give permissions down to the individual site
you can do it with IE by putting the sites into the different zones. If you want block a site, just put it in "restricted sites" zone.
(ala NoScript) or even down to the individual script.
"allow or cancel" question for
Re: (Score:2, Informative)
If only JavaScript were the only scripting option on IE. Furthermore, JavaScript is one of the primary vectors of attack for Firefox, IE and Opera: what makes you think that an untrusted JavaScript is NOT dangerous?
Right. Again, see how NoScript does it. Far easier and more convenient for the user, IMHO.
Re: (Score:2)
That's insufficient. The danger from scipts comes from sites you *do* trust that get hacked. And if you grant permission per script, how many people are competent to read a script and judge it to be non-malicious? Of those, how many will feel like taking the time for every single script?
NoScript is good, and I use it, but it's far from sufficient to secure the browser against script-based attacks.
Re: (Score:1)
Re: (Score:1)
Re:Proof (Score:4, Insightful)
You would also have every web developer in the marketplace whining about how IE ignores standards if they pulled the plug on scripting.
Sorry but Zoning in IE is fine. IE 7 is actually a pretty good modern browser and, sure, it isn't perfect but frankly what is?
Re:Proof (Score:4, Informative)
Unfortunately, IE7 has made things a little more difficult:
- Pages with content from various zones no longer show up as 'mixed'. Since the upgrade to IE7, all sites only show the zone of the main URL, however the content runs according to the security zone for it's own source. It makes it almost impossible to work out whether a site can or can't run scripts, and you end up digging into the pages source code to work out what sites need adding to the trusted zones to get pages to work.
- Dynamic scripts added to a page in the 'trusted' zone, execute from the 'internet' zone. This is "by design"... The only workaround is to change the way the code works on the server.
- If you want to lock down the 'internet' zone, you will need to add "about:internet" to your 'trusted' zone
- You will also need to add res://ieframe.dll to your 'trusted' zone
Re: (Score:2)
Re: (Score:2)
The zones concept isn't perfect, but for the technically quasi-literate it's generally a better solution to the problem. Golden rule of design: don't build things as though your users are smart, because most of them won't be.
Usage (Score:5, Funny)
yes, I use it (Score:2, Informative)
Re: (Score:1, Troll)
Re: (Score:3, Funny)
It didn't take.
Re: (Score:2, Offtopic)
Re: (Score:1, Troll)
Re: (Score:1)
Oh yeah? (Score:4, Funny)
Oh yeah? I use Internet Explorer in XP under non-admin mode in a virtualbox install on Cygwin on a virtualbox install of XP inside a Linux virtualbox install under a SELinux host!
HAH! Take that!
Re: (Score:1, Offtopic)
Oh wait...
Re: (Score:2)
Well, it protects you from the code execution problem (but is apparently still vulnerable to an "information disclosure" as a result, but I don't know the details) for this particular flaw. But using Firefox or Opera or IE6 also protects you from this particular flaw.
Re: (Score:2)
For using IE since 2.X... (Score:3, Funny)
Irresponsible disclosure (Score:5, Interesting)
Re:Irresponsible disclosure (Score:5, Insightful)
Re:Irresponsible disclosure (Score:4, Insightful)
Re: (Score:2)
Re: (Score:1, Troll)
Re: (Score:1)
Re: (Score:2, Informative)
Re: (Score:2, Insightful)
Yes, as always... blame the whistle blower not the manufacturer of the crap product.
*feeds the troll* (Score:3, Insightful)
We *might* be blaming Aviv for telling the world, script kiddies and botnet operators alike, about this bug -before- even notifying the manufacturer of the crap product.
Nor did Aviv wait a reasonable time period for the manufacturer to admit their product's crap state and issue either A. a warning of their own (don't print links) or B. a fix, while providing full credit for discovering the bug to Av
Re: (Score:2)
Re: (Score:1, Troll)
Re: (Score:1)
Can it be triggered via javascript? (Score:5, Interesting)
If not it's a rather useless exploit other than as a prank to pull on your secretary... "Hey Sandra... can you print out a table of links for this website?"
5 minutes later "What the F***!"
"HAHAHAHAHAHAHA... I totally got you!"
Re:Can it be triggered via javascript? (Score:5, Informative)
Re: (Score:2)
No (Score:5, Informative)
To view this article on one page... (Score:5, Funny)
end sarcasm
Re: (Score:2)
Re: (Score:1)
You can't grep dead trees.
I'll be back in a bit ... (Score:2)
Re: (Score:1)
*crickets*... What?
Must we highlight every bug in IE? (Score:2, Insightful)
I appreciate the desire to raise awareness, but there's no practical benefit to running this story other than Windows bashing. It'll get patched, the patch will probably ship on some future Tuesday given this is a feature few people use and the risk of exploitation is relatively low, and that'll be that.
In contrast, a far more dangerous bug [debian.org] in the openssl package used by Debian and its derivatives was discovered earlier this week, and doesn't seem to have made the Slashdot home page at all, even though i
Re:Must we highlight every bug in IE? (Score:5, Informative)
Re: (Score:2)
Re:Must we highlight every bug in IE? (Score:4, Informative)
http://it.slashdot.org/article.pl?sid=08/05/13/1533212 [slashdot.org]
Re: (Score:2, Informative)
In contrast, a far more dangerous bug [debian.org] in the openssl package used by Debian and its derivatives was discovered earlier this week, and doesn't seem to have made the Slashdot home page at all
Re: (Score:3, Funny)
Re: (Score:1)
WTF is a "0-day" ? (Score:2)
"0-day" doesn't mean a f$%^&ing thing ! There is no information being transmitted by that phrase, it is empty of any meaning and might as well be a punction mark.
Re: (Score:1)
"0-day" typically is used in the warez/cracking scene. 0-day releases are essentially programs or games or whatnot that are cracked or released for download the same day (or even before) they hit retail shelves. So you've got 0-day games, 0-day cracks, etc. - but in the context the summary uses the term it doesn't really seem like it means anything unless it coincides with a brand new release
Re: (Score:1)
Re: (Score:3, Insightful)
A zero-day (or zero-hour) attack or threat is a computer threat that tries to exploit unknown, undisclosed or unpatched computer application vulnerabilities.
So, it's a newly discovered exploit. Can't we use that phrase instead of the uber-lame "0-day"
Re: (Score:2)
I'm save... (Score:1)
0-day.... (Score:1)
Printer Paper Eating? (Score:1)
0 Day on IE (Score:1, Offtopic)
IE - It Executed
0 Day - 0 Productivity. Nothing works.
So It Executed 0 Day and nothing works and there was no productivity.
And ol Br'er Mac User, he jus' sits back and LAFFS!!
zones are meaningless, useless, stupid, etc. (Score:2)
Printer-friendly version (Score:3, Funny)