# CVE-2021-39113: Missing authorization in Jira Data Center

> Anonymous attackers can view cached content after losing permissions due to broken access control in the allowlist feature.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 30 Aug 2021
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-h2f3-6hhf-j7cc

## What is CVE-2021-39113?

CVE-2021-39113 is a high-severity missing authorization vulnerability in Atlassian Jira, published on 30 Aug 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 anonymous remote attackers to continue to view cached content even after losing permissions, via a Broken Access Control vulnerability in the allowlist feature. The affected versions are before version 8.13.9, and from version 8.14.0 before 8.18.0.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2021-39113?

It affects 4 products.


Products: Atlassian Data Center, Atlassian Jira, Atlassian Jira Data Center, Atlassian Jira Server.

## How do I fix CVE-2021-39113?

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

## Is CVE-2021-39113 being exploited?

There is no known exploitation of CVE-2021-39113 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-43947](https://insights.sbomify.com/CVE-2021-43947/): Code injection in Jira Data Center (high 7.2)
- [CVE-2021-26070](https://insights.sbomify.com/CVE-2021-26070/): Auth bypass in Jira Data Center (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-39113 and fix it if it is affected.

What it is: CVE-2021-39113 is a high-severity missing authorization vulnerability in Atlassian Jira, published on 30 Aug 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-2021-39113 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-2021-39113/ (Markdown: https://insights.sbomify.com/CVE-2021-39113/index.md)
```

## Sources

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

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