[
https://issues.apache.org/jira/browse/BEAM-7881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948204#comment-16948204
]
Romain Manni-Bucau commented on BEAM-7881:
------------------------------------------
Well I dont really panic but I am a bkt tired of that issue.
You need to consider multiple points on that:
# Jackson alone is in better shape and does require an explicit list of
*classnames* if the feature is activated - note it is not only what was done
# Projects cant review all usages each time an issue is found so it is
expected to be CVE free anyway
# Jackson still enables to exploits the issue by its too user friendly config
# Beam must also ensure there is no issue in all possible usable runner stacks
# Most of beam code can be exploited from an endpoint or external system by
design even if indirected (all is not just cronned ;))
# Beam is often coupled with other libs which can exploit that so not having
it is more drastic but efficient and saves investigations for each release
which is very costly for end users for literally no gain
> Get rid of jackson to avoid the continuous flow of CVEs in Jackson
> ------------------------------------------------------------------
>
> Key: BEAM-7881
> URL: https://issues.apache.org/jira/browse/BEAM-7881
> Project: Beam
> Issue Type: Task
> Components: sdk-java-core
> Affects Versions: 2.14.0
> Reporter: Romain Manni-Bucau
> Priority: Blocker
>
> Jackson keeps having CVE on all releases of databind and transitively beam
> sdk java core has CVE on all its releases (for the record, when writing this
> issue you must use at least jackson-databind 2.9.9.2 but last week it was
> 2.9.9.1 and 2.14 didn't get the fix).
> Can be neat to get rid of jackson which does not fix this issue for a very
> long time now and just use JSON-B or another JSON impl to ensure the CVE is
> not usable because beam is there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
