You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Tamas Penzes (Jira)" <ji...@apache.org> on 2020/02/24 14:25:00 UTC

[jira] [Commented] (HADOOP-16485) Remove dependency on jackson

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

Tamas Penzes commented on HADOOP-16485:
---------------------------------------

It's worth reading the following article: [https://medium.com/@cowtowncoder/jackson-2-10-features-cd880674d8a2]

[~weichiu] would it be an option to update to 2.10.2 instead of removing it?

> Remove dependency on jackson
> ----------------------------
>
>                 Key: HADOOP-16485
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16485
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Wei-Chiu Chuang
>            Priority: Major
>              Labels: release-blocker
>
> Looking at git history, there were 5 commits related to updating jackson versions due to various CVEs since 2018. And it seems to get worse more recently.
> File this jira to discuss the possibility of removing jackson dependency once for all. I see that jackson is deeply integrated into Hadoop codebase, so not a trivial task. However, if Hadoop is forced to make a new set of releases because of Jackson vulnerabilities, it may start to look not so costly.
> At the very least, consider stripping jackson-databind coode, since that's where the majority of CVEs come from.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org