[
https://issues.apache.org/jira/browse/CASSANDRA-14612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419400#comment-17419400
]
Stefan Miklosovic commented on CASSANDRA-14612:
-----------------------------------------------
criticals in 4.0
cassandra-driver-core-3.11.0-shaded.jar: CVE-2018-8016 - supress, this is false
positive, it was thinking it is this
https://issues.apache.org/jira/browse/CASSANDRA-14173
chronicle-wire-2.20.117.jar: CVE-2020-27853 - this is false positive, it thinks
it is a completely different package
https://nvd.nist.gov/vuln/detail/CVE-2020-27853
commons-collections-3.2.1.jar: CVE-2017-15708 - exploitable as already discussed
hadoop-core-1.0.3.jar: CVE-2012-4449 - suppress
jackson-mapper-asl-1.0.1.jar: CVE-2017-17485, CVE-2017-7525, CVE-2017-15095,
CVE-2018-14718, CVE-2018-7489, CVE-2019-17267, CVE-2019-16335, CVE-2019-14893,
CVE-2019-14540 -
I am not sure where this is comming from, it is marked as "excluded" in hadoop
and hadoop-minicluster but I see it is still downloaded into build/lib/jars so
I guess there is yet somebody else depending on this but we do not ship this.
jetty-6.1.26.jar: CVE-2017-7658, CVE-2017-7657 - suppress
criticals in trunk
cassandra-driver-core-3.11.0-shaded.jar: CVE-2018-8016 - supress, this is false
positive, it was thinking it is this
https://issues.apache.org/jira/browse/CASSANDRA-14173
chronicle-wire-2.20.117.jar: CVE-2020-27853 - supress
commons-collections-3.2.1.jar: CVE-2017-15708 - reported as exploitable
hadoop-core-1.0.3.jar: CVE-2012-4449 - supress
jetty-6.1.26.jar: CVE-2017-7658, CVE-2017-7657 - supress
All the time I was scanning build/lib/jars but there are jars we ship in "lib"
dir in the root, "lib" is just a subset of "build/lib/jars" so it doesnt matter
I scanned it instead of lib. At least we know what vulnerabilities there are in
stuff we do not necessarilly package.
Are we ok with scanning all build/lib/jars or we should focus on "lib" only?
[~ABakerIII] I was not able to connect the lib we are shipping with any library
in the list from that project so I guess if it is trully exploitable we do not
know what jar causes it. The only thing I see is commons-io:2.6 in
build/test/lib/jars and in the list it is version 2.4 but I guess that might
still apply. Free free to reach me (preferable privately) with the details /
steps how you actually exploited this etc so I might repeat as you did it.
Anyway, I will prepare the suppression files for each branch and I will put it
all together and we might review it more formaly.
> 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]
