You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2021/05/28 13:11:00 UTC
[jira] [Commented] (BEAM-12422) Vendored gRPC 1.36.0 is using a
log4j version with security issues
[ https://issues.apache.org/jira/browse/BEAM-12422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353338#comment-17353338 ]
Ismaël Mejía commented on BEAM-12422:
-------------------------------------
[~suztomo] do you know why we are defining log4j explicitly there? I wonder if we really need this dependency. Seems to come from a transitive dependency no? I suppose gRPC does not use log4j directly.
> Vendored gRPC 1.36.0 is using a log4j version with security issues
> ------------------------------------------------------------------
>
> Key: BEAM-12422
> URL: https://issues.apache.org/jira/browse/BEAM-12422
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Affects Versions: 2.30.0
> Reporter: Ismaël Mejía
> Priority: P1
>
> Automatic security scanners report this vulnerability [https://nvd.nist.gov/vuln/detail/CVE-2017-5645]
> This is defined during vendoring here https://github.com/apache/beam/blob/3c9807bfb4e00a8f8564b4688e01ad5c8c2189d2/buildSrc/src/main/groovy/org/apache/beam/gradle/GrpcVendoring_1_36_0.groovy#L71
--
This message was sent by Atlassian Jira
(v8.3.4#803005)