You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/24 12:44:00 UTC
[jira] [Commented] (NIFI-5541) Please add OWASP Dependency Check to
the build (pom.xml)
[ https://issues.apache.org/jira/browse/NIFI-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591586#comment-16591586 ]
ASF GitHub Bot commented on NIFI-5541:
--------------------------------------
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/2963
NIFI-5541 - Added OWASP profile for dependency check
Added a profile allowing people to run the OWASP maven plugin. I had to add ``<nspAnalyzerEnabled>false</nspAnalyzerEnabled>`` to get things working without failure.
I'm running the following command:
````shell
mvn -Powasp -Dtest=false -DfailIfNoTests=false org.owasp:dependency-check-maven:aggregate
````
````
Project: nifi
org.apache.nifi:nifi:1.8.0-SNAPSHOT
Scan Information (show less):
dependency-check version: 3.3.1
Report Generated On: Aug 24, 2018 at 14:27:56 +02:00
Dependencies Scanned: 1855 (1181 unique)
Vulnerable Dependencies: 141
Vulnerabilities Found: 509
Vulnerabilities Suppressed: 0
NVD CVE 2002: 23/08/2018 09:24:06
NVD CVE 2003: 24/08/2018 13:00:49
NVD CVE 2004: 15/08/2018 10:16:37
NVD CVE 2005: 15/08/2018 10:14:46
NVD CVE 2006: 15/08/2018 10:11:39
NVD CVE 2007: 15/08/2018 10:06:55
NVD CVE 2008: 15/08/2018 10:02:24
NVD CVE 2009: 15/08/2018 09:57:28
NVD CVE 2010: 15/08/2018 09:53:24
NVD CVE 2011: 24/08/2018 13:00:48
NVD CVE 2012: 24/08/2018 13:00:48
NVD CVE 2013: 24/08/2018 13:00:48
NVD CVE 2014: 24/08/2018 13:00:47
NVD CVE 2015: 24/08/2018 13:00:47
NVD CVE 2016: 24/08/2018 13:00:47
NVD CVE 2017: 24/08/2018 13:00:47
NVD CVE 2018: 24/08/2018 13:00:48
NVD CVE Checked: 24/08/2018 13:46:11
NVD CVE Modified: 24/08/2018 12:01:53
VersionCheckOn: 1535111171413
````
Full report here: http://jsfiddle.net/4jk90tqo/embedded/result/
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pvillard31/nifi NIFI-5541
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2963.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2963
----
commit 871598742ad26e585da73a1d8bb506972a1ace43
Author: Pierre Villard <pi...@...>
Date: 2018-08-24T12:36:36Z
NIFI-5541 - Added OWASP profile for dependency check
----
> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
> Key: NIFI-5541
> URL: https://issues.apache.org/jira/browse/NIFI-5541
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Tools and Build
> Affects Versions: 2.0.0, 1.8.0
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Assignee: Pierre Villard
> Priority: Major
> Labels: build, easy-fix, security
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Please add OWASP Dependency Check to the build (pom.xml). OWASP DC makes an outbound REST call to MITRE Common Vulnerabilities & Exposures (CVE) to perform a lookup for each dependant .jar to list any/all known vulnerabilities for each jar. This step is needed because a manual MITRE CVE lookup/check on the main component does not include checking for vulnerabilities that get pulled into the released product via dependant/third-party libraries.
> OWASP Dependency check : https://www.owasp.org/index.php/OWASP_Dependency_Check has plug-ins for most Java build/make types (ant, maven, ivy, gradle).
> Also, add the appropriate command to the nightly build to generate a report of all known vulnerabilities in any/all third party libraries/dependencies that get pulled in. example : mvn -Powasp -Dtest=false -DfailIfNoTests=false clean aggregate
> Generating this report nightly/weekly will help inform the project's development team if any dependant libraries have a newly discovered & reported (known) vulnerailities. Project teams that keep up with removing known vulnerabilities on a weekly basis will help protect businesses that rely on these open source componets.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)