New IE 8 Zero Day Discovered
Trailrunner7 (1100399) writes "Researchers have disclosed a new zero day vulnerability in Internet Explorer 8 that could enable an attacker to run arbitrary code on vulnerable machines via drive-by downloads or malicious attachments in email messages. The vulnerability was discovered and disclosed to Microsoft in October, but the company has yet to produce a patch, so HP's Zero Day Initiative, which is handling the bug, published its advisory Wednesday. The ZDI has a policy of disclosing vulnerability details after 180 days if the vendor hasn't produced a patch. The use-after-free flaw lies in the way that IE handles CMarkup objects, and ZDI's advisory says that an attacker can take advantage of it to run arbitrary code."
this IS a critical bug... onehundredandeighty days... 180 zero days. why? MS wants to drive up marketshare of competing browsers incompetence? MS employees acitvely exploiting the bug?
I've had it. Nothing is secure. Nothing works. I'm going back to an abacus and an Etch-a-Sketch.
0day can happen to anybody
Can't Balmer spare any developers developers developers?
>80 column hard wrapped e-mail is not a sign of intelligent
>life
if microsoft has been sitting on the bug report for six fucking months.. it's an old and ignored bug, certainly not 'new'... although since it's 'out there' now, there will be 'new' malware that utilizes it.
Aren't they on like IE 10 by now? I don't use it so I haven't kept up with it.
You are welcome on my lawn.
Face it: There's an element of risk online. Has been for decades. You take your chances. You also take risks like it everyday (driving an automoble for Pete's sake - so let's be realistic here). Just learn to be cautious on how to use any of them more safely.
APK
P.S.=> Use this or the resultant file from it to aid in doing so (it works for added speed, security, reliability, & even anonymity) -> APK Hosts File Engine 9.0++ 32/64-bit: http://start64.com/index.php?o...
... apk
Internet Explorer 8 was the last Internet Explorer available for Windows XP. Was Microsoft tempted to ignore the security exposure until XP fell out of support? Are there other security vulnerabilities in Windows XP reported before April, 2014, that Microsoft has ignored? Will Microsoft ignore (or at least slow walk) reported security vulnerabilities in their other products as they get nearer (but not actually reach) their end of support dates?
These continuing security defects are really beyond ridiculous. Maybe regulators -- the European Commission? -- ought to be mandating that vendors fix security vulnerabilities in their products within, say, 120 days. That would extend to all products sold (refurbished, new, whatever) within the past, say, 7 years. Otherwise, the vendor will be automatically barred from selling anything unless and until their security messes are cleaned up.
They give NSA all of their backdoors months in advance. Do not use Microsoft products!
It is really a sad state that computer systems are in nowadays. Every year multiple vulnerabilities are published showing how easy it is for someone to find critical vulnerabilities in software used every day by citizens and government officials. I bet the NSA is into Chinese government systems and China already has access to american government systems. The underground hacker/criminal scene certainly already has access to corporate and government systems too if you think about how many vulnerabilities are found every year and the underground market to sell not yet published vulnerabilities. Obviously not only the good guys who publish the vulnerabilities find vulnerabilities. I wonder what the ratio is but I bet the good guys don't have that much of a lead. Maybe we are going about this wrong and instead of making people think they are secure they should assume all governments are not secure. This would bring about a cold war. China won't critically bring down American government systems because they know that America would just do the same to them :).
With articles being published that show that the NSA is putting trojan software in exported systems you can certainly bet that other countries are doing the same. Are you sure that USB drive you ordered from China is only a USB drive?
We need a revolution in computing when it comes to security. While we have seen improvements in security over the years we don't seem any closer to solving security issues than we were 10 years ago when it comes to the apps that every day users use.
American Date Format :DIE Already!!!!!!!!!!! .....[shhh the nsa is listening]
American Imperial Units: DIE Already!!!!!!!!!!
American Imperialism :
46137
What's with all the illiteracy these days? It's not a "zero day"; it's a "zero-day". Zero-day is an adjective and must be hyphenated.
Zero-day attack
Up shit creek w/o paddle.
Somebody done burned old dixie down.
It's "640k 0 days should be enough for anybody". I'm not going to tell you again.
According to the timeline it is a -180 day.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
"Researchers have disclosed a new zero day vulnerability in Internet Explorer 8 ... The ZDI has a policy of disclosing vulnerability details after 180 days if the vendor hasn't produced a patch.
So then wouldn't that make it a minus 180 day vuln instead? </snark>
Oh -- it was found 180d ago so that's be a plus 180. Wrong orientation base there, sorry.
If the universe is someone's simulation -- does that mean the stars are just stuck pixels?
Honestly, I hope they do not release a patch so that all of the sysadmins they turned into liars with the last one can get some of their credibility back.
Doesn't matter even if it is a newer version e.g. IE10, IE11.
If you're in a corporate environment and some legacy in-house apps only play nice with IE, cough out some money and upgrade or port those apps.
It's time to let IE go the way of Realplayer: once annoyingly ubiquitous, now a mere footnote in tech history.
OK, first I was confused because I read IE 8 as Windows 8.
So a bug is discovered in IE 8, which has been deployed for a long time... but...
Somehow the meaning of "Zero Day" has changed over the last few years. It used to mean a vulnerability that was discovered before a version of software even went live.... ouch.
Now the definition on wikipedia seems to pretty much include ANY vulnerability that hasn't been patched. So by definition ALL vulnerabilities are "zero day" until the vendor releases a patch... so therefore to add the "zero day" adjective in this context is meaningless...
IE is a vulnerable pile of crap and always will be.
Everyone that doesn't live under a rock already knows this.
No amount of "ZOMG! NEW HACK FOUND IN IE!" announcements is going to get through the skulls of those that still use it.
Please, no more stories about IE vulnerabilities. Consider it a standing notice "IE is a POS"
It WARNS YOU AT BUILDTIME OF HOSTS TO TURN OFF DNSCACHE in its SAVE tab... thus, you didn';t use my app, or you don't read & follow directions.
That's also widely documented online by the way -To turn off usermode slow faulty with large hosts files dnscache service.
* It causes a lag with larger hosts files - it's a KNOWN issue!
(Nice part is that when you turn off dnscache service, you stop that "lag" & also save CPU cycles, RAM, & other forms of I/O it uses: double-bonus!)
APK
P.S.=> I regain indexing lost via its feature that allows "hardcoding" your favorite sites - I do 24 of them here @ the TOP of my custom hosts file... that equates to approximately 2-3 million indexed seeks AND seeks those favorites of yours as FAST as possible cached into RAM via the kernelmode diskcaching subsystem working in combination with TCP/IP itself also in PnP kernelmode design (higher CPU priority privelege than usermode, thus faster) in combination with DNSSEC secured EXTERNAL OpenDNS... apk
"Zero-Day exploit allowing the attacker to run arbitrary code"
I thought these words should be history based on the implemented NX bit, sandboxing, multiple lines of defense and Data Execution Prevention features of MS Windows after XP.
Why do all these features fail, when they are specifically designed for exposed code like IE? Or does this warning assume the worst case, where all these other features are turned off?
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
I'm a sales guy at a soon to be bankrupt company who has been tasked with light IT work because the boss is too cheap to hire a real one. Finally scared him enough to upgrade to Win7 (and pay for it lol). Everything went great updates/drivers seemed to install fine. All of them except for Internet Explorer! To which windows update says Error(s) found Code 9C59 Windows Update has encountered an unknown error. Spent a month on MS forums doing all kinds of voodoo and fixes still nothing. Offline installer package gives same thing. New updates download and install just fine, but were doing all our business on IE 8 which is insane. Anyone ran into this lately?
> Or does this warning assume the worst case, where all these other features are turned off?
It seems not. But remember that Internet Explorer was written to be inseparable from the operating system itself, with effectively bare metal access to provide Microsft-only speed, power, and enforced reliance on Microsoft's system libraries. It was designed _not_ to be lmodular, and designed _not_ to be clealy segregated from the underlying operating system so that it would be impossible to remove or replace on a Windows system.
In IE8, Internet explores YOU.
Now the definition on wikipedia seems to pretty much include ANY vulnerability that hasn't been patched. So by definition ALL vulnerabilities are "zero day" until the vendor releases a patch... so therefore to add the "zero day" adjective in this context is meaningless...
And a "new" zero day at that. That's a relief, it could have been an old one.
"Zero-Day exploit allowing the attacker to run arbitrary code"
I thought these words should be history based on the implemented NX bit, sandboxing, multiple lines of defense and Data Execution Prevention features of MS Windows after XP.
Why do all these features fail, when they are specifically designed for exposed code like IE? Or does this warning assume the worst case, where all these other features are turned off?
The NX bit, and DEP forced us to develop Return Oriented Programming https://en.wikipedia.org/wiki/... Basically because function arguments and return pointers are on the stack you can make the code that's already there do the work for you. It's not as easy as just writing a little shell code and tends to be more specific as far as the version of the software the victim is running, but it's really quite neat and hard to stop.
So lets pretend that we've just completed writing this code, as opposed to having just completed sabotaging it -Altera
Except this exploit is only in XP which lacks DEP and NX, based on your own sentence even... So your comment about features failing?
IE8 no longer needs to exist. The only technical reason for it is Windows Updates for XP which are no longer available.
I don't know if your problem was the same as mine, but I had a problem where I couldn't repair, or re-install IE11 for someone on Windows7 because it wouldn't update properly... I went to this website:
http://support.microsoft.com/kb/923737
and downloaded the automatic wizard... It seemed to reset the IE settings and it was smooth sailing after that...
Direct link for the file (MicrosoftFixit50195.msi) is:
http://go.microsoft.com/?linkid=9646978
Give it a try and I hope it works for you...
http://it.slashdot.org/comment... what you saw is a HUGE margin less than AdBlock eating 5gb of RAM & tearing up CPU terribly -> https://blog.mozilla.org/nneth... by way of comparison.
APK
P.S.=> I still don't believe you used my program, since it tells you (no matter what way you go to do it on SAVE) to turn off usermode slow faulty with large hosts files dnscache service (and gives you the services.msc tool to do it directly)... apk
Windows XP supports the NX bit, which came in with a service pack. Maybe you're thinking of Windows 2000? Though by default I believe Windows XP won't use it unless you specifically turn it on. And of course, you need to have a processor that has the NX bit in the first place. Windows Vista defaulted it to on (though only for the 64-bit versions), and Windows 8 requires it to the point where it won't boot on a processor that lacks the NX bit.