Slashdot Log In
IE7 Bug Reports Flooding In
Posted by
Zonk
on Thu Feb 02, 2006 08:32 AM
from the experience-them-now-avoid-the-rush dept.
from the experience-them-now-avoid-the-rush dept.
the JoshMeister writes "According to ZDNet, bug reports are already flooding in for Microsoft's new Internet Explorer 7 Beta 2 Preview. Specific issues include the possibility of arbitrary code execution as well as incompatibilities with McAfee Security Center, anti-spyware programs, and online banking sites." From the article: "... browser testers may already be at risk, according to security researcher Tom Ferris. Late Tuesday, Ferris released details of a potential security flaw in IE 7. An attacker could exploit the flaw by crafting a special Web page that could be used to crash the browser or gain complete control of a vulnerable system, Ferris said in an advisory on his Web site. Microsoft had no immediate comment on Ferris' alert."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Duh! (Score:5, Insightful)
Re:Duh! (Score:4, Insightful)
Parent
Re:Duh! (Score:2, Insightful)
Re:Duh! (Score:3, Interesting)
I think the notable part is its the same bugs as IE 4 had.. and IE 5... and IE 6...
Re:Duh! (Score:3, Informative)
Re:Duh! (Score:5, Insightful)
Parent
Re:Duh! (Score:3, Insightful)
Wow (Score:4, Funny)
Re:Wow (Score:4, Insightful)
I don't even see how this is a news-worthy... it's a beta!
Parent
Bug reports already? (Score:3, Insightful)
Taken with grain of salt... it's still beta.
good! (Score:5, Insightful)
(anyone who would use it - or anything else beta - in a production environment is insane)
OMG.... (Score:2, Insightful)
Of course it has bugs. Grow up already.
Security is Job 1? (Score:3, Funny)
Re:Security is Job 1? (Score:2, Insightful)
Re:Security is Job 1? (Score:3, Interesting)
What surprised me about beta 1 was that they hadn't even finished implementing features that were already on the final product's feature list. Actually, it seemed that they hadn't actually finished deciding what was going on the feature list.
Most people would consider that development stage to be alpha - beta is where you have finished implementing the feature list and you are now after feedback from the cus
Re:Security is Job 1? (Score:2, Insightful)
This a good thing (Score:5, Insightful)
Why is this front page, unless it's just the usual knee-jerk, let's-find-something-bad-to-say-about-Microsoft thing that makes Slashdot less than useful for info about anything about Microsoft.
Yeesh.
Re:This a good thing (Score:5, Insightful)
Why is this front page
This is on the front page for a number of reasons. First, it is somewhat indicative of the quality of the new software MS is planning to release. Yes, betas will have bugs, but no comment has been made about the remote exploit from MS, nor about the myriad failures to implement CSS properly. The number of bugs found in such a small time, is a meaningful metric and of interest to people here. It indicates to many of us, that the final version is still unlikely to properly implement the spec and that whatever new security practices MS is employing are probably not working to stop vulnerabilities. (Gee, big surprise.) The number of incompatibilities with current banking and other Websites is a useful indication to how much work the Web designers among us are likely to have ahead of us.
Second, because of the design of Windows and IE you can either install this beta for testing, or you can install the current IE, but not both. This means a number of people will install the beta, but end up also using it as an everyday browser, since they don't want to be constantly installing and uninstalling it for testing. Thus, security concerns with this beta may actually be a real concern. Those among us working to secure networks may want to account for this by restricting use of this browser for the time being.
Finally, the number of bug reports is a useful metric for gauging interest in the product, which is also of concern to people here.
Parent
Story is inaccurate... (Score:5, Interesting)
The guy is not a professional anything, I mean he lists workarounds as 'Firefox'; which just shows how little he understands the security field which he claims to work in (A workaround should be a way to fix or bypass the bug, not a blind pointer at some random other product, even the Linux Security guys know that).
Re:Story is inaccurate... (Score:2)
In most cases, yes - a workaround should allow you to continue using your current product. However, in some cases the affected product is considered so fundamentally flawed that alternative products must be considered. Even CERT has
Re:Story is inaccurate... (Score:2)
Bill not a programmer? (Score:3, Insightful)
blakespot
Bug identification & research for a beta relea (Score:5, Funny)
Not surprised by the bugs... (Score:3, Informative)
It's.. Beta? (Score:5, Insightful)
The past builds were also riddled with bugs, and the IE developers are very involved with testers to fix them. It's not like they're just sitting with their hands over their ears yelling "LA LA LA LA I can't hear you!"
Re:It's.. Beta? (Score:2, Insightful)
Of course, in reality, I use Firefox for everything, so it's a moot point for me, but nevertheless it doesn't make sense to me that someone would release a beta product and have it install over top of a production product.
More annoying than the bugs.. (Score:5, Interesting)
I'm not asking them to spend money advertising the fact that they're way behind the curve on browsers, just to stop lying to me.
Re:More annoying than the bugs.. (Score:4, Insightful)
Ok, this doesn't buy the customer much, but is it really all that big of a pain? Do you just conceptually object to Microsoft asking "is that a valid Windows you're using?"
Requires a reboot
I am not thrilled about this but given the wedding of the browser rendering component and the rest of the user experience ("OS"), i can't say i am surprised. You have to reboot after uninstalling it also, by the way
Actually attempts to pass off things like tabbed browsing and a search bar as innovative (really, take a look at the "demo" they bring you to when you first install it).
Consider part of the target market for IE7: People that are happy enough with the features of IE6 that they haven't bothered looking at Firefox yet. For them, tabbed browsing and a search bar are new and innovative. These are things that everyone will potentially benefit from but not all people will seek out and discover by themselves.
Part of the reason my grandfather uses a computer at a public library to do web surfing and write email is because Microsoft brings "cool stuff" away from the realm of the early adopter and puts it in the hands of everyone.
Parent
Re:More annoying than the bugs.. (Score:3, Interesting)
While not surprising, it's still crap.
The core flaw is that under Windows you can't delete a file that is in use. The accepted solution is to set up a little script to run on reboot that deletes the file and replaces it with the new version. That's sad and stupid.
The Unix solution allowing you to delete an in use file solves the problem. It has
Re:More annoying than the bugs.. (Score:3, Insightful)
where can I download the OpenBSD version ?
So let me get this straight .... (Score:4, Informative)
Treat IE 7 as IE 6? (Score:5, Interesting)
if (browser is Internet Explorer) then
emit HTML code that works around the numerous rendering bugs of IE
else (Mozilla, Netscape, Opera)
emit standards-compliant HTML code
With this kind of (flawed) logic, IE 7 will often be identified as IE, and hence be provided with IE 6-specific HTML code, whereas it should have been sent "correct" HTML code. The result may be, well, interesting
I really don't see what Microsoft can do against this. They can't expect millions of web sites to be updated overnight just to support IE 7.
Re:Treat IE 7 as IE 6? (Score:2)
Perhaps, for compatibility, they could make the UserAgent string pretend to be Mozilla? Put the real identifier in brackets where the obsolete website scripts don't expect it.
Obviously there's no precedent for this kind of shenanigans at all, but it might be worth a try :)
Re:Treat IE 7 as IE 6? (Score:5, Insightful)
Microsoft has eliminated several bugs that made it easy to identify IE6 and apply hacks to the CSS. For example, the "* html" selector let you apply CSS rules just for IE because it's ignored by standards-compliant browsers. Now IE7 ignores that too. However, the need for hacks is still there. IE7 still does not implement several important CSS features that necessitated the hacks in the first place, such as min-height.
If Microsoft were to decide that this beta was "close enough" or even if it fixes just the minimum number of things to keep major sites from breaking, that's not going to help. Designers will end up needing an entirely different set of hacks to make up for the fact that IE7 is *still* not a complete CSS2 implementation.
Parent
Report Non-Compliance As A Bug (Score:3, Insightful)
The web community should start flooding the bug reporting for the IE beta with reports about CSS and XHTML/HTML standards non-compliance. Anything IE 7 does that isn't in line with web standards should be reported as a bug, by as many people as possible. And we should keep reporting these, daily, until the IE team wakes up to web standards and decides to support them.
Then, webmasters can make one version of the website that works in all modern browsers.
So what if it's a beta? (Score:2, Informative)
Nasty security flaw that Microsoft missed (Score:4, Insightful)
An attacker could exploit the flaw by crafting a special Web page that could be used to crash the browser or gain complete control of a vulnerable system
So, this is actually a relevant article, despite its initial appearance.
We've got some new additions and enhancements to IE, and here we have a flaw that can give an attacker complete control over the user's computer!
I guess this is a taste of things to come in Vista? Evidence that Microsoft's secure code development practices are mostly just verbal pacification?
Re:Nasty security flaw that Microsoft missed (Score:2, Insightful)
Actually you don't. There's a flaw that can crash the browser, but the reporter of this offers no proof that it will result in code execution or the ability to take over a user's computer. Very few buffer overruns result in code execution, and without proof, it's just another crash.
Looking at how the reported went public before the vendor has a chance to respon
Re:Nasty security flaw that Microsoft missed (Score:4, Interesting)
Fairly official response [msdn.com] (taken from another comment).
So it appears that Microsoft's new development practices caught this bug internally before it was caught in the public beta, to find bugs like this. It also seems that the overrun is caught and dealt with (causing a crash as overruns should, but not allowing any degree of "control") by the system they are using for development anyway. Apparently the original article has not proven that the bug could be exploited at all yet anyway, so a response from his end will be required before this can really be seen as anything other than the sort of thing that's to be expected from a beta release.
Parent
Error in article... (Score:3, Funny)
Not so - they tried to post a reply on his site but their browser kept crashing.
Using beta for banking (Score:3, Informative)
I don't just mean IE either. Firefox in it's pre 1.0 days had a bug where tabs could read form data from other tabs. Like credit card numbers. All the way up to 1.0.
Why aren't beta's being released with some sort of self-setting desktop wallpaper that says "Look dipshit this is a beta product, and not like Google Beta TM, like buggy beta, so spare a seconds thought before you go doing your finances".
In next weeks news: some stupid fuck loses his identity and $20000 minutes after using IE7 Beta to pay his bills, therefore IE7 is bad.
MSIE 7 in the wild (Score:4, Interesting)
The Acid 2 CSS Test (Score:3, Insightful)
From the IE Team Blog (Score:4, Insightful)
I'm sorry, but I take issue with this, particularly with a product being beta-tested, but really, with any product. Users need to know what exploits are known. If there are serious, known, security flaws in IE, that may very well affect my decision of whether or not I want to install it on my system. THe idea of keeping it hush-hush doesn't really help anyone.
Gee, its BETA SOFTWARE! (Score:3, Insightful)
1) NOBODY is forcing you to install a beta product. If you are curious or impulsive, and feel compelled to install beta software, your doing so at great risk to your security and data. Whether it's Microsoft beta's, Google beta's, or Linux Beta's, you are accepting that risk by the nature of installing beta software (its in the disclaimer)
2) THE REASON for beta software is to open it up to wider testing to CATCH AND FIX Bugs. This is a good thing, that bugs are flowing back to Microsoft. It will force them to fix the bugs and strengthen the product.
3) No, you CAN'T Sue, see 1)
4) Get a life. I mean, if IE 7 was in full release and these bugs were being reported, I would jump on the bandwagon myself and fire a few shots at MS, but this is still beta software, it isn't even a release candidate yet. Its intended for people with a brain to install it at their own risk and test the product, to REPORT bugs is the definition of what Beta software is. Obviously lots of stupid people are installing IE 7!
This is NOT NEWS, this is sad. To report and complain that Microsoft's beta software is full of bugs suggest a complete bias, prejudice, and ignorance towards them without merit or provocation. This is not microsoft screwing up, this is microsoft doing what countless other software companies do, release a beta in order to get feedback and bug reporting in order to fix and strengthen the product.
When FireFox 1.5 beta was released, it was full of bugs, but people praised Mozilla for their innovation and success. I can't stand double standards.
XHTML support (Score:4, Informative)
Not so fast.... (Score:2, Informative)
Re:Microsoft Beta Crap (Score:2)
My my my, how's that possible, that the preview release of a beta version could be less stable as a software released 5 years ago is unheard of, i'd suggest you to sue Microsoft.
Re:Note: Its BETA (Score:2, Insightful)
There you go, I corrected it for you. (no karma bonus checked for all those Gzealots)
Re:Ahh... what a relief... (Score:4, Funny)
Right?
Parent