Chapter 26. Vulnerability Researcher to Software Developer: The Other Side of the Coin
Larry W. Cashdollar
I’ve been finding vulnerabilities in software since 1999. I’ve reported over 300 vulnerabilities in that time, ranging from format string vulnerabilities to cross-site scripting. I also started developing a web server in C around 1994. The web server has been tweaked, patched, and modified over the years since I started using it to serve traffic to my website in 2002.
My site only served static content, as the HTTP server I developed was much too simple to provide dynamic content. In 2010, one of the top vulnerability and bug curators in the infosec community mentioned that my site should be searchable, and that he’d had trouble finding vulnerabilities I had published while he was building his database. So I added the ability to execute PHP code and put all of my advisories in a MySQL database.
In April 2013, I had the opportunity to put my website behind Akamai’s massive content delivery network (CDN) and enlist some of our security products to help my site. As time passed, I ran into bugs when fixing the code or adding features.
I eventually ran my code through Valgrind and fixed various null pointer dereferences, memory corruption issues, and leaks. I mentioned my Valgrind adventures to my friend, who is a seasoned C developer. He works as a penetration tester and participates ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access