Uploaded image for project: 'Qpid JMS'
  1. Qpid JMS
  2. QPIDJMS-503

Upgrade examples log4j dependency to log4j2

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.51.0
    • 0.52.0
    • qpid-jms-client
    • None

    Description

      The log4j 1.x reached EOL on August 5, 2015 as per http://logging.apache.org/log4j/1.2/. The client is distributes with an optional dependency log4j 1.2.17. There is CVE-2019-17571 raised against this version for class SocketServer that is vulnerable to deserialization of untrusted data. Though, no log4j configuration in the Qpid JMS client uses SocketServer, the open source scanning tools flag the JMS client bundle as being impacted by CVE-2019-17571.
      In order to silence such open source scanning tools the log4j dependencies can be upgraded to log4j2.

      Added detail for clarity: note the client itself has no dependency on Log4J, it is used in the tests, and the examples, and is in the release archive for use with those, but the actual client module does not use it (uses only SLF4J).

      Attachments

        Activity

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

          People

            robbie Robbie Gemmell
            orudyy Alex Rudyy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment