OWASP Dependency Check

=Main=



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

OWASP Dependency-Check
Dependency-Check is a utility that identifies project dependencies and checks if there are any known, publicly disclosed, vulnerabilities. Currently Java and .NET dependencies are supported; however, support for Node.JS, client side JavaScript libraries, etc. is planned. This tool can be part of the solution to the OWASP Top 10 2013 A9 - Using Components with Known Vulnerabilities.

Introduction
The OWASP Top 10 2013 contains a new entry: A9 - Using Components with Known Vulnerabilities. Dependency-check can currently be used to scan Java applications (and their dependent libraries) to identify any known vulnerable components.

The problem with using known vulnerable components was described very well in a paper by Jeff Williams and Arshan Dabirsiaghi titled, "The Unfortunate Reality of Insecure Libraries". The gist of the paper is that we as a development community include third party libraries in our applications that contain well known published vulnerabilities (such as those at the National Vulnerability Database).

Dependency-check has a command line interface, a Maven plugin, an Ant task, and a Jenkins plugin. The core engine contains a series of analyzers that inspect the project dependencies, collect pieces of information about the dependencies (referred to as evidence within the tool). The evidence is then used to identify the Common Platform Enumeration (CPE) for the given dependency. If a CPE is identified, a listing of associated Common Vulnerability and Exposure (CVE) entries are listed in a report.

Dependency-check automatically updates itself using the NVD Data Feeds hosted by NIST. IMPORTANT NOTE: The initial download of the data may take ten minutes or more, if you run the tool at least once every seven days only a small XML file needs to be downloaded to keep the local copy of the data current.


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

What is Dependency-Check?
OWASP Dependency-Check provides:


 * Monitoring of project dependencies
 * Library Identification
 * Notification of CVE

Documentation

 * Project Documentation
 * Wiki for developers

Mailing List

 * Subscribe: [mailto:dependency-check+subscribe@googlegroups.com dependency-check+subscribe@googlegroups.com]
 * Post: [mailto:dependency-check@googlegroups.com dependency-check@googlegroups.com]
 * Archive: google group

Presentation

 * dependency-check (PDF)
 * dependency-check (PPTX)


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

Quick Download
Version 1.1.4
 * Command Line
 * Ant Task
 * Maven Plugin
 * Jenkins Plugin

Source Code:
 * github

Ohloh

 * https://www.ohloh.net/p/dependencycheck

Classifications

 * }

= Acknowledgements =

Volunteers
Dependency-Check is developed by a team of volunteers. The primary contributors to date have been:


 * Jeremy Long
 * Steve Springett
 * Will Stranathan

= Road Map and Getting Involved = As of May 2014, the top priorities are:
 * Resolving all open github issues/feature requests
 * Improving analysis for .NET Dlls
 * Implementing a JavaScript analyzer to support both Node.js and JavaScript libraries such as jquery

Involvement in the development and promotion of dependency-check is actively encouraged! You do not have to be a security expert in order to contribute. How you can help:
 * Use the tool
 * Provide feedback via the mailing list or by creating github issues (both bugs and feature requests are encouraged)
 * The project source code is hosted on github - if you are so inclined fork it and provide push requests!