
The first step is to turn on pageheap and user mode stack tracing for iexplore.exe using gflags. We begin with this, which should give us a crash that looks something like the following: When installing, make sure you disconnect the internet connection so it doesn’t update, which it will do otherwise. I got the vulnerable version of IE from this totally legit looking site.
#Tcp gecko net crash install
Install a windows xpsp3 VM without updates. I’m a noob in this space so please call out/forgive mistakes.
#Tcp gecko net crash free
I’ve been spending some free time over the past month looking into use after free type bugs. Although there are a million posts about the class of bug, not many are hands on (and this one is). This is an introductory post to use after free – walking through an exploit.

#Tcp gecko net crash code
In various scenarios, attackers can influence the values in that memory, and code at a later point will use it with a broken reference. |_SHA-1: b865 1880 79d6 56bd e876 7006 ece0 f1fd a1bf 551eĪ use after free bug is when an application uses memory (usually on the heap) after it has been freed. You can run it like this, and use any of the output that nmap does, so it’s simple to parse out. return shortport.ssl(host, port) or sslcert.isPortSupported(port) In that case you can just return true regardless of port. I couldn’t find a command line switch to force nmap to run a script on a port, but it’s easy enough to edit the scripts themselves. It turns out it’s already there with ssl-cert. With our python script, it was also slow.Īnyway after the engagement I was thinking about writing this up as an NSE and looked more carefully at the existing nmap scripts.

This is a good way to guess at internal hostnames.

We had some time pressure, so we looked to see if nmap had a script (we didn’t see one) and wrote a python script that grabbed the cert names. We recently had a red team where we had a lot of RDP endpoints, but not many other endpoints.
