******Job Left-1: Need to find a way to link between the output file and the Safe Library.The safe library is named as "SafeLib.h".Here The SafeLib file is not complete.So we need to find a way to complete the SafeLib file and link it to the scanner for better performance.In the grammar file named as "y.y",we have included SafeLib.h but its not using the library.Please check the SafeLib.h file to see if there is any way to link it to the y.y file.Some pages from the Thesis

*****Job Left-2: Scanning the cpp (C++ source code) also not properly functioning. We need to find a way so that scanner can scan C++ codes also. And based on the paper this scanner can scan cpp file.Probably the problem is the way I m compiling here.So I need to create another file with cpp extension where function wrapper can work and then using g++ to compile them all together into a complete scanner can scan c and c++ files.I have uploaded a test-input.cpp file which our scanner fails to scan but in paper it scanned properly and showed the warnings,So I still have to find the properway to compile these codes

***** Job Left-3: Most of the Warning messages have been fixed, even the re-write process is working. But we still have to find a way for the less amount of false positives and false negatives. Probably need to test more vulnerable files.

WE ARE DOING THIS PROJECT based on the paper "A new approach for testing buffer overflow vulnerabilities in C and C++" by Alouneh, Sahel A"This is the Scanner Architecture

PLEASE FOLLOW THIS LINK BELOW IF YOU WANT TO COMPILE THE SCANNER IN THE WINDOWS OS. IN LINUX FLEX,BISON AND GCC COMES WITH THE SYSTEM SO U DONT NEED TO INSTALL ANYTHING.

http://stackoverflow.com/questions/5456011/how-to-compile-lex-yacc-files-on-windows

First Use the FLEX tool to compile *.l file, Here it is l.l,the lexical file

$ flex l.l

then Use the BISON tool to compile *.y file, Here it is y.y,the parser file (this file is the heart of the program)

$ bison -dy y.y (if u type bison --help,you can see,bison manual,normally we r using -dy ,but not sure if we should use some other append)

in the program We r having

14 shift/reduce conflicts

searching in google,we have found out two types of conflicts,shift/reduce and reduce/reduce,normally reduce/reduce is more complicated to resove. Here,shift/reduce conflict is related to the grammar of the y.y file.So,if u type bison -V y.y ,it will create an output file with an *.o extension where u can check which line or grammar is responsible.

In spite of having this conflict we were still able to compile the code,so not yet sure if this conflict is a big issue or not.

finally GCC has been used to compile the final executable file

 g++ y.tab.c lex.yy.c -o test   (i have made some change adding extern C function,but with extern C you cant compile with gcc,so you need to use g++ command)
 gcc lex.yy.c y.tab.c -o test   (here test is the application name)

Now to run the scanner you should

(linux)     ./test input.c output.c warnings.txt
(windows) test.exe input.c output.c warnings.txt

Here "output.c" is the re-writted safer version of the code. Even You can use the text extension instead of c extension.

It means the input.c (it can scan cpp extension too) is the file you want to scan, output.c is the safer version of the code,the scanner will try to produce and the warnings should be the vulnerability function alarm.If you check the y.y file,you can see some printf function containing those warnings.

Our Current Scan Result of Extensions.c from WuFtpd 2.6.2

******Updates: During scanning, we got the message

"error: syntax error in line: 1082 and 1106 please check your function arguments! *** NOW: if you are sure your code is correct, please insert // before your function call in orderto ignore this syntax error"

So We modified line 1082 and 1106 for ignoring syntax error as the image below