[
https://issues.apache.org/jira/browse/BEAM-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547303#comment-17547303
]
Kenneth Knowles commented on BEAM-5075:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/19071
> Please add OWASP Dependency Check to the build
> ----------------------------------------------
>
> Key: BEAM-5075
> URL: https://issues.apache.org/jira/browse/BEAM-5075
> Project: Beam
> Issue Type: New Feature
> Components: build-system
> Affects Versions: 3.0.0, 2.6.0, 2.7.0
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Priority: P3
> 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 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.20.7#820007)
