[
https://issues.apache.org/jira/browse/TEZ-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated TEZ-3975:
------------------------------
Fix Version/s: 0.10.0
> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
> Key: TEZ-3975
> URL: https://issues.apache.org/jira/browse/TEZ-3975
> Project: Apache Tez
> Issue Type: New Feature
> Affects Versions: 0.8.next, 0.10.0, 0.10.1
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Assignee: Jonathan Turner Eagles
> Priority: Major
> Labels: build, easy-fix, security
> Fix For: 0.9.2, 0.10.0, 0.10.1
>
> Attachments: TEZ-3975.001.patch
>
> 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 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
(v8.3.4#803005)
