db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Georg Kallidis (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (TORQUE-352) Please add OWASP Dependency Check to the build (pom.xml)
Date Wed, 18 Dec 2019 08:06:00 GMT

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

Georg Kallidis resolved TORQUE-352.
    Fix Version/s: 4.1
         Assignee: Georg Kallidis
       Resolution: Fixed

- fixed in Revision: 1838084

> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>                 Key: TORQUE-352
>                 URL: https://issues.apache.org/jira/browse/TORQUE-352
>             Project: Torque
>          Issue Type: New Feature
>          Components: Maven 1 Plugin, Maven 2 Plugin
>    Affects Versions: 4.1
>         Environment: All development, build, test, environments.
>            Reporter: Albert Baker
>            Assignee: Georg Kallidis
>            Priority: Major
>              Labels: build, easy-fix, security
>             Fix For: 4.1
>   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 newly discovered & reported (known) vulnerailities. 
Project teams that keep up with removing known vulnerabilities on a weekly basis will help
protect businesses that rely on these open source componets.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message