syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-1349) Please add OWASP Dependency Check to the build (pom.xml)
Date Mon, 06 Aug 2018 10:04:00 GMT

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

Francesco Chicchiriccò commented on SYNCOPE-1349:
-------------------------------------------------

[~massimiliano.perrone@tirasa.net] maybe you need to refresh, and you'll see the attached
report, above.

About [~ABakerIII], you can see his recent activity from https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ABakerIII
- with some sensible replies.

To me, adding some OWASP check is not a bad idea; only, as far as I can see from the report,
the provided tooling is possibly not adequate.


> 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)

Mime
View raw message