commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Baker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMMONSSITE-119) Please add OWASP Dependency Check to all commons projects - affects all versions
Date Tue, 31 Jul 2018 12:15:00 GMT

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

Albert Baker commented on COMMONSSITE-119:
------------------------------------------

Old libraries/dependencies do incurr new vulnerabilities.  Both because a new reasercher
develops a new way to subvert systems and applies that to your a & reports it, and many
libraries just have never been tested very hard; so vulnerabilities lay dormant for years
until someone decides to squeeze them. 

> Please add OWASP Dependency Check to all commons projects - affects all versions
> --------------------------------------------------------------------------------
>
>                 Key: COMMONSSITE-119
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-119
>             Project: Commons All
>          Issue Type: New Feature
>          Components: Commons Build
>         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 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