9.8
CRITICAL
CVE-2020-36239
"Atlassian Jira Remote Code Execution via Deserialization"
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.

INFO

Published Date :

July 29, 2021, 11:15 a.m.

Last Modified :

Aug. 1, 2022, 4:32 p.m.

Remotely Exploitable :

Yes !

Impact Score :

5.9

Exploitability Score :

3.9
Public PoC/Exploit Available at Github

CVE-2020-36239 has a 3 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

Affected Products

The following products are affected by CVE-2020-36239 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Atlassian jira_data_center
2 Atlassian jira_service_desk
3 Atlassian jira_service_management
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2020-36239.

URL Resource
https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html Patch Vendor Advisory
https://jira.atlassian.com/browse/JRASERVER-72566 Issue Tracking Vendor Advisory
https://jira.atlassian.com/browse/JSDSERVER-8454 Issue Tracking Vendor Advisory

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

None

Updated: 2 years, 3 months ago
0 stars 0 fork 0 watcher
Born at : May 20, 2022, 4:01 p.m. This repo has been linked 1 different CVEs too.

Programmatically create hunting rules for deserialization exploitation with multiple keywords, gadget chains, object types, encodings, and rule types

deserialization yara snort snort-rules-generate yara-rule-generator ysoserial

Python YARA PowerShell Shell

Updated: 3 weeks, 4 days ago
136 stars 19 fork 19 watcher
Born at : Dec. 7, 2021, 1:37 p.m. This repo has been linked 7 different CVEs too.

The cheat sheet about Java Deserialization vulnerabilities

javadeser java-deserialization pentesting

Updated: 1 week, 6 days ago
3011 stars 537 fork 537 watcher
Born at : Feb. 23, 2016, 10:28 p.m. This repo has been linked 168 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2020-36239 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2020-36239 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by [email protected]

    May. 14, 2024

    Action Type Old Value New Value
  • Reanalysis by [email protected]

    Aug. 01, 2022

    Action Type Old Value New Value
    Changed CPE Configuration OR *cpe:2.3:a:atlassian:core_data_center:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 8.5.16 *cpe:2.3:a:atlassian:core_data_center:*:*:*:*:*:*:*:* versions from (including) 8.6.0 up to (excluding) 8.13.8 *cpe:2.3:a:atlassian:core_data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 up to (excluding) 8.17.0 *cpe:2.3:a:atlassian:data_center:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 8.5.16 *cpe:2.3:a:atlassian:data_center:*:*:*:*:*:*:*:* versions from (including) 8.6.0 up to (excluding) 8.13.8 *cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 up to (excluding) 8.17.0 *cpe:2.3:a:atlassian:service_management_data_center:*:*:*:*:*:*:*:* versions from (including) 2.0.2 up to (excluding) 4.5.16 *cpe:2.3:a:atlassian:service_management_data_center:*:*:*:*:*:*:*:* versions from (including) 4.6.0 up to (excluding) 4.13.8 *cpe:2.3:a:atlassian:service_management_data_center:*:*:*:*:*:*:*:* versions from (including) 4.14.0 up to (excluding) 4.17.0 *cpe:2.3:a:atlassian:software_data_center:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 8.5.16 *cpe:2.3:a:atlassian:software_data_center:*:*:*:*:*:*:*:* versions from (including) 8.6.0 up to (excluding) 8.13.8 *cpe:2.3:a:atlassian:software_data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 up to (excluding) 8.17.0 OR *cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 8.5.16 *cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:* versions from (including) 8.6.0 up to (excluding) 8.13.8 *cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 up to (excluding) 8.17.0 *cpe:2.3:a:atlassian:jira_service_desk:*:*:*:*:data_center:*:*:* versions from (including) 2.0.2 up to (excluding) 4.5.16 *cpe:2.3:a:atlassian:jira_service_desk:*:*:*:*:data_center:*:*:* versions from (including) 4.6.0 up to (excluding) 4.13.8 *cpe:2.3:a:atlassian:jira_service_management:*:*:*:*:data_center:*:*:* versions from (including) 4.14.0 up to (excluding) 4.17.0
  • Reanalysis by [email protected]

    Jul. 15, 2022

    Action Type Old Value New Value
    Removed CWE NIST CWE-862
    Added CWE NIST CWE-306
  • CPE Deprecation Remap by [email protected]

    Mar. 30, 2022

    Action Type Old Value New Value
    Changed CPE Configuration OR *cpe:2.3:a:atlassian:data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 from (excluding) 8.17.0 OR *cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 from (excluding) 8.17.0
  • Initial Analysis by [email protected]

    Aug. 11, 2021

    Action Type Old Value New Value
    Added CVSS V2 NIST (AV:N/AC:L/Au:N/C:P/I:P/A:P)
    Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    Changed Reference Type https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html No Types Assigned https://confluence.atlassian.com/adminjiraserver/jira-data-center-and-jira-service-management-data-center-security-advisory-2021-07-21-1063571388.html Patch, Vendor Advisory
    Changed Reference Type https://jira.atlassian.com/browse/JRASERVER-72566 No Types Assigned https://jira.atlassian.com/browse/JRASERVER-72566 Issue Tracking, Vendor Advisory
    Changed Reference Type https://jira.atlassian.com/browse/JSDSERVER-8454 No Types Assigned https://jira.atlassian.com/browse/JSDSERVER-8454 Issue Tracking, Vendor Advisory
    Added CWE NIST CWE-862
    Added CPE Configuration OR *cpe:2.3:a:atlassian:core_data_center:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 8.5.16 *cpe:2.3:a:atlassian:core_data_center:*:*:*:*:*:*:*:* versions from (including) 8.6.0 up to (excluding) 8.13.8 *cpe:2.3:a:atlassian:core_data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 up to (excluding) 8.17.0 *cpe:2.3:a:atlassian:data_center:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 8.5.16 *cpe:2.3:a:atlassian:data_center:*:*:*:*:*:*:*:* versions from (including) 8.6.0 up to (excluding) 8.13.8 *cpe:2.3:a:atlassian:data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 up to (excluding) 8.17.0 *cpe:2.3:a:atlassian:service_management_data_center:*:*:*:*:*:*:*:* versions from (including) 2.0.2 up to (excluding) 4.5.16 *cpe:2.3:a:atlassian:service_management_data_center:*:*:*:*:*:*:*:* versions from (including) 4.6.0 up to (excluding) 4.13.8 *cpe:2.3:a:atlassian:service_management_data_center:*:*:*:*:*:*:*:* versions from (including) 4.14.0 up to (excluding) 4.17.0 *cpe:2.3:a:atlassian:software_data_center:*:*:*:*:*:*:*:* versions from (including) 6.3.0 up to (excluding) 8.5.16 *cpe:2.3:a:atlassian:software_data_center:*:*:*:*:*:*:*:* versions from (including) 8.6.0 up to (excluding) 8.13.8 *cpe:2.3:a:atlassian:software_data_center:*:*:*:*:*:*:*:* versions from (including) 8.14.0 up to (excluding) 8.17.0
  • CVE Modified by [email protected]

    Jul. 30, 2021

    Action Type Old Value New Value
    Changed 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. 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.
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2020-36239 is associated with the following CWEs:

Exploit Prediction

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.

1.02 }} 0.05%

score

0.83881

percentile

CVSS31 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability