How To: The Art of 0-Day Vulnerabilities, Part 1: STATIC ANALYSIS

The Art of 0-Day Vulnerabilities, Part 1: STATIC ANALYSIS

The Art of 0-Day Vulnerabilities, Part 1: STATIC ANALYSIS


Hello my masters and colleagues, first of all I would like to apologize for my absence during the past month, to say that i was busy with some projects and decide to leave the white-side for a while and made some visits on the dark-side(every good COP has a dealer friend),i left null byte last month to learn more and come here to share with you ... I spent almost the whole last month trying to practice my knowledge, and there were moments where the systems were well protected, not that they were impossible to be hacked but hard or complicated, so I decided to start investigating deeply the functioning of these systems to see if I could find flaws instead of simple scans with some tools, I began by analyzing the code of applications in the case of open source , sending abnormal data and more, and in the end most were hacked and still others are in process.

btw gr33tz t0 :Ciuffy ghost_ Phoenix750 f0r the gr3at j0b


According to wikipedia a zero-day (also known as zero-hour or 0-day) vulnerability is an undisclosed and uncorrected computer application vulnerability that could be exploited to adversely affect the computer programs, data, additional computers or a network.1 It is known as a "zero-day" because once a flaw becomes known, the programmer or developer has zero days (before disclosure) to fix it.

If you can find a flaw that the software authores do not know aobut "bingo" you got the gold.

The proccess

1-Responsible disclosure
contact the sellers and give them time to fix(you can set a time limit before you put it public)

2-full disclosure
go public with technical details of the bug without first giving the vendor an opportunity to fix it

As a white-hat you have the obligation to use the responsible disclousure some might give you money while others just greetings, but for black-hat guys some spread the vulnerabilities in some forums, use the vulnerabilities for their own benefits and more, I have personally seen exchanging vulnerabilities between black-hat guys and so on.


There are a lot of way to find a 0 day vulnerability, i will show you some of the most common ways to do it.

1-Open source or when you have access to the source code

1.1-Manual code review

when you have access to the source code its pretty much easier, what you can do is manual code review depending on which language it was made, here you need some programming skills in order to understand the code and find possible flaws

1.2- static analysis
depending on the plataform which you are working with you can find a tool to automatically analyse the code.
here is a good list of them
my reconmendations:
its always good to combine all of them because they will produce different coverage

2-No access to the source code

2.1-Reverse enginnering

also called back engineering, is the processes of extracting knowledge or design information from anything man-made and re-producing it or reproducing anything based on the extracted information. The process often involves disassembling something and analyzing its components and workings in detail.

2.2-Binary static analysis
tool that i used recently

2.3 fuzzing "do random testing"

fuzzing is the art of inputing unexpected data in order to uncover unexpected behavior, fuzzing is often used to find vulnerabilities..

an example of that are the famous sql injections:
ADMIN' OR 1=1#

using one of these tests above as username and password in some weak web forms can bypass the password authentication giving you the power to find a 0day sql injection.

$ip = getip();
$tablename = $wpdb->prefix."limitlogin";
$tablerows = $wpdb->get
results( "SELECT `loginid`,
ip`,`loginattempts`,`attempttime`,`lockedtime` FROM `$tablename`
WHERE `login
ip` = '$ip' ORDER BY `loginid` DESC LIMIT 1 " );

function getip(){
if (!empty($SERVER'HTTP_CLIENT_IP')) {
} elseif (!empty($
} else {
$ip = $
$ip = '';
return $ip;

as example i will leave here this part of code that contains a vulnerability i know, its php and mysql, i hope you can find a 0 day vulnerability on it and leave it in comments.

for now thats all soon i will be going through all the ways we can find 0 days bugs and specific bugs for specific plataform..keep coming and dont forget to greet me if you find a 0 day vulnerability..



Great contribution! I'm looking forward to this series!

Yeah, I'm gonna like this series.

Also, you might want to check that $ip before returning... as headers can be forged and $ip is not sanitized before inserting in the query ;)

you are right..thats the most common bugs on php codes that can lead us to finding some sql injections on systems, actually thats a peace of code of the WP Limit Login Attempts plugin, they had an sql injection vulnerability, and now you see how easy could be for you to find a 0 day vulnerability, coz the key here is to explore and be patient, most of this plugins can be downloaded for free, so you can have the access to the source code and do some statics analysis. and i guess you know how popular this plugin is, you can imagine the impact of this 0 day vulnerability..


ikr... I think that's 0day no more, now $ip is escaped with esc_sql() while IMHO it should be validated as an IP, for data integrity.

But that's not the most juicy 0day you can get... best ones come from leaked C&C source. There are often similar bugs in the code (or shall I call them backdoors?) that allow complete network takeover.

Bug hunting is a funny game, you always catch something...

hahaha i know its not 0 day anymore..that was just to show the idea to those readers with no such a big background on how it works, and sure this aint the most juicy 0day, its just a simple sql injection but using this bug you might be able to upload a shell on server and take control over the server.. and personally my favorite 0 days is a buffer overflow when i can run RCE.. but cool i will be showing how to get some other vulnerabilities soon..


Yeah someone could have fun making a weaponized exploit out of the information we provided... he just needs to take out the sql_esc() function and try it out... for educational purpose ofc.

Bring it on with vulnerabilities !

Wow,I know cppcheck now.
I think perhaps I will download it later.
Good! +1

cool article, can't wait for more :)

Share Your Thoughts

  • Hot
  • Latest