[
https://issues.apache.org/jira/browse/COMMONSSITE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562235#comment-16562235
]
Albert Baker commented on COMMONSSITE-119:
------------------------------------------
A reason for performing this more often is that during development of a new
feature, a partial fix will get checkin on day , then added to the next day and
checked in again, then get added to a third day and checked in again. Each
day may also add a unit test that checks that days functionality. However each
new piece of functionality could bring in a new dependency, perhaps several
over several days. It would be very beneficial for the developer to know that
the dependency they added on the first day was flawed and that first days'
fuctionality needs to be re-worked,/prior/ to building more code on top of it,
resulting in possibly lots of code that has to get thrown out or substantially
re-worked. It would be good to know that sooner than later so that entire
weeks of work dont need to be re-done becuase a simple check was put-off to the
final build.
> 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)
