[ 
https://issues.apache.org/jira/browse/CASSANDRA-17459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509810#comment-17509810
 ] 

Brandon Williams edited comment on CASSANDRA-17459 at 3/21/22, 3:58 PM:
------------------------------------------------------------------------

jackson-databind: For CVE-2020-36518 we should upgrade as someone could 
technically cause a DoS with json over cql

cassandra-driver: For the driver we'll just suppress our own CVE-2021-44521.



was (Author: brandon.williams):
jackson-databind: For CVE-2020-36518 we should upgrade as someone could 
technically cause a DoS with json over cql

cassandra-driver: For the driver we'll just suppress our own CVE-2021-44521.

netty-tcnative: Most of these are HTTP-related that we already have these 
suppressed for other parts of netty,  but a few remain:
* CVE-2019-16869 - HTTP
* CVE-2015-2156 - HTTP
* CVE-2014-3488 - SSL DoS
* CVE-2019-20445 - HTTP



> OWASP failures on trunk
> -----------------------
>
>                 Key: CASSANDRA-17459
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17459
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Build
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Normal
>             Fix For: 4.x
>
>
> On trunk there are a few failures:
> {quote}
> Dependency-Check Failure:
> One or more dependencies were identified with vulnerabilities that have a 
> CVSS score greater than or equal to '1.0': 
> cassandra-driver-core-3.11.0-shaded.jar: CVE-2021-44521
> jackson-databind-2.12.5.jar: CVE-2020-36518
> See the dependency-check report for more details.
> {quote}
> Notably, we have bitten ourselves with CVE-2021-44521, which the driver has 
> echoed, which we depend on.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to