# CVE-2024-21685: Information disclosure in Jira Core Data Center

> Unauthenticated attackers can view sensitive information in Jira Core Data Center, requiring an upgrade to mitigate confidentiality risks.

- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jun 2024
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-j6h8-65gx-v495

## What is CVE-2024-21685?

CVE-2024-21685 is a high-severity vulnerability in Atlassian Jira Data Center, published on 18 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

This High severity Information Disclosure vulnerability was introduced in versions 9.4.0, 9.12.0, and 9.15.0 of Jira Core Data Center. 
	
	This Information Disclosure vulnerability, with a CVSS Score of 7.4, allows an unauthenticated attacker to view sensitive information via an Information Disclosure vulnerability which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires user interaction. 
	
	Atlassian recommends that Jira Core Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:
		
		Jira Core Data Center 9.4: Upgrade to a release greater than or equal to 9.4.21
		
		Jira Core Data Center 9.12: Upgrade to a release greater than or equal to 9.12.8
		
		Jira Core Data Center 9.16: Upgrade to a release greater than or equal to 9.16.0
		
		
	
	See the release notes. You can download the latest version of Jira Core Data Center from the download center. 
	
	This vulnerability was found internally.

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

## Which versions are affected by CVE-2024-21685?

It affects 2 products.


Products: Atlassian Jira Data Center, Atlassian Jira Server.

## How do I fix CVE-2024-21685?

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

## Is CVE-2024-21685 being exploited?

There is no known exploitation of CVE-2024-21685 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-2020-36239](https://insights.sbomify.com/CVE-2020-36239/): Deserialization in Jira Core Data Center (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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-21685 and fix it if it is affected.

What it is: CVE-2024-21685 is a high-severity vulnerability in Atlassian Jira Data Center, published on 18 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-21685 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-2024-21685/ (Markdown: https://insights.sbomify.com/CVE-2024-21685/index.md)
```

## Sources

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

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