Windows MHTML Vulnerability Warning From Microsoft 49
jhernik writes "An HTML scripting bug impacting all supported versions of Windows is receiving Microsoft's attention Microsoft issued an advisory on a Windows security vulnerability today after exploit code for the bug went public. The bug, which lies in the MIME Encapsulation of Aggregate HTML (MHTML) protocol handler, can be exploited to cause data leakage. Though proof-of-concept code for the vulnerability has already gone public, the company said it is unaware of any attempts to exploit the bug." This might seem familiar to you, but considering how many times I saw it submitted this morning, it probably doesn't ;)
Dupe (Score:2, Informative)
http://tech.slashdot.org/story/11/01/29/0050223/New-Critical-Bug-In-All-Current-Windows-Versions [slashdot.org]
Re: (Score:2)
http://tech.slashdot.org/story/11/01/29/0050223/New-Critical-Bug-In-All-Current-Windows-Versions [slashdot.org]
The fact that it's a dupe is actually mentioned right in the summary...
Re: (Score:2)
The fact that it's a dupe is actually mentioned right in the summary...
I think it was added after the original story, because I don't remember it being there a few minutes ago.
Re: (Score:1)
You are correct. It was a silent, unmarked edit. Design may have changed, but editor behavior hasn't.
Re: (Score:2)
Re: (Score:2)
If it's actually your job to know this, you had better not be depending on Commander Taco to keep you informed.
Posted just after /.'s changeover to new version. (Score:2)
That was posted last Friday. I suspect a lot of people didn't see it because slashdot had recently changed to the new format that is virtually unreadable on older browsers - or even recent Firefox versions.
I notice that things are substantially better today, at least for the older firefox 2.0.0.8. Maybe they got fixed up enough that more people will see this posting.
Can't make a gorilla change its spots. (Score:1)
So, what have we learned in 2010? MS will deny the existence of a bug, at the very least until proof-of-concept is published; afterwards, they'll downplay it by saying "it's not really critical at all, but you should update ASAP because, uh, eh, well, the stars are right or something, but definitely not critical, nosir, not at all". In other words, same old, same old. Nothing to see here, move along.
Feature (Score:1)
Re: (Score:1, Troll)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Ah well. Not every day you can be accused of shilling for Bill for a comment made from Konqueror running on a remote debian host over an ssh -X tunnel...
Re: (Score:2)
I'll fess up and say I modded too hastily, immediately realized I was wrong and am posting to undo.
Would be nice to be able to undo an individual mistaken mod (say within a couple of minutes), but I'll try to not jump the gun in future.
Here's the MS Fixit link from the original article (Score:4, Informative)
Manual method (vs. Ms FixIt) (Score:2, Informative)
TO APPLY THIS FIX:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_PROTOCOL_LOCKDOWN]
"explorer.exe"=dword:00000001
"iexplore.exe"=dword:00000001
"*"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\RestrictedProtocols]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\RestrictedProtocols\1]
"mhtml"="mhtml"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Re:Manual method (vs. Ms FixIt) (Score:4, Insightful)
I'm going to edit my registry based on the word of AC. Seems like a reliable source.
Re: (Score:1)
So what you're saying is, you copied & pasted code from the MSDN website (which has "© 2011 Microsoft Corporation. All rights reserved." printed at the bottom) without citing the source of the information that you ripped from it.
Isn't that called plagiarism?
Re: (Score:2)
Please link to some proof that you are who you say you are, and you have done what you say you have done. For all anyone knows you are a random person claiming the initials APK and claiming that you have done oh so much. In reality, it is difficult for you to prove anything seeing as you aren't even logged in so if multiple people were posting the same way, there's no way to know the difference.
If you are as knowledgeable as you claim to be, then you would know that it is stupid to follow the instructions o
Useless features. (Score:1)
MHTML is HTML in a MIME container (Score:3)
Are you at risk if you use an "alternate" browser? (Score:2)
Are you at risk if you use an alternate web browser like Firefox, Opera, or Chrome?
Re: (Score:2)
Re: (Score:1)
Chrome seems to just render a blank document for mhtml: urls, and doesn't let you enter them in the omnibox directly... Firefox gets confused and thinks mhtml: is not associated with any application
Yeah. Probably because "mhtml" isn't a valid URL protocol, according to HKEY_CLASSES_ROOT.
"My Computer\HKEY_CLASSES_ROOT\mhtml" doesn't exist.
"My Computer\HKEY_CLASSES_ROOT\mhtmlfile" exists, but it doesn't have the "URL Protocol" REG_SZ flag set.
Here we have yet another example of Internet Explorer / Windows doing things in non-standard ways and breaking everything else. The MSDN Library even has a how-to page describing how to register an application to a URL protocol [microsoft.com]...
For instance, to add an "alert:" protocol, add an alert key to HKEY_CLASSES_ROOT, as follows [...] Under this new key, the URL Protocol string value indicates that this key declares a custom protocol handler. Without this key, the handler application will not launch. [...]
HKEY_CLASSES_ROOT
alert
(Default) = "URL:Alert Protocol"
URL Protocol = ""
DefaultIcon
(Default) = "alert.exe,1"
shell
open
command
(Default) = "C:\Program Files\Alert\alert.exe" "%1"quote>
Re:Are you at risk if you use an "alternate" brows (Score:4, Informative)
Opera has fixed this. Firefox crashes. I would hope Chrome has fixed it because Google is the company that discovered the problem.
Re: (Score:1)
Firefox does not "crash". It pops up an alert message which reads as follows:
Firefox doesn't know how to open this address, because the protocol (mhtml) isn't associated with any program.
...which it isn't. Go check HKEY_CLASSES_ROOT...
Re: (Score:2)
So wait, it affected Opera as well? Is it because it used some IE bits to handle MHTML, or because any naive implementation of it is prone to that bug?
Re: (Score:1)