# CVE-2020-36237: Information disclosure in Jira Data Center

> Unauthenticated attackers can view custom field options in Atlassian Jira Server and Data Center via an information disclosure vulnerability.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x467-qjmw-8pjc

## What is CVE-2020-36237?

CVE-2020-36237 is a medium-severity vulnerability in Atlassian Jira, published on 14 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of Atlassian Jira Server and Data Center allow unauthenticated remote attackers to view custom field options via an Information Disclosure vulnerability in the /rest/api/2/customFieldOption/ endpoint. The affected versions are before version 8.15.0.

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

It affects 2 products.


Products: Atlassian Data Center, Atlassian Jira.

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

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

## Is CVE-2020-36237 being exploited?

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

## Other vulnerabilities in Atlassian Jira

- [CVE-2017-18113](https://insights.sbomify.com/CVE-2017-18113/): Code injection in Jira Data Center (high 8.8)
- [CVE-2021-41312](https://insights.sbomify.com/CVE-2021-41312/): Auth bypass in Jira Data Center (high 7.5)
- [CVE-2021-39123](https://insights.sbomify.com/CVE-2021-39123/): Denial of service in Jira Data Center (high 7.5)
- [CVE-2021-39113](https://insights.sbomify.com/CVE-2021-39113/): Missing authorization in Jira Data Center (high 7.5)
- [CVE-2021-43947](https://insights.sbomify.com/CVE-2021-43947/): Code injection in Jira Data Center (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36237 is a medium-severity vulnerability in Atlassian Jira, published on 14 Feb 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-36237 in the wild and no public exploit code.

Affected product: Atlassian Jira. 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-36237/ (Markdown: https://insights.sbomify.com/CVE-2020-36237/index.md)
```

## Sources

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

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