Skip to content
Fencer Intel
critical 9.8

CVE-2020-36239 in the critical feed json

Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0…

published 5y ago modified 4mo ago also EUVD-2020-23784

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
49.8%
EPSS 49.8% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0 before 8.17.0 and Jira Service Management Data Center from version 2.0.2 before 4.5.16, from version 4.6.0 before 4.13.8, and from version 4.14.0 before 4.17.0 exposed a Ehcache RMI network service which attackers, who can connect to the service, on port 40001 and potentially 40011[0][1], could execute arbitrary code of their choice in Jira through deserialization due to a missing authentication vulnerability. While Atlassian strongly suggests restricting access to the Ehcache ports to only Data Center instances, fixed versions of Jira will now require a shared secret in order to allow access to the Ehcache service. [0] In Jira Data Center, Jira Core Data Center, and Jira Software Data Center versions prior to 7.13.1, the Ehcache object port can be randomly allocated. [1] In Jira Service Management Data Center versions prior to 3.16.1, the Ehcache object port can be randomly allocated.

Patch / fix

  • Atlassian Jira Data Center 8.5.16, 8.13.8, 8.17.0
  • Atlassian Jira Core Data Center 8.5.16, 8.13.8, 8.17.0
  • Atlassian Jira Software Data Center 8.5.16, 8.13.8, 8.17.0
  • Atlassian Jira Service Management Data Center 4.5.16, 4.13.8, 4.17.0
  • atlassian jira_data_center 8.5.16, 8.13.8, 8.17.0
  • atlassian jira_service_desk 4.5.16, 4.13.8
  • atlassian jira_service_management 4.17.0

Is CVE-2020-36239 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

49.82% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Atlassian Jira Data Center
  • Atlassian Jira Core Data Center
  • Atlassian Jira Software Data Center
  • Atlassian Jira Service Management Data Center
  • atlassian jira_data_center
  • atlassian jira_service_desk
  • atlassian jira_service_management

Classification

Weakness
  • CWE-862 Missing Authorization
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.