Dependency-Check Plugin for SonarQube 7.x
Integrates Dependency-Check reports into SonarQube v7.6 or higher.
Please see the SonarQube 6.x branch for SonarQube 6.x LTS support. The project will try to backport all code from master branch, as long as the LTS version is supported. Please see the SonarQube 5.x branch for older SonarQube 5.x support.
Dependency-Check is a utility that attempts to detect publicly disclosed vulnerabilities contained within project dependencies. It does this by determining if there is a Common Platform Enumeration (CPE) identifier for a given dependency. If found, it will generate a report linking to the associated CVE entries.
Dependency-Check supports the identification of project dependencies in a number of different languages including Java, .NET, Node.js, Ruby, and Python.
This SonarQube plugin does not perform analysis, rather, it reads existing Dependency-Check reports. Use one of the other available methods to scan project dependencies and generate the necessary XML report which can then be consumed by this plugin. Refer to the Dependency-Check project for relevant documentation.
The plugin keeps track of a number of statistics including:
- Total number of dependencies scanned
- Total number of vulnerabilities found across all dependencies
- Total number of vulnerable components
- Total number of critical, high, medium, and low severity vulnerabilities
Additionally, the following two metrics are defined:
Inherited Risk Score (IRS)
(critical * 7) + (high * 5) + (medium * 3) + (low * 1)
The IRS is simply a weighted measurement of the vulnerabilities inherited by the application through the use of vulnerable components. It does not measure the applications actual risk due to those components. The higher the score the more risk the application inherits.
Vulnerable Component Ratio
(vulnerabilities / vulnerableComponents)
This is simply a measurement of the number of vulnerabilities to the vulnerable components (as a percentage). A higher percentage indicates that a large number of components contain vulnerabilities. Lower percentages are better.
$ mvn clean package
Copy the plugin (jar file) to $SONAR_INSTALL_DIR/extensions/plugins and restart SonarQube.
Create aggregate reports with Dependency-Check. Dependency-Check will output a file named 'dependency-check-report.xml' when asked to output XML. The Dependency-Check SonarQube plugin reads an existing Dependency-Check XML report.
A typical SonarQube configuration will have the following parameter. This example assumes the use of a Jenkins workspace, but can easily be altered for other CI/CD systems.
In this example, both the XML and HTML reports are specified. Only the XML report is required, however, if the HTML report is also available, it greatly enhances the usability of the SonarQube plugin by incorporating the actual Dependency-Check HTML report in the SonarQube project.
To configure the severity of the created issues you can optionally specify the minimum score for each severity with the following parameter. Specify a score of
-1 to completely disable a severity.
sonar.dependencyCheck.severity.blocker=9.0 sonar.dependencyCheck.severity.critical=7.0 sonar.dependencyCheck.severity.major=4.0 sonar.dependencyCheck.severity.minor=0.0
In large projects you have many dependencies with (hopefully) no vulnerabilities. The following configuration summarize all vulnerabilities of one dependency into one issue.
sonar.dependencyCheck.summarize=true sonar.dependencyCheck.summarize=false (default)
Dependency-Check is available as a:
- Command-line utility
- Ant Task
- Gradle Plugin
- Jenkins Plugin
- Maven Plugin
- SonarQube Plugin
Copyright & License
Dependency-Check Sonar Plugin is Copyright (c) SonarSecurityCommunity. All Rights Reserved.
Dependency-Check is Copyright (c) Jeremy Long. All Rights Reserved.
Permission to modify and redistribute is granted under the terms of the LGPLv3 license.