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

DoS (Denial of Service) org.xerial.snappy:snappy-java Dependency in Jira Software Data Center and Server

    XMLWordPrintable

Details

    • Public Security Vulnerability
    • Resolution: Fixed
    • High
    • 9.4.16, 9.13.0, 9.12.3
    • 8.20.0, 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.7.0, 9.4.4, 9.8.0, 9.7.1, 9.4.5, 9.9.0, 9.4.6, 9.8.1, 9.4.7, 9.10.0, 9.9.1, 9.4.8, 9.11.0, 9.4.9, 9.10.1, 9.12.0, 9.4.10, 9.11.1, 9.7.2, 9.8.2, 9.9.2, 9.11.2, 9.4.11, 9.10.2, 9.4.12, 9.11.3, 9.12.1, 9.4.13, 9.4.14, 9.4.15, 9.12.2
    • None
    • 7.5
    • High
    • CVE-2023-34455
    • Atlassian (Internal)
    • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    • DoS (Denial of Service)
    • Jira Software Data Center, Jira Software Server

    Description

      This High severity org.xerial.snappy:snappy-java 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, 9.6.0, 9.7.0, 9.8.0, 9.9.0, 9.10.0, 9.11.0, and 9.12.0 of Jira Software Data Center and Server.

      This org.xerial.snappy:snappy-java 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:N/I:N/A:H allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation which has no impact to confidentiality, no impact to integrity, high 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.2 9.14.1 recommended or 9.13.0 or 9.12.3 LTS
      9.11.0 to 9.11.3 9.14.1 recommended or 9.13.0 or 9.12.3 LTS
      9.10.0 to 9.10.2 9.14.1 recommended or 9.13.0 or 9.12.3 LTS
      9.9.0 to 9.9.2 9.14.1 recommended or 9.13.0 or 9.12.3 LTS
      9.8.0 to 9.8.2 9.14.1 recommended or 9.13.0 or 9.12.3 LTS
      9.7.0 to 9.7.2 9.14.1 recommended or 9.13.0 or 9.12.3 LTS
      9.6.0 9.14.1 recommended or 9.13.0 or 9.12.3 LTS
      9.5.0 to 9.5.1 9.14.1 recommended or 9.13.0 or 9.12.3 LTS
      9.4.0 to 9.4.15 LTS 9.14.1 recommended or 9.12.3 LTS or 9.4.16 LTS
      9.3.0 to 9.3.3 9.14.1 recommended or 9.12.3 LTS or 9.4.16 LTS
      9.2.0 to 9.2.1 9.14.1 recommended or 9.12.3 LTS or 9.4.16 LTS
      9.1.0 to 9.1.1 9.14.1 recommended or 9.12.3 LTS or 9.4.16 LTS
      9.0.0 9.14.1 recommended or 9.12.3 LTS or 9.4.16 LTS
      Any earlier versions 9.14.1 recommended or 9.12.3 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: snappy-java is a fast compressor/decompressor for Java. Due to use of an unchecked chunk length, an unrecoverable fatal error can occur in versions prior to 1.1.10.1.

      The code in the function hasNextChunk in the fileSnappyInputStream.java checks if a given stream has more chunks to read. It does that by attempting to read 4 bytes. If it wasn’t possible to read the 4 bytes, the function returns false. Otherwise, if 4 bytes were available, the code treats them as the length of the next chunk.

      In the case that the `compressed` variable is null, a byte array is allocated with the size given by the input data. Since the code doesn’t test the legality of the `chunkSize` variable, it is possible to pass a negative number (such as 0xFFFFFFFF which is -1), which will cause the code to raise a `java.lang.NegativeArraySizeException` exception. A worse case would happen when passing a huge positive value (such as 0x7FFFFFFF), which would raise the fatal `java.lang.OutOfMemoryError` error.

      Version 1.1.10.1 contains a patch for this issue.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: