[ 
https://issues.apache.org/jira/browse/HBASE-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956522#comment-17956522
 ] 

Dávid Paksy commented on HBASE-20971:
-------------------------------------

Hi [~ndimiduk],
I think this is a very good question. [~stoty] mentioned that they had good 
result at Phoenix running OWASP Dependency Check manually before releases.

There was a discussion about automating it in the original PR: 
[https://github.com/apache/hbase/pull/6822]

 

> Please add OWASP Dependency Check to the core build (pom.xml) and all 
> sub-component builds.
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-20971
>                 URL: https://issues.apache.org/jira/browse/HBASE-20971
>             Project: HBase
>          Issue Type: New Feature
>          Components: build
>    Affects Versions: 3.0.0-alpha-1, 2.2.0, 2.1.1
>         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
(v8.20.10#820010)

Reply via email to