You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Goldstein Lyor (JIRA)" <ji...@apache.org> on 2018/08/05 17:31:00 UTC

[jira] [Resolved] (SSHD-837) Please add OWASP Dependency Check to the build (pom.xml)

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

Goldstein Lyor resolved SSHD-837.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.1

Activated via {{owasp}} profile: {code:bash}mvn -Pquick,owasp verify{code}

> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
>                 Key: SSHD-837
>                 URL: https://issues.apache.org/jira/browse/SSHD-837
>             Project: MINA SSHD
>          Issue Type: New Feature
>    Affects Versions: 2.0.0, 2.1.0, 2.0.1
>         Environment: All development, build, test, environments.
>            Reporter: Albert Baker
>            Assignee: Goldstein Lyor
>            Priority: Major
>              Labels: build, easy-fix, security
>             Fix For: 2.0.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 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)