dbcve.org
Jira Data CenterApplication · Atlassian

CVE-2024-21685

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-18
Fix available
A fix is available. Upgrade to 9.4.21 / 9.12.8 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated information disclosure vulnerability in Jira Core Data Center allows attackers to view sensitive information with high confidentiality impact. The vulnerability was introduced in versions 9.4.0, 9.12.0, and 9.15.0 and requires user interaction to exploit.

MitigationUpgrade Jira Core Data Center to version 9.4.21+, 9.12.8+, or 9.16.0+ depending on your current release line to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jira Data CenterApplication
Affected:>= 9.4.0, < 9.4.21>= 9.12.0, < 9.12.8>= 9.15.0, < 9.16.0
Jira ServerApplication
Affected:>= 9.4.0, < 9.4.21>= 9.12.0, < 9.12.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jira product type
    Access the Jira administration console or check the installation to determine if you are running Jira Data Center or Jira Server. The about page at /about.jspa displays the product type.
    Affected if Running Jira Data Center or Jira Server
  2. Determine installed Jira version
    Navigate to Jira administration > System > Troubleshooting and support > About, or access the /about.jspa page. The version number is displayed in the format X.Y.Z.
    Affected if Version falls within any of the affected ranges: 9.4.0 to 9.4.20, 9.12.0 to 9.12.7, or 9.15.0 to 9.15.x (below 9.16.0)
  3. Verify version is in affected range
    Compare your installed version number against the affected version ranges. For Jira Data Center: 9.4.0-9.4.20, 9.12.0-9.12.7, or 9.15.0-9.15.x. For Jira Server: 9.4.0-9.4.20 or 9.12.0-9.12.7.
    Affected if Installed version is 9.4.0 through 9.4.20, 9.12.0 through 9.12.7, or 9.15.0 through 9.15.x (below 9.16.0)

Your Jira instance is affected if it is running Jira Data Center or Server version 9.4.0-9.4.20, 9.12.0-9.12.7, or 9.15.0-9.15.x.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.4.21 / 9.12.8 / 9.16.0 or later
Fixed in 9.4.219.12.89.16.0
Interim mitigation

Upgrade Jira Core Data Center to version 9.4.21+, 9.12.8+, or 9.16.0+ depending on your current release line to remediate this vulnerability.

Recommended fix High confidence

Jira Data Center/Server 9.4.21+, 9.12.8+, or 9.16.0+ (preferably latest stable 9.16.x)

  1. Back up your Jira instance and database before upgrading
  2. Download the appropriate fixed version of Jira from Atlassian's official download center
  3. For Jira Data Center 9.4.x: Upgrade to version 9.4.21 or later
  4. For Jira Data Center 9.12.x: Upgrade to version 9.12.8 or later
  5. For Jira Data Center 9.15.x: Upgrade to version 9.16.0 or later
  6. For Jira Server 9.4.x: Upgrade to version 9.4.21 or later
  7. For Jira Server 9.12.x: Upgrade to version 9.12.8 or later
  8. Verify the upgrade was successful by checking the Jira version in the administration console
Caveat Standard Atlassian upgrade considerations apply - review release notes for migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jira Data Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21685 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data