4 ms·
I found CVE-2010-0539 (Safari remote code execution) by setting up a website that just fuzzed a ton of stuff. It had a meta-refresh setup so the browser would j
by fintler 12y ago
I found CVE-2010-0539 (Safari remote code execution) by setting up a website that just fuzzed a ton of stuff. It had a meta-refresh setup so the browser would just keep reloading with a new random fuzz payload. I was in my 2nd year of a CS undergrad program, so I would do stuff like this when I was bored.
I think much of it is just a bit of luck that you're looking in the right place.
- highschooler 12y agoCan I ask what exactly you where watching for with your fuzzer? Where you just waiting for Safari to crash? Then what?
- tracker1 12y agoWhat's funny, is back in the mid-late 90's, I found a lot of bugs in Netscape Navigator simply by running the browser in a more secure OS (Windows NT) vs. Windows 9x... There were a lot of conditions where the browser would crash in NT, but in 9x meant you had an exploit. Many of those were pretty simplistic... fortunately for almost everyone at the time, the browser wasn't a widely used method of exploit, and to my knowledge compromising distributed computer networks via such compromises and ad networks wasn't thought of either. Though by 2002/2003, I had started blocking Flash, Java and Adobe Reader at home when I saw what could be done in the browser.