[The security hole allows for] full blown remote code execution, ... If a user browses to a bad Web site, malicious software can be installed on their PC without their knowledge.
I am walking a fine line, but I am doing it very carefully because I am not disclosing actual vulnerability details, ... I do this to inform users that flaws still do exist in IE...I don't like it that Microsoft tries to give users a nice warm feeling that they are disclosing everything researchers report to them.
I have been e-mailed a couple of times by people asking for an exploit. This tells me the Trojan writers are out there looking for something.
I'm guessing they are working on a patch. Who knows, though?
It's a pretty nasty flaw.
It's not like any other flaw in IE?it's definitely different.
Microsoft obviously takes way too long to fix flaws, ... All researchers should follow responsible disclosure guidelines, but if a vendor like Microsoft takes six months to a year to fix a flaw, a researcher has every right to release the details.
The reason I released the [proof of concept] is so that other researchers like myself can check out the bug, and maybe there is possibly a variant of this flaw that can be exploited.
Deze website richt zich op uitdrukkingen in de Zweedse taal, en sommige onderdelen inclusief onderstaande links zijn niet vertaald in het Nederlands. Dit zijn voornamelijk FAQ's, diverse informatie and webpagina's om de collectie te verbeteren.
Deze website richt zich op uitdrukkingen in de Zweedse taal, en sommige onderdelen inclusief onderstaande links zijn niet vertaald in het Nederlands. Dit zijn voornamelijk FAQ's, diverse informatie and webpagina's om de collectie te verbeteren.