dbcve.org
JiraApplication · Atlassian

CVE-2019-20410

MEDIUM · 6.5 CVSS v3.1 Published 2020-06-29
Fix available
A fix is available. Upgrade to 7.6.17 / 7.13.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 view sensitive information via an Information Disclosure vulnerability in the comment restriction feature. The affected versions are before version 7.6.17, from version 7.7.0 before 7.13.9, and from version 8.0.0 before 8.4.2.

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

This is an information disclosure vulnerability in Atlassian Jira Server and Data Center's comment restriction feature. The flaw allows remote attackers to bypass the intended access controls on comments and view sensitive information they should not have access to. The vulnerability affects multiple version branches (7.x before 7.6.17 and 7.13.9, 8.x before 8.4.2).

MitigationUpgrade Jira to version 7.6.17, 7.13.9, 8.4.2 or later to patch the vulnerability. As a temporary workaround, review and restrict user permissions on comment-related operations until the upgrade can be completed.

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:< 7.6.17
Jira Data CenterApplication
Affected:>= 7.7.0, < 7.13.9>= 8.0.0, < 8.4.2
Jira ServerApplication
Affected:>= 7.7.0, < 7.13.9>= 8.0.0, < 8.4.2
Jira Software Data CenterApplication
Affected:< 7.6.17

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check Jira version from the web interface
    Log into Jira as an administrator and look at the footer of any Jira page. The version number is displayed there (for example: 'Jira v8.3.1 (701000)').
    Affected if The version displayed is less than 7.6.17, or falls between 7.7.0 and 7.13.9, or falls between 8.0.0 and 8.4.2.
  2. Check Jira version via API
    Send an authenticated GET request to the /rest/api/2/serverInfo endpoint. For example: curl -u admin:password https://jira.example.com/rest/api/2/serverInfo
    Affected if The 'version' field in the JSON response matches the affected version ranges described above.
  3. Determine Jira deployment type
    Look for 'Data Center' or 'Server' designation in the Jira footer or in the /rest/api/2/serverInfo response under the 'deploymentType' field.
    Affected if The deployment is Server or Data Center and the version falls within the affected ranges for that deployment type.
  4. Verify comment restriction feature is in use
    Navigate to a project, open an issue, and check if any comments exist with restricted visibility (visible only to certain users or groups). Go to project settings > issue security or check individual comment permissions.
    Affected if Comment restrictions are configured and the Jira version is within the affected ranges.

A user is affected if their Jira installation version is less than 7.6.17, between 7.7.0 and 7.13.9, or between 8.0.0 and 8.4.2, and the comment restriction feature is in use.

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 7.6.17 / 7.13.9 / 8.4.2 or later
Fixed in 7.6.177.13.98.4.2
Interim mitigation

Upgrade Jira to version 7.6.17, 7.13.9, 8.4.2 or later to patch the vulnerability. As a temporary workaround, review and restrict user permissions on comment-related operations until the upgrade can be completed.

Fix this in Jira Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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