<div id="RTEContent">ad, <br> don't you think it would be a good idea if you either post your PoC with complete details otherwise do not post it. I mean from the "excel_like_hell.swf" demo, I do not see anything that one would infer. <br> <br> I can see that a xls file is created and on opening it (as per the demo), it makes a registry entry. Now how true is this? If you are posting no more info here they how is it going to help us otherwise what was the intent of the post?<br> <br> - Amit<br> <br><br><b><i>"ad@heapoverflow.com" <ad@heapoverflow.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> -----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br> <br>I have got many questions about the severity of the bug , you can show<br>a demo yourself here:<br><br>http://heapoverflow.com/excelol/excel_like_hell.swf<br><br>ms will fixe this issue soon I'm sure, for me , job done, bye
:><br><br>ad@heapoverflow.com wrote:<br>> after many hours working on excel I have found a critical excel bug<br>> exploitable. This is not a stack bof nor a heap bof , a bug<br>> extremely hard to find and trigger , but it conduct excel to<br>> execute any arbitrary codes while opening a malicious .xls file.<br>><br>> note: the bug isn't related to both excel dos that I have already<br>> published but shows similiar to a null pointer bug at a first look.<br>> much infos won't be disclosed publicly or privately and this will<br>> be transmitted to ms before the spyware loosers catch it :)<br>><br>>>> I have said so this is only null pointer bugs but the way I<br>>>> trigger the bug might be modded for a remote code execution who<br>>>> know , I'm not a guru and maybe did an error triggering the<br>>>> flaw who knows :) but I bet many are already reasearching on<br>>>> this hehe, happy
job!<br>><br>><br>><br>>>> Let's go on the fast publishing :) I wont bother to message<br>>>> microsoft about this because they wont patch it for sure<br>>>> according that they can't patch fully exploitable bugs in a<br>>>> decent time, they do not patch IE dos<br>>>> (http://heapoverflow.com/IEcrash.htm), so no way to bother<br>>>> them, we should let them sleep a bit shhh ;)<br>>>><br>>>> Bugs 1 and Bugs 2 are quite similiar but NOT, both are null<br>>>> pointer bugs . In bug1 you should mod a grafic's pointer to<br>>>> point to a bad area, and in bug 2 you should null out the size<br>>>> of the page name.<br>>>><br>>>><br>>>> attached are the 2 pocs, nor here are direct links<br>>>><br>>>><br>>>> http://heapoverflow.com/excelol/bug1.xls<br>>>> <http:><br>>>>
http://heapoverflow.com/excelol/bug2.xls<br>>>> <http:><br>>>><br>>>><br>>>><br>>>> Credits:<br>>>><br>>>> AD [at] heapoverflow.com<br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.2 (MingW32)<br>
<br>iQIVAwUBQ8PL5a+LRXunxpxfAQIHNw/9H6aug9gm0orJmZGIEQ7vGSdDwZkOCLMO<br>Dw7pt6fzDFUKM3HeL3oR2gbQaPUZL57iuuY8NCKEoU3y5hiFm64nlWyGARu3ITW3<br>cuBVUWNpqvZzZbBU4mj9Rc5pG23Y8WrfsNRBAaJWJGjOTHacDsmn5sD0rIdwDXIP<br>pb7pDztp6C4yPkWKN+n/Y5I73M1a8ZI+34VvOSqyMM8eGGTbcnnzF4Uz/f/rhZm9<br>Mm6NBgdQhSOHNqPYz5RjQtrC8O9e8/C3Zekj/YKr1jB3HOa0jiBLDALG7VIQwK/b<br>49e+nUK3FxQ49ygoWSvVwP0+7cFOdOVZ8Ahfd0EVCnyAkxJ04Qa+L9rF0FGSO+M6<br>ljg0ma93De14rHj1O+mQvRpotuUGSWJsfeBSPVLAuODZBmcp7N+AE3E2vKUwGjr5<br>k+FJWHs2fRxCkXb55mic+1aFdWxZvnXDmpJt1t+QTcWDl4OL6/+Ovu/fPWzg2vcQ<br>i25RqdbsfKUnW2/QuoSrPzmgIc8s9UjIwFOj25eR0kUYMwjaugoGaYRMH0NdsSAK<br>MwQJuVGtI4FaKLzYrPQ6m/dOyIqdH0s9cUyXrpNUWByVgMtO+pBSHp9gyCj9lVGs<br>PfHEqYFQX2/xwJQ9QLJz+rCtATzcEjWkN2b79GOm622laRfFI0te/QJa/4BJLncp<br>LGgvT0HVO0k=<br>=smBn<br>-----END PGP SIGNATURE-----<br><br><br>_______________________________________________<br>Full-Disclosure - We believe in it.<br>Charter: http://lists.grok.org.uk/full-disclosure-charter.html<br>Hosted and sponsored by
Secunia - http://secunia.com/<br></http:></http:></blockquote><br></div><p>Send instant messages to your online friends http://in.messenger.yahoo.com