CVE-2020-36239· NVD / CVE Program· CNA atlassian

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 b

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.

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded

BDU:2021-04000

Published: Jul 29, 2021
Updated: Jun 16, 2026
EPSS: 49.8% · 99th percentile
CWE: CWE-862

Follow this CVE

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 15 / 30 · 49.8%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Affected systems

Vendor	Product	CPE
atlassian	jira data center	cpe:2.3:a:atlassian:jira_data_center
atlassian	jira service desk	cpe:2.3:a:atlassian:jira_service_desk
atlassian	jira service management	cpe:2.3:a:atlassian:jira_service_management

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

atlassian jira data center6.3.0 and later · before 8.5.16
atlassian jira data center8.6.0 and later · before 8.13.8
atlassian jira data center8.14.0 and later · before 8.17.0
atlassian jira service desk2.0.2 and later · before 4.5.16
atlassian jira service desk4.6.0 and later · before 4.13.8
atlassian jira service management4.14.0 and later · before 4.17.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.

Atlassian Jira Core Data Center
- 6.3.0 and later · before unspecifiedaffected
- unspecified and later · before 8.5.16affected
- 8.6.0 and later · before unspecifiedaffected
- unspecified and later · before 8.13.8affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.17.0affected
Atlassian Jira Data Center
- 6.3.0 and later · before unspecifiedaffected
- unspecified and later · before 8.5.16affected
- 8.6.0 and later · before unspecifiedaffected
- unspecified and later · before 8.13.8affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.17.0affected
Atlassian Jira Service Management Data Center
- 2.0.2 and later · before unspecifiedaffected
- unspecified and later · before 4.5.16affected
- 4.6.0 and later · before unspecifiedaffected
- unspecified and later · before 4.13.8affected
- 4.14.0 and later · before unspecifiedaffected
- unspecified and later · before 4.17.0affected
Atlassian Jira Software Data Center
- 6.3.0 and later · before unspecifiedaffected
- unspecified and later · before 8.5.16affected
- 8.6.0 and later · before unspecifiedaffected
- unspecified and later · before 8.13.8affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.17.0affected

Same product

atlassian: all records

Other highest-scoring records for the same primary product.

CVE-2021-26086Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal vulnerabilitKEV
81Now
CVE-2022-0540A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP reques
65This week
CVE-2022-26135A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the si
47Plan
CVE-2022-36801Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to inject arbitrary HTML or JavaScript via a Ref
44Plan
CVE-2020-14179Affected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom SLA
44Plan
CVE-2022-36799This issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days+1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2021-3912849 days apartAffected versions of Atlassian Jira Server or Data Center using the Jira Service Management addon allow remote attackers with JIRA Administr
29Monitor

Bug bounty scope

AtlassianBugcrowd · paid · up to $12,000

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-862 · Missing Authorization

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

Exploitation of Thunderbolt Protection FlawsCAPEC-665likelihood: Low · Very High

ATT&CK techniques

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records