CVE-2020-36239
CRITICALEPSS 99th pctlDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 99% of all known CVEs.
References
Related Vulnerabilities
Other CWE-862 (Missing Authorization) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-39226 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2022-0543 | Critical | 10.0 | 99% | KEV | Fix |
| CVE-2021-21978 | Critical | 9.8 | 99% | - | Fix |
| CVE-2023-52163 | High | 8.8 | 97% | KEV | - |
| CVE-2022-1329 | High | 8.8 | 93% | - | - |
| CVE-2023-6875 | Critical | 9.8 | 90% | - | - |
Common questions
How do I fix CVE-2020-36239?
Upgrade Jira Service Management Long Term Support to 4.17.0 or later.
Is CVE-2020-36239 being actively exploited?
Not that we know of. CVE-2020-36239 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 46.7% is the estimated probability that it will be exploited in the next 30 days. That is higher than 99% of all scored CVEs.
How severe is CVE-2020-36239?
CVE-2020-36239 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2020-36239 affect?
Published advisories record a fix for Jira Service Management Long Term Support (Windows application). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2020-36239
Markdown
[](https://tridentstack.com/cve/CVE-2020-36239)HTML
<a href="https://tridentstack.com/cve/CVE-2020-36239"><img src="https://tridentstack.com/cve/badge/CVE-2020-36239.svg" alt="CVE-2020-36239"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.