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

Deserialization com.fasterxml.jackson.core:jackson-databind in Jira Software Data Center and Server

XMLWordPrintable

    • 7.5
    • High
    • CVE-2022-42004
    • Atlassian (Internal)
    • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    • Patch Management
    • 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: In FasterXML jackson-databind before 2.13.4, resource exhaustion can occur because of a lack of a check in BeanDeserializer._deserializeFromArray to prevent use of deeply nested arrays. An application is vulnerable only with certain customized choices for deserialization.

            [JSWSERVER-25409] Deserialization com.fasterxml.jackson.core:jackson-databind in Jira Software Data Center and Server

            Roberto Correa added a comment -

            Dear Atlassian team,

            Please could you clarify the sentence: "This High severity Third-Party Dependency vulnerability was introduced in versions 8.20.0,.."

            For me it is not clear if the vulnerability was in introduced in version 8.20.0 and remain in all later  8.20.x versions

            or

            if the vulnerability was only affects to version 8.20.0.

            Is the only fix available other than 9.11.3? Is not any planned fixing for 8.20.X?

            As a suggestion try to avoid the words " vulnerability was introduced" and use explicitly " vulnerability affected to". This will avoid misunderstandings.

            Looking forward to your feedback,

            Thanks in advance,

            Cheers,

            Roberto Correa

             

            Roberto Correa added a comment - Dear Atlassian team, Please could you clarify the sentence: "This High severity Third-Party Dependency vulnerability was introduced in versions 8.20.0,.." For me it is not clear if the vulnerability was in introduced in version 8.20.0 and remain in all later  8.20.x versions or if the vulnerability was only affects to version 8.20.0. Is the only fix available other than 9.11.3? Is not any planned fixing for 8.20.X? As a suggestion try to avoid the words " vulnerability was introduced" and use explicitly " vulnerability affected to". This will avoid misunderstandings. Looking forward to your feedback, Thanks in advance, Cheers, Roberto Correa  

            Yurim An added a comment -

            https://confluence.atlassian.com/security/security-bulletin-november-21-2023-1318881573.html

            According to a upper link, "All versions including and after 8.20.0"  need to be patched.

            I want to be sure of the meaning "And".

            Does it mean "All versions"+"after 8.20.0"? otherwise, only for after 8.20.0? 

            our version is 8.5.10. Is it needed to be patched?

            Yurim An added a comment - https://confluence.atlassian.com/security/security-bulletin-november-21-2023-1318881573.html According to a upper link, "All versions including and after 8.20.0"  need to be patched. I want to be sure of the meaning "And". Does it mean "All versions"+"after 8.20.0"? otherwise, only for after 8.20.0?  our version is 8.5.10. Is it needed to be patched?

            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

            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

            Suraj Nagesha added a comment - - edited

            Dear Atlassian Team,

            Echoing the comment by Rainer, Could you let us know the whether this fix is already available in other LTS releases? For e.g. 9.11.3 released on 9th November indicates the issue is fixed, where as other LTS Version for e.g. 9.4.12 released on 8th November (a day before the 9.11.3) do not have any information about the fix?

            How can we interpret the fixed version?

            Or this is fixed only in 9.11.3 and not in earlier LTS releases?

             

            https://confluence.atlassian.com/jirasoftware/issues-resolved-in-9-11-3-1319243033.html,

            https://confluence.atlassian.com/jirasoftware/issues-resolved-in-9-4-12-1318389243.html

            Regards

            Suraj

             

            Suraj Nagesha added a comment - - edited Dear Atlassian Team, Echoing the comment by Rainer, Could you let us know the whether this fix is already available in other LTS releases? For e.g. 9.11.3 released on 9th November indicates the issue is fixed, where as other LTS Version for e.g. 9.4.12 released on 8th November (a day before the 9.11.3) do not have any information about the fix? How can we interpret the fixed version? Or this is fixed only in 9.11.3 and not in earlier LTS releases?   https://confluence.atlassian.com/jirasoftware/issues-resolved-in-9-11-3-1319243033.html, https://confluence.atlassian.com/jirasoftware/issues-resolved-in-9-4-12-1318389243.html Regards Suraj  

            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

            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

            Uli Haas added a comment - - edited

            Is it already fixed in the LTS Version? (9.4.12) 

            Uli Haas added a comment - - edited Is it already fixed in the LTS Version? (9.4.12) 

            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

            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:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: