View source for OWASP WAP-Web Application Protection

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |

<!--
<span style="color:#ff0000">
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
</span>
-->
==OWASP WAP - Web Application Protection Project==
WAP is a tool to detect and correct input validation vulnerabilities in web applications written in PHP and predicts false positives. The tool combines source code static analysis and data mining to detect vulnerabilities and predict false positives. Then, corrects the source code to remove the real vulnerabilities inserting fixes (small functions) in the right places of the source e code.

==Introduction==
* OWASP WAP is a security tool to detect and remove input validation vulnerabilities in web applications, and predict false positives.
* Uses source code static analysis to detect vulnerabilities, data mining to predict false positives and inserts fixes to correct the source code.
* Detects and corrects 8 types of input validation vulnerabilities.
* Teaches the user to build secure software.
* Works on Linux, Macintosh and Windows.
* Requires JRE to run.
* Portable, ready to run and no installation required.

==Description==
<!--
<span style="color:#ff0000">
	This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful.  
</span>
-->
WAP is a source code static analysis and data mining tool to detect and correct input validation vulnerabilities in web applications written in PHP (version 4.0 or higher) with a low rate of false positives.

WAP detects and corrects the following vulnerabilities:
* SQL Injection (SQLI)
* Cross-site scripting (XSS)
* Remote File Inclusion (RFI)
* Local File Inclusion (LFI)
* Directory Traversal or Path Traversal (DT/PT)
* Source Code Disclosure (SCD)
* OS Command Injection (OSCI)
* PHP Code Injection

This tool semantically analyses the source code. More precisely, it does taint analysis (data-flow analysis) to detect the input validation vulnerabilities. The aim of the taint analysis is to track malicious inputs inserted by entry points ($_GET, $_POST arrays) and to verify if they reach some sensitive sink (PHP functions that can be exploited by malicious input, such as mysql_query). After the detection, the tool uses data mining to confirm if the vulnerabilities are real or false positives. At the end, the real vulnerabilities are corrected by the insertion of the fixes (small pieces of code) in the source code.


WAP is constituted by three modules:
* Code Analyzer: composed by tree generator and taint analyser. The tool has integrated a lexer and a parser generated by ANTLR, and based in a grammar and a tree grammar written to PHP language. The tree generator uses the lexer and the parser to build the AST (Abstract Sintatic Tree) to each PHP file. The taint analyzer performs the taint analysis navigating through the AST to detect potentials vulnerabilities.

* False Positives Predictor: composed by a supervised trained data set with instances classified as being vulnerabilities and false positives and by the Logistic Regression machine learning algorithm. For each potential vulnerability detected by code analyser, this module collects the presence of the attributes that define a false positive and creates with them an instance. Then, the Logistic Regression algorithm receives the instances and classifies them as being a false positive or not (real vulnerability).

* Code Corrector: each real vulnerability is removed by correction of its source code. This module for the type of vulnerability selects the fix that removes the vulnerability and signalizes the places in the source code where the fix will be inserted. Then, the code is corrected with the insertion of the fixes and new files are created. Fixes are small pieces of the code (user functions) that performing sanitization or validation of the user inputs, depending of the vulnerability type.

==Licensing==


This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.    

| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
<!--
<span style="color:#ff0000">
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. 
</span>
-->
[http://awap.sourceforge.net http://awap.sourceforge.net]
<!-- [http://sourceforge.net/projects/awap/ http://sourceforge.net/projects/awap/] -->

== Project Leader ==
[[User:iberiam| Ibéria Medeiros]]<br/>
<!--
[mailto:ibemed@gmail.com Email]<br/>
[https://sites.google.com/site/ibemed/ Homepage]
-->

== Related Projects ==
<!--
<span style="color:#ff0000">
	This is where you can link to other OWASP Projects that are similar to yours. 
</span>
-->

==Classifications==

   {| width="200" cellpadding="2"
   |-
   | colspan="2" align="center"  | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]
   |-
   | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]  
   |-
   | align="center" valign="top" width="50%"| [[File:Owasp-breakers-small.png|link=Breakers]]
   |-
   | colspan="2" align="center"  | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
   |}

| valign="top"  style="padding-left:25px;width:200px;" | 

== News and Events ==
<!--
<span style="color:#ff0000">
	This is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project. 
</span>
-->
|}

=FAQs=

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<!--
<span style="color:#ff0000">
	Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
</span>
-->

None, for now...

= Acknowledgements =
==Contributors==
OWASP WAP - Web Application Protection is brought to you by OWASP, a free and open software security community focusing on improving the security of software. Our goal with OWASP WAP project is to build secure software, by the detection of web application vulnerabilities and removing of them by the correction of web application source code. 
<br/><br/>
OWASP WAP - Web Application Protection project is led by [[user:iberiam| Ibéria Medeiros]], a software security developer and enthusiast.

==Volunteers==
The project is free and open source, and if you want to join to the development team, please contact the project leader by sending her an [mailto:ibemed@gmail.com email].

<!--
==Others==

* [mailto:ibemed@gmail.com Ibéria Medeiros]
-->

= Road Map and Getting Involved =
The main goals are: 
# Demonstrate using the tool that there is a lack of software security in the development of web applications,
# Help programmers learn the need of secure codding practices, which are the practices and how they are implemented. 
# Help programmers learn how to build secure software.
# Become a test bed for analyzing the QoS security of source code of web application.
# Become a tool to teach software security in web application in a class room/lab environment.
# Attract people to extend the WAP tool to detect and correct new types of vulnerabilities,


The phases of development of the WAP tool:
# Build a PHP parser to create an abstract syntax tree (AST). (progress: concluded)
# Detect candidates vulnerabilities using taint analysis under the AST. (progress: concluded)
These two phases can be improved by implementing the new characteristics of the PHP language, such as of object oriented.

# Predict if the candidate vulnerabilities are false positives or not, using for this data mining with a defined training data set. (progress: concluded)
This phase could be modified if the training data set grows vertically and/or horizontally, i.e. more instances are included and/or new attributes that characterize false positives are added to the instances.

# Correct the source code, removing the real vulnerabilities inserting fixes in the right places of the source code. (progress: partially concluded)
This task needs some improvements when the line of the source code occupy more than 1 line.

# Output the results: vulnerabilities found, its correction and the new corrected files; and the false positives predicted. (progress: concluded)

<!--
1. Build a PHP parser to create an abstract syntax tree (AST) (progress: concluded)

2. Detect vulnerabilities using taint analysis under the AST (progress: concluded)
These two phases can be improved by implementing the new characteristics of the PHP language, such as of object oriented.

3. Predict false positives using data mining with a defined training data set (progress: concluded).
This phase could be modified if the training data set grows vertically and/or horizontally, i.e. more instances are included and/or new attributes that characterize false positives are added to the instances.

4. Correct the source code, removing the vulnerabilities inserting fixes in the right places of the source code (progress: partially concluded)
This task needs some improvements when the line of the source code occupy more than 1 line.

5. Output the results: vulnerabilities found, its correction and the new corrected files; and the false positives predicted (progress: concluded)
Additional Comments	 
WAP is a static analysis tool that uses taint analysis to detect vulnerabilities, tracking malicious users inputs and checking if they reach calls of sensitive functions. The tool uses data mining to predict if a vulnerability detected by taint analysis is a false positive or a real vulnerability. The real vulnerabilities are removed by the correction of the source code, inserting fixes (small PHP functions developed to the effect) in the right places in the source code. 
The tool outputs: the vulnerabilities found and how they are corrected and the new files with the corrections; reports the false positives predicted.
WAP detects the following vulnerabilities:
- SQL injection using MySQL, PostgreSQL and DB2 DBMS
- Reflected cross-site scripting (XSS)
- Stored XSS
- Remote file inclusion
- Local file inclusion
- Directory traversal
- Source code disclosure
- OS command injection
- PHP code injection
-->



==Getting Involved==
Involvement in the development and promotion of OWASP WAP is actively encouraged!
You do not have to be a security expert in order to contribute. 
Some of the ways you can help:
* Spread the word - Facebook, Twitter, Google+ or any other communication platform.
* Write about OWASP WAP on your web site, book or blog.
* Make tutorials/videos of WAP tool in languages you know of.
* Include it in your training materials, talks, laboratories etc.

===Coding===
You can also help if you wish to extend the WAP tool with a new module or even improving some part(s) of it.

===Feedback===
Feedback should be sent to the project leader by sending her an [mailto:ibemed@gmail.com email].

=Download=
<br/>
The delivery of the project is a zip or tar.gz file containing:
* a jar file with the WAP tool;
* plain text file with the indications how to install and use the tool;
* vulnerable PHP example files to demonstrate how to work the tool; 
* the source code of the tool.


The tool works in different operating systems -- Linux, OSx and Windows -- and is available at [http://awap.sourceforge.net http://awap.sourceforge.net]

The requirements to run the tool are only the JRE (Java Runtime Enviroment), which can be downloaded at [http://www.oracle.com/us/downloads/index.html#menu-downloads http://www.oracle.com]. No installation required.


__NOTOC__ <headertabs /> 

[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]