dbcve.org
Data CenterApplication · Atlassian

CVE-2020-36286

MEDIUM · 5.3 CVSS v3.1 Published 2021-04-01
Fix available
A fix is available. Upgrade to 8.5.13 / 8.13.5 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The membersOf JQL search function in Jira Server and Data Center before version 8.5.13, from version 8.6.0 before version 8.13.5, and from version 8.14.0 before version 8.15.1 allows remote anonymous attackers to determine if a group exists & members of groups if they are assigned to publicly visible issue field.

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

The membersOf JQL search function in affected Jira Server and Data Center versions (before 8.5.13, 8.6.0-8.13.4, 8.14.0-8.15.0) allows remote anonymous attackers to enumerate group existence and membership by crafting specific JQL queries. Exploitation requires the attacker to be assigned to a publicly visible issue field.

MitigationUpgrade Jira Server/Data Center to version 8.5.13, 8.13.5, 8.15.1 or later. As a temporary measure, restrict public access to issue fields and disable anonymous access if possible.

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
Data CenterApplication
Affected:< 8.5.13
JiraApplication
Affected:< 8.5.13
Jira Data CenterApplication
Affected:>= 8.6.0, < 8.13.5>= 8.14.0, < 8.15.1
Jira ServerApplication
Affected:>= 8.6.0, < 8.13.5>= 8.14.0, < 8.15.1

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed Jira version
    Navigate to Jira Administration > System > System Info or check the <install_dir>/atlassian-jira/WEB-INF/classes/application-info.xml file for the version number
    Affected if The installed version is before 8.5.13, between 8.6.0-8.13.4 inclusive, or between 8.14.0-8.15.0 inclusive
  2. Verify if anonymous access is enabled
    Check Jira Administration > Security > Global Permissions to see if 'Anonymous' is granted any access permissions
    Affected if Anonymous users have any access rights to Jira
  3. Identify publicly visible custom fields
    Navigate to Jira Administration > Issues > Custom Fields and review fields that are available to 'All Users' or 'Anonymous' in the 'Context' configuration
    Affected if Any custom field exists that is visible to unauthenticated users
  4. Check if attackers can be assigned to visible fields
    Review the 'Allow users to attach this field to issues' permission on publicly accessible custom fields in the custom field context settings
    Affected if Publicly visible custom fields can be assigned to issues by anonymous or untrusted users
  5. Test membersOf JQL function accessibility
    As an anonymous or low-privilege user, construct a JQL query using 'membersOf("groupname")' to see if group enumeration is possible
    Affected if The JQL query returns results without proper authorization errors, indicating group membership can be enumerated

You are affected if your Jira version falls within the vulnerable ranges AND anonymous access is enabled AND there exists a publicly visible issue field that attackers can manipulate to exploit the membersOf JQL function.

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.5.13 / 8.13.5 / 8.15.1 or later
Fixed in 8.5.138.13.58.15.1
Interim mitigation

Upgrade Jira Server/Data Center to version 8.5.13, 8.13.5, 8.15.1 or later. As a temporary measure, restrict public access to issue fields and disable anonymous access if possible.

Fix this in Data Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,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 $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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