[
https://issues.apache.org/jira/browse/CASSANDRA-17966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019219#comment-18019219
]
Teddy Reed commented on CASSANDRA-17966:
----------------------------------------
That sounds good, so then the suppress/not-suppress is moot with 4.0.19, since
then 4.0/4.1/5.0 are all using jackson-databind versions without the
vulnerability. And also +1 that there's no additional risk for a user with
write beyond the existing trust/risk already conveyed. I could not find any way
to trigger via a pure-read path, and also could not find a way from reading the
code. (yet, a poor proof by lack of counter evidence)
> jackson-databind vulnerability CVE-2022-42003 CVE-2022-42004
> ------------------------------------------------------------
>
> Key: CASSANDRA-17966
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17966
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Dependencies
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 3.11.14, 4.0.7, 4.1-rc1, 5.0-alpha1, 5.0
>
>
> As the summary says, jackson-databind 2.13.2.2 which was upgraded for a
> vulnerability in CASSANDRA-17556 is vulnerable again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
