CVE-2020-36239

CRITICAL
9.8
CVSS Score
Published: July 29, 2021 at 10:12 AM UTC
Updated: June 17, 2026 at 03:15 AM UTC
3 products affected across 1 vendorJira Data CenterJira Service ManagementJira Service Desk

Using Jira Data Center by Atlassian?

Get instant alerts when new vulnerabilities affect Jira Data Center - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL9.8
Exploit prediction
EPSS 50%
SSVC
No known exploit

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 object port can be randomly allocated.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.3.0v ≥ 8.14.0v ≥ 8.6.0v < 8.13.8v < 8.17.0v < 8.5.166.3.0 ≤ v < 8.5.168.14.0 ≤ v < 8.17.08.6.0 ≤ v < 8.13.86.3.08.14.08.6.0
Affected range stops below 8.13.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.17.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.5.16, so it looks safe — our inference, not a vendor statement
2.0.2 ≤ v < 4.5.164.6.0 ≤ v < 4.13.82.0.24.6.0
Affected range stops below 4.13.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.16, so it looks safe — our inference, not a vendor statement
v ≥ 2.0.2v ≥ 4.14.0v ≥ 4.6.0v < 4.13.8v < 4.17.0v < 4.5.164.14.0 ≤ v < 4.17.02.0.24.14.04.6.0
Affected range stops below 4.13.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.17.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5.16, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitAutomatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

9.8CRITICALCISA-ADP
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-862CWE-306

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card