[ https://issues.apache.org/jira/browse/MAHOUT-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trevor Grant resolved MAHOUT-2053. ---------------------------------- Resolution: Duplicate Jira Cleanup 1/31/24 > Please add OWASP Dependency Check to the core build (pom.xml) and all > sub-componet builds. > ------------------------------------------------------------------------------------------ > > Key: MAHOUT-2053 > URL: https://issues.apache.org/jira/browse/MAHOUT-2053 > Project: Mahout > Issue Type: New Feature > Components: build > Affects Versions: 1.0.0, 0.13.0, 0.14.0, 0.13.1, 0.13.2 > Environment: All development, build, test, environments. > Reporter: Albert Baker > Priority: Major > Labels: build, easyfix, security > Original Estimate: 5h > Remaining Estimate: 5h > > 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.10#820010)