[PIG-5352] Please add OWASP Dependency Check to the build (ivy.xml)

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.15.1, 0.17.0, 0.16.1, 0.18.0, 0.17.1
• Fix Version/s: 0.18.0
• Component/s: build
• Labels: security

Environment

All development, build, test, environments.

• Patch Info: Patch Available
• Hadoop Flags: Reviewed

Release Note

Now
% ant owasp
would create a report for known vulnerabilities for the jars Pig depend on at ./build/owasp.

• Flags: Patch, Important
• Assignee: Koji Noguchi
• Reporter: Albert Baker
• Created: 30/Jul/18 00:51
• Updated: 10/Jan/20 22:10
• Resolved: 10/Jan/20 22:10

Description

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.