Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-2987

Snyk reports vulnerability for log4j-to-slf4j caused by junit transitive depedency

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Not A Problem
    • 2.14.0
    • None
    • SLF4J Bridge
    • None

    Description

      I am using log4j-to-slf4j bridge for my own library. During the regular vulnerability scan it reported that it has a vulnerability caused by a transitive dependency from log4j-api which has a compile scoped dependency of org.junit.jupiter:junit-jupiter-migrationsupport.

      See here for a screenshot:

      See here for the report: https://app.snyk.io/org/hakky54/project/667055da-a0a4-461f-a169-e88bd2f94ce1

       

      This issue can fixed when adding the test scope to the dependency in the following file: https://github.com/apache/logging-log4j2/blob/master/log4j-api/pom.xml

      I am not familiar with the code base, so I was not sure if someone did not put a test scope on purpose... But looking at the other dependencies the following could also by marked as test scope: junit-vintage-engine, junit-jupiter-migrationsupport, junit-jupiter-params, junit-jupiter-engine, assertj-core

      Attachments

        1. image-2020-12-30-11-44-03-287.png
          235 kB
          Hakan Altindag

        Activity

          People

            Unassigned Unassigned
            Hakky54 Hakan Altindag
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2h
                2h
                Remaining:
                Remaining Estimate - 2h
                2h
                Logged:
                Time Spent - Not Specified
                Not Specified