CVE-2020-36239
9.8 · CRITICALOverview
CVE-2020-36239 is a critical-severity vulnerability affecting atlassian jira_data_center. It was published on July 29, 2021 and has a CVSS 3.1 base score of 9.8 (CRITICAL).
This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical Description
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 o
Remediation
Check the references section for vendor advisories and patches from atlassian. Update jira_data_center to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| atlassian | jira_data_center | >= 6.3.0, < 8.5.16 | Affected |
| atlassian | jira_service_desk | >= 2.0.2, < 4.5.16 | Affected |
| atlassian | jira_service_management | >= 4.14.0, < 4.17.0 | Affected |
References
Frequently Asked Questions
What is CVE-2020-36239?
CVE-2020-36239 is a critical-severity vulnerability affecting atlassian jira_data_center. It was published on July 29, 2021 and has a CVSS 3.1 base score of 9.8 (CRITICAL).
How severe is CVE-2020-36239?
This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2020-36239?
Check the references section for vendor advisories and patches from atlassian. Update jira_data_center to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2020-36239?
CyberStrike's AI-powered security agents can automatically detect CVE-2020-36239 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related CRITICAL CVEs from 2020
View all →In ApexPro Telemetry Server, Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinic
In ApexPro Telemetry Server, Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinic
In ApexPro Telemetry Server Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinica
In ApexPro Telemetry Server Versions 4.2 and prior, CARESCAPE Telemetry Server v4.2 & prior, Clinica
Missing Authentication for Critical Function in the Bosch Video Streaming Gateway (VSG) allows an un
Deserialization of Untrusted Data in the BVMS Mobile Video Service (BVMS MVS) allows an unauthentica
NaCl in 2015 allowed the CLFLUSH instruction, making rowhammer attacks possible.
A remote code execution vulnerability exists in the way that the Microsoft Server Message Block 3.1.
Apache Commons Configuration uses a third-party library to parse YAML files which by default allows
UltraLog Express device management interface does not properly filter user inputted string in some s
A Use of Hard-coded Credentials vulnerability exists in the NFX250 Series for the vSRX Virtual Netwo
Beaker before 0.8.9 allows a sandbox escape, enabling system access and code execution. This occurs