NVD / CVE Program· CNA atlassian

CVE-2020-36239: 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…

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

Noroxi assessment

Priority: Plan (action score 54/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 49.8% (FIRST EPSS); higher than 98.9% of all records.
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.
According to CISA the attack is automatable: targets can be found by mass scanning.
According to the record, no fixed version is available yet.

Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

BDU:2021-04000

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

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.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

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

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

Affected versions · NVD (6)

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

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…KEV
81Now
CVE-2022-0540A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP…
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…
47Plan

Published before and after this one in the same product

← EarlierCVE-2020-14179Sep 20, 2020 · Affected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom…
44Plan
← EarlierCVE-2021-26080Jun 7, 2021 · EditworkflowScheme.jspa in Jira Server and Jira Data Center before version 8.5.14, and from version 8.6.0 before version 8.13.6, and from 8.
24Monitor
Later →CVE-2021-39116Sep 7, 2021 · Affected versions of Atlassian Jira Server and Data Center allow remote attackers to impact the application's availability via a Denial of…
22Monitor

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).

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…
29Monitor

Bug bounty scope