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

Info Disclosure com.google.guava:guava in Jira Software Data Center and Server

    • 7.1
    • High
    • CVE-2023-2976
    • Atlassian (Internal)
    • CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
    • Information Disclosure
    • Jira Software Data Center, Jira Software Server

      This High severity Third-Party Dependency vulnerability was introduced in versions 8.20.0, 9.4.0, 9.6.0, 9.7.0, 9.8.0, 9.9.0, 9.10.0, and 9.11.0 of Jira Software Data Center and Server.

      This Third-Party Dependency vulnerability, with a CVSS Score of 7.1 and a CVSS Vector of CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N allows an authenticated attacker to expose assets in your environment susceptible to exploitation which has high impact to confidentiality, high 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:

      • Jira Software Data Center and Server 9.11: Upgrade to a release greater than or equal to 9.11.3

      See the release notes. You can download the latest version of Jira Software Data Center and Server from the download center.

      The National Vulnerability Database provides the following description for this vulnerability: Use of Java's default temporary directory for file creation in `FileBackedOutputStream` in Google Guava versions 1.0 to 31.1 on Unix systems and Android Ice Cream Sandwich allows other users and apps on the machine with access to the default Java temporary directory to be able to access the files created by the class.

      Even though the security vulnerability is fixed in version 32.0.0, we recommend using version 32.0.1 as version 32.0.0 breaks some functionality under Windows.

            [JSWSERVER-25415] Info Disclosure com.google.guava:guava in Jira Software Data Center and Server

            This story is also linked to [Issues resolved in 8.20.29 | Atlassian Support | Atlassian Documentation|https://confluence.atlassian.com/jirasoftware/issues-resolved-in-8-20-29-1332805745.html]

            So I assume all 8.20.x <8.20.29 are affected as wel. And fixed version should include 8.20.29?

            IT-operations added a comment - This story is also linked to [Issues resolved in 8.20.29 | Atlassian Support | Atlassian Documentation|https://confluence.atlassian.com/jirasoftware/issues-resolved-in-8-20-29-1332805745.html] So I assume all 8.20.x <8.20.29 are affected as wel. And fixed version should include 8.20.29?

            Please give us feedback , regarding 9.4

            Noni Khutane added a comment - Please give us feedback , regarding 9.4

            Hi Atlassian-Team,

            please clearify the fixed versions of this Vulnerability. You had this problems in the past, where you first mentioned the wrong fixed and affected versions and corrected them afterwards.

            I dont think that Jira 9.11.3 is the only fixed version.

            • this issue was created on 14/Nov/2023
            • The "fixed" Jira version was released on 09/Nov/2023
            • newest Jira LTS was released on 08/Nov/2023

            On the other hand, if the LTS really is affected, you have 20 days left to fix this issue. So could we can expect an new LTS release in the next days?

            Thanks and best regards

            Edgar König

            Edgar Koenig - SVA added a comment - Hi Atlassian-Team, please clearify the fixed versions of this Vulnerability. You had this problems in the past, where you first mentioned the wrong fixed and affected versions and corrected them afterwards. I dont think that Jira 9.11.3 is the only fixed version. this issue was created on 14/Nov/2023 The "fixed" Jira version was released on 09/Nov/2023 newest Jira LTS was released on 08/Nov/2023 On the other hand, if the LTS really is affected, you have 20 days left to fix this issue. So could we can expect an new LTS release in the next days? Thanks and best regards Edgar König

            Dear Atlassian-Team,

            could you please be slightly more specific regarding the fact which sub-versions are affected?
            How should "9.4.0" be interpreted? Does this mean all 9.4.x versions are affected or just 9.4.0? And will there be a fix also backported to the current LTS version 9.4. (you are just mentioning 9.11.3 as fixed version)?

            With the introduction of your monthly security bulleting you're aiming at a more clearly structured overview of security issues. But to be honest, it's slightly the opposite and at least partially more confusing ...

            Thanks & best regards,
            -Rainer

            Rainer Pöhlmann added a comment - Dear Atlassian-Team, could you please be slightly more specific regarding the fact which sub-versions are affected? How should "9.4.0" be interpreted? Does this mean all 9.4.x versions are affected or just 9.4.0? And will there be a fix also backported to the current LTS version 9.4. (you are just mentioning 9.11.3 as fixed version)? With the introduction of your monthly security bulleting you're aiming at a more clearly structured overview of security issues. But to be honest, it's slightly the opposite and at least partially more confusing ... Thanks & best regards, -Rainer

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

                Created:
                Updated:
                Resolved: