You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Georg Kallidis (JIRA)" <ji...@apache.org> on 2018/08/15 12:41:00 UTC
[jira] [Commented] (TORQUE-352) Please add OWASP Dependency Check
to the build (pom.xml)
[ https://issues.apache.org/jira/browse/TORQUE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581024#comment-16581024 ]
Georg Kallidis commented on TORQUE-352:
---------------------------------------
I ve updated Torque trunk pom.xml with the OWASP plugin, tested it and applied some changes, which could be fixed by upgrading or declaring as false positive.
{code:java}
>mvn -Powasp -Dtest=false -DfailIfNoTests=false clean verify
{code}
should now run the OWASP checks. Further steps to generate the nightly report may be needed..
> 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
> 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 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org