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

DoS (Denial of Service) org.jsoup:jsoup in Jira Software Data Center and Server

    • 7.5
    • High
    • CVE-2021-37714
    • 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

      This High severity Third-Party Dependency vulnerability was introduced in versions 8.20.0, 9.4.0, 9.5.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.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:

      • 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: jsoup is a Java library for working with HTML. Those using jsoup versions prior to 1.14.2 to parse untrusted HTML or XML may be vulnerable to DOS attacks. If the parser is run on user supplied input, an attacker may supply content that causes the parser to get stuck (loop indefinitely until cancelled), to complete more slowly than usual, or to throw an unexpected exception. This effect may support a denial of service attack. The issue is patched in version 1.14.2. There are a few available workarounds. Users may rate limit input parsing, limit the size of inputs based on system resources, and/or implement thread watchdogs to cap and timeout parse runtimes.

            [JSWSERVER-25410] DoS (Denial of Service) org.jsoup:jsoup in Jira Software Data Center and Server

            Hi, 

            Atlassian support informed us, that this would also be fixed in 9.4.14. similar to the other CVEs, however I don't see it as a fix version yet.

            Please clarify.

            Oliver Lutz added a comment - Hi,  Atlassian support informed us, that this would also be fixed in 9.4.14. similar to the other CVEs, however I don't see it as a fix version yet. Please clarify.

            We just upgraded to version 9.4.11 does this mean we are affected and is there a workaround if we cant upgrade.

            Noni Khutane added a comment - We just upgraded to version 9.4.11 does this mean we are affected and is there a workaround if we cant upgrade.

            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 12/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 18 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 12/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 18 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

            Dear Atlassian Team,

            Please inform us urgently whether only JIRA 8.20.0 is actually affected or all 8.20.x versions

            Regards
            Hannes

            Hannes Medwed added a comment - Dear Atlassian Team, Please inform us urgently whether only JIRA 8.20.0 is actually affected or all 8.20.x versions Regards Hannes

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

                Created:
                Updated:
                Resolved: