You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2018/08/05 04:08:00 UTC
[jira] [Commented] (HADOOP-15653) Please add OWASP Dependency Check
to the build (pom.xml)
[ https://issues.apache.org/jira/browse/HADOOP-15653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569354#comment-16569354 ]
Allen Wittenauer commented on HADOOP-15653:
-------------------------------------------
It's already there in modern versions of Hadoop. Just run 'mvn dependency-check:aggregate (other appropriate flags)'. It should be noted that in my testing, the maven plugin has several deficiences that would lead someone to get an incomplete picture. For example, it doesn't not read the node.js package.json file. (Ofc, the standalone version doesn't read the pom file, so ...)
FWIW, the Apache Yetus team is adding support for the OWASP dependency checker to precommit and qbt. See YETUS-441 for details.
> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
> Key: HADOOP-15653
> URL: https://issues.apache.org/jira/browse/HADOOP-15653
> Project: Hadoop Common
> Issue Type: New Feature
> Components: build
> Affects Versions: 3.0.0
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Priority: Major
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org