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

Move JNDI / network lookups out of the core module

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Wish
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 2.16.0
    • Core
    • None

    Description

      I don't wish to dogpile on maintainers during a difficult time (the vulnerability of LOG4J2-3201 / LOG4J2-3198), however:

      The surface of what can go wrong with this functionality is vast. A primary motivation for it originally in LOG4J2-313 was context selection, and anecdotally at least, web application containers are a diminishing deployment model in industry.

      In my operation of first- and third-party systems, I do not want this functionality to be used, or at least for any use to draw a high degree of scrutiny.

      Thus I'd like to propose that JNDI lookups require a dedicated dependency such as log4j-jndi without which ${jndi:} lookups should not function.

      While a crucial part of the issue was a sanitization one (LOG4J2-3198) which could have dangers with nearly any lookup plugin, lookups involving any form of network access are of particular concern. Docker and Kubernetes lookups may thus belong in the scope of this request also.

      It would be an improvement to me if only the java JNDI protocol was supported in Core, but much easier to audit if ${jndi:} is altogether unsupported.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            vy Volkan Yazici
            ches Ches Martin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment