You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2025/04/19 13:45:00 UTC

[jira] [Updated] (COLLECTIONS-693) Please add OWASP Dependency Check to the build

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

Gary D. Gregory updated COLLECTIONS-693:
----------------------------------------
    Summary: Please add OWASP Dependency Check to the build  (was: Please add OWASP Dependency Check to the build (build.xml))

> Please add OWASP Dependency Check to the build
> ----------------------------------------------
>
>                 Key: COLLECTIONS-693
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-693
>             Project: Commons Collections
>          Issue Type: New Feature
>          Components: Collection, Core
>    Affects Versions: 4.2, 4.x
>         Environment: All development, build, test, environments.
>            Reporter: Albert Baker
>            Priority: Major
>             Fix For: 4.5.0
>
>   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
(v8.20.10#820010)