[
https://issues.apache.org/jira/browse/BEAM-11055?focusedWorklogId=508479&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-508479
]
ASF GitHub Bot logged work on BEAM-11055:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Nov/20 14:12
Start Date: 06/Nov/20 14:12
Worklog Time Spent: 10m
Work Description: iemejia commented on pull request #13073:
URL: https://github.com/apache/beam/pull/13073#issuecomment-723101054
Argh! I was afraid of that too, It clearly looks like a different classpath
issue, that will explain why it breaks so weirdly.
I think the simplest solution would be to let that module to provide its own
log4j. The part that still does not make any sense to me is how the hcatalog
module in Beam ends up resolving the new version of log4j? Can you spot which
dependency is overwriting the version ? From a look at the module build.gradle
file I don't see any of the Beam dependencies of hcatalog requiring log4j. I
have checked in the [gradle
scan](https://scans.gradle.com/s/6fi4yafhc37zc/dependencies?focusedDependencyView=versions&toggled=W1s4MF0sWzgwLDIxXSxbODAsMjEsWzExNDEwXV0sWzgwLDIxLFsxMTQxMCwxMTQxNF1dLFs4MCwyMSxbMTE0MTAsMTE0MTQsMTE0MTZdXV0)
too and I just cannot see who is doing it
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 508479)
Time Spent: 4h 50m (was: 4h 40m)
> Update log4j to version 2.13.3
> ------------------------------
>
> Key: BEAM-11055
> URL: https://issues.apache.org/jira/browse/BEAM-11055
> Project: Beam
> Issue Type: Improvement
> Components: build-system, io-java-elasticsearch
> Reporter: Ismaël Mejía
> Assignee: Ismaël Mejía
> Priority: P2
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> Beam uses a version of log4j that is reported by some security tools to have
> some security issues. Notice that Beam's use of log4j should not be impacted
> by the issue.
> See [https://nvd.nist.gov/vuln/detail/CVE-2017-5645]
> The update in the vendored grpc module is to ensure it gets updated too in a
> future release of our vendored dependencies. Notice that this is a runtime
> dep for users so they are free to provide their own version so less of an
> issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
