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

Albert Baker commented on SYNCOPE-1349:
---------------------------------------

Massi :  OWASP report lets you know if any known vulnerabilities are currently 
in your build, /and/ tomorrow, next week, next month..a new vulnerability could 
be discovered & reported against a library that you use.   It is helpful to run 
the report ? daily/weekly ?  so that you know as quickly as possible, if/when a 
new vulnerability becomes known so you can take action.    You are exceedily 
lucky that there are no serious vulnerabilities /today/.  99.999% of projects 
are no so lucky.

 

> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
>                 Key: SYNCOPE-1349
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1349
>             Project: Syncope
>          Issue Type: New Feature
>    Affects Versions: 2.0.10, 2.1.1, 3.0.0
>         Environment: All development, build, test, environments.
>            Reporter: Albert Baker
>            Priority: Major
>              Labels: build, easy-fix, security
>         Attachments: dependency-check-report.html
>
>   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)

Reply via email to