[
https://issues.apache.org/jira/browse/CASSANDRA-14612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419244#comment-17419244
]
Stefan Miklosovic commented on CASSANDRA-14612:
-----------------------------------------------
CRITICALS in 3.11
commons-collections-3.2.1.jar: CVE-2017-15708
hadoop-core-1.0.3.jar: CVE-2012-4449 - good old Hadoop -
https://nvd.nist.gov/vuln/detail/CVE-2012-4449, I would just supress this imo
jetty-6.1.26.jar: CVE-2017-7658, CVE-2017-7657 - believe or now, we are
packaging jetty server into Cassandra as a dependency from hadoop-core, see
here (1), I am not sure we ever need this so if we do not exclude that in
build.xml, I would just supress this.
libthrift-0.9.2.jar: CVE-2016-5397 - skip, same as in 3.0
logback-core-1.1.3.jar: CVE-2017-5929 - skip, same as in 3.0
netty-all-4.0.44.Final.jar: CVE-2019-20445, CVE-2019-20444, skip, same as in 3.0
(1)
https://repo1.maven.org/maven2/org/apache/hadoop/hadoop-core/1.0.3/hadoop-core-1.0.3.pom
> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
> Key: CASSANDRA-14612
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14612
> Project: Cassandra
> Issue Type: New Feature
> Components: Build
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Assignee: Stefan Miklosovic
> Priority: Normal
> 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 :
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
