Full Disclosure mailing list archives
Re: MSIE (mshtml.dll) OBJECT tag vulnerability
From: "Aaron Gray" <angray () beeb net>
Date: Fri, 28 Apr 2006 20:47:41 +0100
My $0.02, ignore as you see fit. As a consumer, I prefer (arguably have the right) to know at the earliest possible opportunity whether a product I am using is flawed. Whether a medication appears to cause cancer, my car is prone to exploding when rear ended, or a piece of software is found to be exploitable. I don't wish towait through some potentially lengthy process, legal or otherwise, in whichthe producer of the product denies or downplays the severity of the flaw before finally addressing the problem and making the flaw public before Ihear about it for the first time. To pretend that you are somehow immune tothe problem while the vendor fails to disclose it is simply ridiculous.While vendor coordination is certainly nice to have, the ONLY thing I wouldlike to see required in pre-patch disclosures are constructive ways to mitigate the problem, and the impact of those mitigations.For those that would not disclose, what gives you the right to judge whethersomeone is capable of dealing or not dealing with the newly announcedvulnerability, and what makes you think that you are qualified to manage the risk on my networks? If you are an information security professional, then you are paid to deal with "problem", if you are not capable of dealing withit, then you need to rethink your profession. Flame away,
The only thing that I would add that ehat in an idea world firstly on finding a vulnerability that an advisory is made to the product producer then secondly to the list with an IDS fingerprint SNORT. Then not until a reasonable time to fix the vulnerability the proof of concept exploit is released (This gives time to hone the exploit as well :)
My 0.02 cents added, Aaron _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability, (continued)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability str0ke (Apr 27)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability poo (Apr 27)
- Re[2]: MSIE (mshtml.dll) OBJECT tag vulnerability Thierry Zoller (Apr 27)
- RE: MSIE (mshtml.dll) OBJECT tag vulnerability Tim Bilbro (Apr 27)
- RE: MSIE (mshtml.dll) OBJECT tag vulnerability Michal Zalewski (Apr 27)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Brian Eaton (Apr 27)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Michal Zalewski (Apr 27)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Peter Besenbruch (Apr 28)
- RE: MSIE (mshtml.dll) OBJECT tag vulnerability Chris Eagle (Apr 28)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Sol Invictus (Apr 28)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Aaron Gray (Apr 28)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Valdis . Kletnieks (Apr 28)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Aaron Gray (Apr 28)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Aaron Gray (Apr 28)
- RE: MSIE (mshtml.dll) OBJECT tag vulnerability Michal Zalewski (Apr 27)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Tim (Apr 27)
- Re: MSIE (mshtml.dll) OBJECT tag vulnerability Sol Invictus (Apr 28)
