[AMBARI-24376] Please add OWASP Dependency Check to the build (pom.xml)

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 3.0.0, trunk, 2.6.2, 2.7.1
• Component/s: ambari-admin, ambari-client, ambari-server, ambari-shell, ambari-views, ambari-web, security
• Labels: build easyfix security

Environment

All development, build, test, environments of the core product and all of its associated componnets.

• Flags: Patch, Important
• Assignee: Unassigned
• Reporter: Albert Baker
• Created: 30/Jul/18 00:04
• Updated: 30/Jul/18 00:09
• Resolved: 30/Jul/18 00:09

Description

Please add OWASP Dependency Check to the build (pom.xml) of the core components and all sub-components. 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.