Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-25799

SSRF (Server-Side Request Forgery) org.apache.xmlgraphics:batik-bridge Dependency in Jira Software Data Center and Server

    • Icon: Public Security Vulnerability Public Security Vulnerability
    • Resolution: Fixed
    • Icon: High High (View bug fix roadmap)
    • 9.4.16, 9.14.0, 9.12.4
    • 8.20.0, (34)
      8.22.0, 8.22.1, 8.22.2, 9.0.0, 8.22.3, 9.1.0, 8.22.4, 9.2.0, 8.22.6, 9.1.1, 9.3.0, 9.4.0, 9.2.1, 9.3.1, 9.5.0, 9.3.2, 9.4.1, 9.6.0, 9.5.1, 9.4.2, 9.3.3, 9.4.3, 9.4.4, 9.4.5, 9.4.6, 9.4.7, 9.4.8, 9.4.9, 9.4.10, 9.4.11, 9.4.12, 9.4.13, 9.4.14, 9.4.15
    • None
    • 7.5
    • High
    • CVE-2022-40146
    • Atlassian (Internal)
    • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    • SSRF (Server-Side Request Forgery)
    • Jira Software Data Center, Jira Software Server

      This High severity org.apache.xmlgraphics:batik-bridge Dependency vulnerability was introduced in versions 8.20.0, 8.22.0, 9.0.0, 9.1.0, 9.2.0, 9.3.0, 9.4.0, 9.5.0, and 9.6.0 of Jira Software Data Center and Server.

      This org.apache.xmlgraphics:batik-bridge Dependency vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction.

      Atlassian recommends that Jira Software Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:

       

      Affected versions Fixed versions
      9.12.0 to 9.12.3 9.14.1 recommended or 9.14.0 or 9.12.4 LTS
      9.11.0 to 9.11.3 9.14.1 recommended or 9.14.0 or 9.12.4 LTS
      9.10.0 to 9.10.2 9.14.1 recommended or 9.14.0 or 9.12.4 LTS
      9.9.0 to 9.9.2 9.14.1 recommended or 9.14.0 or 9.12.4 LTS
      9.8.0 to 9.8.2 9.14.1 recommended or 9.14.0 or 9.12.4 LTS
      9.7.0 to 9.7.2 9.14.1 recommended or 9.14.0 or 9.12.4 LTS
      9.6.0 9.14.1 recommended or 9.14.0 or 9.12.4 LTS
      9.5.0 to 9.5.1 9.14.1 recommended or 9.14.0 or 9.12.4 LTS
      9.4.0 to 9.4.15 LTS 9.14.1 recommended or 9.14.0 or 9.12.4 LTS or 9.4.16 LTS
      9.3.0 to 9.3.3 9.14.1 recommended or 9.14.0 or 9.12.4 LTS or 9.4.16 LTS
      9.2.0 to 9.2.1 9.14.1 recommended or 9.14.0 or 9.12.4 LTS or 9.4.16 LTS
      9.1.0 to 9.1.1 9.14.1 recommended or 9.14.0 or 9.12.4 LTS or 9.4.16 LTS
      9.0.0 9.14.1 recommended or 9.14.0 or 9.12.4 LTS or 9.4.16 LTS
      Any earlier versions 9.14.1 recommended or 9.14.0 or 9.12.4 LTS or 9.4.16 LTS

       

      See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version of Jira Software Data Center and Server from the download center (https://www.atlassian.com/software/jira/download-archives).

      The National Vulnerability Database provides the following description for this vulnerability: Server-Side Request Forgery (SSRF) vulnerability in Batik of Apache XML Graphics allows an attacker to access files using a Jar url. This issue affects Apache XML Graphics Batik 1.14.

            [JSWSERVER-25799] SSRF (Server-Side Request Forgery) org.apache.xmlgraphics:batik-bridge Dependency in Jira Software Data Center and Server

            Why does https://www.atlassian.com/trust/data-protection/vulnerabilities not show this vulnerability (CVE-2022-40146) for Jira Software Data Center 9.12.2, but the table in this issue shows "9.12.0 to 9.12.3" as affected versions?

            Greg Pflaum added a comment - Why does  https://www.atlassian.com/trust/data-protection/vulnerabilities not show this vulnerability (CVE-2022-40146) for Jira Software Data Center 9.12.2, but the table in this issue shows "9.12.0 to 9.12.3" as affected versions?

            Is there a known attack vector for this, or any other mitigation that can be applied to prevent this from being exploited?

            Jason Kemp added a comment - Is there a known attack vector for this, or any other mitigation that can be applied to prevent this from being exploited?

              Unassigned Unassigned
              security-metrics-bot Security Metrics Bot
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: