[ 
https://issues.apache.org/jira/browse/CXF-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colm O hEigeartaigh reassigned CXF-7809:
----------------------------------------

    Assignee: Colm O hEigeartaigh

> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
>                 Key: CXF-7809
>                 URL: https://issues.apache.org/jira/browse/CXF-7809
>             Project: CXF
>          Issue Type: New Feature
>          Components: Aegis Databinding, Build system, Clustering, 
> Configuration, CORBA Binding, Core, Integration, JAX-RS, JAX-RS Security, 
> JAX-WS Runtime, JAXB Databinding, JMS, Management, OSGi, OtherDatabindings, 
> Resources, Service Model, Services, Soap Binding, Tooling, WS-* Components
>    Affects Versions: 3.2.6, 3.1.17, 3.3.0
>         Environment: All development, build, test, environments.
>            Reporter: Albert Baker
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>              Labels: build, easyfix, security
>             Fix For: 3.3.0
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> 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