dbcve.org
JiraApplication · Atlassian

CVE-2019-20898

HIGH · 7.5 CVSS v3.1 Published 2020-07-13
Fix available
A fix is available. Upgrade to 8.8.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to access sensitive information without being authenticated in the Global permissions screen. The affected versions are before version 8.8.0.

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

Affected versions of Atlassian Jira Server and Data Center before 8.8.0 contain an unauthenticated information disclosure vulnerability in the Global permissions screen, allowing remote attackers to access sensitive information without any authentication.

MitigationUpgrade Jira Server or Data Center to version 8.8.0 or later 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
JiraApplication
Affected:< 8.8.0
Jira Software Data CenterApplication
Affected:< 8.8.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 installation version
    Access the Jira administration console and navigate to Administration > System > Troubleshooting and support tools > System info, or query the REST endpoint /rest/api/2/serverInfo to retrieve the version number
    Affected if The displayed version is lower than 8.8.0
  2. Confirm Jira edition
    Check whether the instance is Jira Server or Jira Software Data Center using the same system info screen or the application header
    Affected if The edition is Jira Server or Jira Software Data Center and the version is below 8.8.0
  3. Verify remote access exposure
    Determine if the Jira instance is accessible over the network to unauthenticated users by attempting to access the Global permissions screen at /secure/admin/ViewGlobalPermissions.jspa without logging in
    Affected if The Global permissions screen loads without requiring authentication, exposing sensitive permission configuration details

The environment is affected if the installed Jira Server or Jira Software Data Center version is below 8.8.0 and the Global permissions screen is accessible without authentication.

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.

From vendor data
Upgrade available Upgrade to 8.8.0 or later
Fixed in 8.8.0
Interim mitigation

Upgrade Jira Server or Data Center to version 8.8.0 or later to remediate this vulnerability.

Fix this in Jira Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA2.0 h
23.0 hours of engineering $4,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-20898 — 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-2019-20898 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