Everything, Everything

2024: J F M A M J J A S O N
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
Microsoft
Friday 2nd June, 2006 09:14 Comments: 0
Nice to see they\'re doing something right. A vulnerability has been found in IE (shocking, I know) that will make the browser crash when you click on it. It looks like it's a stack overflow in inetconn.dll, but it's most likely not exploitable because the DLL is compiled with /GS. There are no other interesting variables to overwrite between the buffer and the return address. It would probably be exploitable on older systems not compiled with /GS, but the code was added in XP SP2. Not only that, but it looks like it's already been fixed in IE7 (7.0.5346.5 on XP is apparently not vulnerable). It's bad that you can crash the browser, but it's good that it doesn\'t look like it can be used maliciously. Now if only they could sort out the memory leaks in IE7 Beta.
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3