# CVE-2020-36239: Deserialization in Jira Core Data Center

> Attackers with network access to Ehcache ports can execute arbitrary code via deserialization due to missing authentication in Jira Data Center products.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2021
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-2xhw-jfhh-p475

## What is CVE-2020-36239?

CVE-2020-36239 is a critical unsafe deserialization vulnerability in Atlassian Jira Data Center, published on 29 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-36239?

It affects 3 products.


Products: Atlassian Jira Data Center, Atlassian Jira Service Desk, Atlassian Jira Service Management.

## How do I fix CVE-2020-36239?

No fix has been published for CVE-2020-36239 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36239 being exploited?

There is no known exploitation of CVE-2020-36239 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Jira Data Center

- [CVE-2021-26086](https://insights.sbomify.com/CVE-2021-26086/): Atlassian Jira Server and Data Center Path Traversal (medium 5.3, exploited in the wild)
- [CVE-2022-0540](https://insights.sbomify.com/CVE-2022-0540/): Auth bypass in Jira Core Server (critical 9.8)
- [CVE-2025-22167](https://insights.sbomify.com/CVE-2025-22167/): Path traversal in Jira Software Data Center (high 8.7)
- [CVE-2019-20419](https://insights.sbomify.com/CVE-2019-20419/): Other in Jira Server (high 7.8)
- [CVE-2024-21685](https://insights.sbomify.com/CVE-2024-21685/): Information disclosure in Jira Core Data Center (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36239 and fix it if it is affected.

What it is: CVE-2020-36239 is a critical unsafe deserialization vulnerability in Atlassian Jira Data Center, published on 29 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36239 in the wild and no public exploit code.

Affected product: Atlassian Jira Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36239/ (Markdown: https://insights.sbomify.com/CVE-2020-36239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36239
- OSV: https://osv.dev/vulnerability/CVE-2020-36239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36239/
Summaries are generated and may contain mistakes; the official description above is the record.