Bamboo: Multiple vulnerabilities in log4j < 1.2.17-atlassian-16

XMLWordPrintable

    • 8.1
    • High
    • CVE-2020-9493

      The version of log4j bundled with Bamboo has been updated from version 1.2.7-atlassian-15 to 1.2.7-atlassian-16 to address the following vulnerabilities:

      CVE-2020-9493 and CVE-2022-23307
      Apache Chainsaw is bundled with log4j 1.2.x, and is vulnerable to a deserialization flaw. A remote, unauthenticated attacker could exploit this to execute arbitrary code. Please note that Chainsaw is a log viewer that is designed to be executed manually. It is not required by Bamboo, nor is it executed by default, nor does Atlassian provide any documentation on using Chainsaw with Bamboo. Atlassian has remediated this vulnerability by removing Chainsaw from the Atlassian version of log4j.

      CVE-2022-23302
      JMSSink is vulnerable to a deserialization flaw. A local attacker with privileges to update the Bamboo configuration can exploit this to execute arbitrary code. Bamboo is not configured to use JMSSink by default, nor does Atlassian provide any documentation on using JMSSink with Bamboo. Atlassian has remediated this vulnerability by removing JMSSink from the Atlassian version of log4j.

      CVE-2022-23305
      JDBCAppender is vulnerable to a SQL injection flaw when configured to use the message converter (%m). A remote, unauthenticated attacker can exploit this to execute arbitrary SQL queries. Bamboo is not configured to use JDBCAppender by default, nor does Atlassian provide any documentation on using JDBCAppender with Bamboo. Atlassian has remediated this vulnerability by removing JDBCAppender from the Atlassian version of log4j.

      Affected versions of Bamboo:

      • Versions < 8.1.4

      Fixed versions of Bamboo:

      • Versions 8.1.x >= 8.1.4
      • Versions >= 8.2.0

              Assignee:
              Unassigned
              Reporter:
              Security Metrics Bot
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: