[jira] [Commented] (KAFKA-6737) Is Kafka imapcted by critical vulnerqbilty CVE-2018-7489

["Ismael Juma (JIRA)" <ji...@apache.org>]

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

Ismael Juma commented on KAFKA-6737:
------------------------------------

As the description states, c3p0 has to be in the classpath and Kafka doesn't depend on that library. We have upgraded Jackson to 2.9.5 in trunk in any case though:

https://github.com/apache/kafka/commit/9baa9bddba0dc1b3bda167ea509bd90226615e1f

> Is Kafka imapcted by critical vulnerqbilty CVE-2018-7489
> --------------------------------------------------------
>
>                 Key: KAFKA-6737
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6737
>             Project: Kafka
>          Issue Type: Bug
>          Components: packaging, security, unit tests
>    Affects Versions: 0.10.1.0, 1.1.0, 1.0.1
>            Reporter: Akansh Shandilya
>            Priority: Critical
>
> Kafka is using FasterXML jackson-databind before 2.8.11.1 and 2.9.x before 2.9.5 , which allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the c3p0 libraries are available in the classpath.
>  
> I have checked that all released versions of Kafka are using jackson-databind before 2.8.11.1 and 2.9.x before 2.9.5.
> There are three open questions:
> Question1: Is Kafka imapcted by critical vulnerqbilty CVE-2018-7489?
> [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-7489]
> Question2: If answer of first question is Yes. Is there any workaround to fix it on released version. 
> Question3: If answer of first question is Yes. Should we fix it in future versions?
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)