# CVE-2020-14183: Information disclosure in Jira Server

> Remote attackers with limited privileges can view the Support Entitlement Number via HTTP headers, exposing sensitive instance information.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-c7mj-gq36-7x33

## What is CVE-2020-14183?

CVE-2020-14183 is a medium-severity vulnerability in Atlassian Jira, published on 6 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected versions of Jira Server & Data Center allow a remote attacker with limited (non-admin) privileges to view a Jira instance's Support Entitlement Number (SEN) via an Information Disclosure vulnerability in the HTTP Response headers. The affected versions are before version 7.13.18, from version 8.0.0 before 8.5.9, and from version 8.6.0 before 8.12.1.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Atlassian Jira.

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

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

## Is CVE-2020-14183 being exploited?

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

## Other vulnerabilities in Atlassian Jira

- [CVE-2020-14172](https://insights.sbomify.com/CVE-2020-14172/): Deserialization in Jira Server (critical 9.8)
- [CVE-2019-20409](https://insights.sbomify.com/CVE-2019-20409/): Code injection in Jira Server (critical 9.8)
- [CVE-2017-5983](https://insights.sbomify.com/CVE-2017-5983/): Deserialization in n/a (critical 9.8)
- [CVE-2010-1165](https://insights.sbomify.com/CVE-2010-1165/): Code injection in n/a (critical 9.0)
- [CVE-2016-4319](https://insights.sbomify.com/CVE-2016-4319/): Cross-site request forgery in Atlassian JIRA Server before 7.1.9 (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14183 is a medium-severity vulnerability in Atlassian Jira, published on 6 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14183 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-14183/ (Markdown: https://insights.sbomify.com/CVE-2020-14183/index.md)
```

## Sources

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

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