Skip to content

Security: remove use log of log4j v1 #12425

Closed

Description

@pjfanning

Description

log4j v1 is end of life and full of security issues

Can you upgrade log4j v2.17.x or reload4j?

  • indexing-hadoop/pom.xml
  • extensions-core/hdfs-storage/pom.xml

Motivation

Please provide the following for the desired feature or change:

  • A detailed description of the intended use case, if applicable
  • Rationale for why the desired feature/change would be beneficial

Activity

  1. changed the title [-]remove use log of log4j v1[/-] [+]Security: remove use log of log4j v1[/+] on Apr 12, 2022
  2. FrankChen021 commented on Apr 18, 2022

    @FrankChen021
    Member

    The log4j v1 used by these two libs is introduced by #11794. And they're used for test profile only. So I think it does not cause any security problems.

    I don't know if it's possible to remove it or upgrade it to log4j2. What do you think ? @cryptoe

  3. cryptoe commented on Apr 18, 2022

    @cryptoe
    Contributor

    Let's try to bump it to log4j2 and look at the travis runs.

  4. murari-goswami commented on Feb 13, 2024

    @murari-goswami

    The log4j v1 is in use for below transitive dependency other than the tests. Can we please bump this up to have a fix to get the CVE fix.

    +- org.apache.ranger:ranger-plugins-common:jar:2.0.0:compile
    | +- log4j:log4j:jar:1.2.17:compile

    +- org.apache.hive.shims:hive-shims-0.23:jar:3.1.3:runtime
    - org.apache.hadoop:hadoop-yarn-server-resourcemanager:jar:3.1.0:runtime
    +- log4j:log4j:jar:1.2.17:runtime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions