cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14612) Please add OWASP Dependency Check to the build (pom.xml)
Date Tue, 31 Jul 2018 01:16:00 GMT


Jason Brown commented on CASSANDRA-14612:

tbh, running this on nightly builds is kinda overkill, as nobody runs nightly builds in production
(and we don't make them, as [~djoshi3] points out). Even if we ran this proposal as part of
the release process, and posted that as part of the vote, it sounds like like we'd still be
much closer to the intent of this request. 

We don't change dependencies that often, and when we do, it's probably simpler to just run
the "OWASP checker" task at release time. Hell, we could add it to the the CI jobs, if we
cared to go that far.

> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>                 Key: CASSANDRA-14612
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Build, Lifecycle, Observability, Repair, Testing
>         Environment: All development, build, test, environments.
>            Reporter: Albert Baker
>            Priority: Major
>              Labels: build, easyfix, security
>             Fix For: 3.11.x, 4.x
>   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 : 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message