[
https://issues.apache.org/jira/browse/KNOX-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638315#comment-16638315
]
Kevin Risden commented on KNOX-1421:
------------------------------------
Attached latest report from [https://github.com/apache/knox/pull/31] (which is
based on master with all the dependencies from KNOX-1484 upgraded). It has
exclusions for matches that aren't correct as well.
Remaining dependencies:
* jetty - Need to look at upgrading Jetty separately
* hadoop - see KNOX-1501
** The one CVE about 3.0.0.alpha1 is incorrect but excluding it causes bad
matches
* htrace - Need to see if this dependency can be excluded
* spring - Need to see if this dependency can be excluded
* apacheds - Looked at upgrading to AM25 instead of M24 but ran into
DIRSERVER-224. Need to wait for next release to come out.
> Enable OWASP Dependency Check
> -----------------------------
>
> Key: KNOX-1421
> URL: https://issues.apache.org/jira/browse/KNOX-1421
> Project: Apache Knox
> Issue Type: New Feature
> Components: Build
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Assignee: Kevin Risden
> Priority: Major
> Labels: build, security
> Fix For: 1.2.0
>
> Attachments:
> dependency-check-report-3414a1a7ca334535ce06b298f3149b33ed1aed8e.html,
> dependency-check-report-cb9911a25a2dae1abfd6c1e5a8ef0ee865afa4d9.html
>
> 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 in components or in dependant 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
> 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)
