Md5 actually harmful
You probably shouldn't take any other view of this vulnerability into consideration. Some amazing research and dedication went into proving this vulnerability is realistic and viable. You should note that detection of it is not really feasible; the bad certs look exactly like
The vuln before Christmas
* T'was the night before Christmas, and all through the net, * not a hacker was stirring, not even FX, * the servers all hummed in post-purchase daze, * to await the deluge of gift-card traffic craze, * * The VRT was drinking, three sheets to the wi
SPAN, The Heap, and esoteric memory buggery…
Have you ever heard someone say they needed a pointer that pointed to itself and was also a nop? Maybe one they could write to? No? Where are you hanging out? For the rest of you, I'll explain why this set of properties can be useful, and when you might want to make use of
Advanced Windows Buffer Overflow 5
Time for more pain. I like this one. It'll be different than the last few, and might involve a bit of a brain stretch for those not familiar with exploit techniques that differ from the norm. It'll hurt. There's a bit of basic reversing, but that's not the proble
AWBO4!
Some of you tore through awbo3 pretty quickly, but I wanted to give others time to catch up before posting this one. We're going to start getting into some issues you'll see in live software when working on exploits. This one in particular might remind you of a certain ba
AWBO Part Deux
Since some people have been chomping at the bit for the next challenge, so here it is. The same rules apply as did last time. When we say no static stack return addresses, this also means of course that there's no need for NOP sleds, so I shouldn't see them in solutions.