CVE-2024-21685 [Medium] | Information Disclosure in Jira Data Center

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.98%	0.44%	-0.55%
2	2025-11-07	0.73%	0.98%	+0.26%
3	2025-09-09	—	0.73%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.98%

0.44%

-0.55%

2025-11-07

0.73%

0.98%

+0.26%

2025-09-09

—

0.73%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.8	3.6	[email protected]
7.4	3.0	HIGH	`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.8	4.0	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.5

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.8

3.6

[email protected]

7.4

3.0

HIGH

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.8

4.0

[email protected]

Affected software / configurations for CVE-2024-21685

Vendor	Product	Version	Raw CPE
atlassian	jira_data_center	>= 9.4.0, < 9.4.21	cpe:2.3:a:atlassian:jira_data_center::::::::
atlassian	jira_data_center	>= 9.12.0, < 9.12.8	cpe:2.3:a:atlassian:jira_data_center::::::::
atlassian	jira_data_center	>= 9.15.0, < 9.16.0	cpe:2.3:a:atlassian:jira_data_center::::::::
atlassian	jira_server	>= 9.4.0, < 9.4.21	cpe:2.3:a:atlassian:jira_server::::::::
atlassian	jira_server	>= 9.12.0, < 9.12.8	cpe:2.3:a:atlassian:jira_server::::::::

References for CVE-2024-21685

URL	Tags
https://confluence.atlassian.com/pages/viewpage.action?pageId=1409286211	Vendor Advisory
https://jira.atlassian.com/browse/JRASERVER-77713	Issue Tracking Vendor Advisory

URL

CVE-2024-21685

Exploit prediction scoring system (EPSS) score for CVE-2024-21685

Common vulnerability scoring system (CVSS) metrics for CVE-2024-21685

Weakness enumeration for CVE-2024-21685

Affected software / configurations for CVE-2024-21685

References for CVE-2024-21685