-
Public Security Vulnerability
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
8.20.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, 9.11.1, 9.11.2
-
None
-
7.5
-
High
-
CVE-2020-36518
-
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: jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.
[JSWSERVER-25406] DoS (Denial of Service) com.fasterxml.jackson.core in Jira Software Data Center and Server
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
Dear Atlassian Team,
Please inform us urgently whether only JIRA 8.20.0 is actually affected or all 8.20.x versions
Regards
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