OWASP LAPSE Project

=Main=



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

OWASP XXX
OWASP XXX is...

Introduction
Write a short introduction

Description
Write a description that is just a few paragraphs long

Licensing
OWASP XXX is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.


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

What is XXX?
OWASP XXX provides:


 * xxx
 * xxx

Presentation
Link to presentation

Project Leader
Project leader's name

Related Projects

 * OWASP_CISO_Survey


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

Quick Download

 * Link to page/download

News and Events

 * [20 Nov 2013] News 2
 * [30 Sep 2013] News 1

In Print
This project can be purchased as a print on demand book from Lulu.com

Classifications

 * }

=FAQs=


 * Q1
 * A1


 * Q2
 * A2

= Acknowledgements =

Volunteers
XXX is developed by a worldwide team of volunteers. The primary contributors to date have been:


 * xxx
 * xxx

Others

 * xxx
 * xxx

= Road Map and Getting Involved = As of XXX, the priorities are:
 * xxx
 * xxx
 * xxx

Involvement in the development and promotion of XXX is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
 * xxx
 * xxx

=Project About=

Main
LAPSE+: The Security Scanner for Java EE Applications

News

 * 4/15/2011 - LAPSE+ released.
 * 8/23/2006 - LAPSE 2.5.5 released.
 * 8/22/2006 - OWASP LAPSE Project Created.

Overview
OWASP LAPSE Project is an initiative to make available to developers and auditors a tool for detecting vulnerabilities in Java EE Applications. The project aims to put at their disposal a tool based on the static analysis of code, due to the importance and difficulty of this type of analysis to detect security flaws in Java EE Applications. The difficulty of this analysis increases when they face applications consisting of thousands of lines of code or having a complex structure with many Java classes. Hence, OWASP LAPSE Project offers a tool that helps the developer and auditor to carry out the static analysis of code in the most effective and efficient way. The tool that is provided and gives the name to the project is LAPSE+.

LAPSE+ is a security scanner for detecting vulnerabilities of untrusted data injection in Java EE Applications. It has been developed as a plugin for Eclipse Java Development Environment, working specifically with Eclipse Helios and Java 1.6 or higher. LAPSE+ is based on the GPL software LAPSE, developed by Benjamin Livshits as part of the Griffin Software Security Project. This new release of the plugin developed by Evalues Lab of Universidad Carlos III de Madrid provides more features to analyze the propagation of the malicious data through the application and includes the identification of new vulnerabilities.

LAPSE+ is based on the static analysis of code to detect the source and the sink of a vulnerability. The source of a vulnerability refers to the injection of untrusted data, e.g. in the parameters of an HTTP request or a Cookie. The sink of a vulnerability refers to the process of data modification to manipulate the behaviour of the application, such as a servlet response or a HTML page. The vulnerability sources can lead to sinks by simple assignments, method calls or parameters passing. When it is possible to reach a vulnerability sink from a vulnerability source then we have a vulnerability in our application.



The vulnerabilities detected by LAPSE+ are related to the injection of untrusted data to manipulate the behavior of the application. This type of vulnerabilities are the most common in web applications. The vulnerability categories detected by LAPSE+ are enumerated below:


 * Parameter Tampering.
 * URL Tampering.
 * Header Manipulation.
 * Cookie Poisoning.
 * SQL Injection.
 * Cross-site Scripting (XSS).
 * HTTP Response Splitting.
 * Command Injection.
 * Path Traversal.
 * XPath Injection.
 * XML Injection.
 * LDAP Injection.

Three steps are needed in LAPSE+ for the detection of this kind of vulnerabilities:


 * Vulnerability Source. The first step involves the detection of the points of code that can be source of an attack of untrusted data injection.
 * Vulnerability Sink. After detecting the points of code that can be target of data injection, LAPSE+ identifies the points that can propagate the attack and manipulate the behaviour of the application.
 * Provenance Tracker. Finally, we check if it is possible to reach a Vulnerability Source from a Vulnerability Sink performing the backward propagation through the different assignations. If this occurs, we have a security vulnerability in our code.

Question: What should you do to avoid these vulnerabilities in your code? - How do we protect Web applications from exploits?

Answer: The proper way to deal with these types of attacks is by sanitizing the tainted input. Please refer to the OWASP Guide to find out more about Web Application Security.

LAPSE+ is inspired by existing lightweight security auditing tools such as FlawFinder. Unlike this tool, however, LAPSE+ addresses vulnerabilities in Web Applications. LAPSE+ is not intended as a comprehensive solution for Web Application Security, but rather as an aid in the code review process. Those looking for more comprehensive tools are encouraged to look at some of the tools produced by Fortify or Ounce Labs.

Download
LAPSE+ can be downloaded at http://evalues.es/?q=node/14

Feedback and Participation:
We hope you find the OWASP LAPSE Project useful. Please contribute to the Project by volunteering for one of the Tasks, sending your comments, questions, and suggestions to owasp@owasp.org. To join the OWASP LAPSE Project mailing list or view the archives, please visit the subscription page.