Data CenterApplication · Atlassian
CVE-2020-36287
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 · uneditedThe dashboard gadgets preference resource of the Atlassian gadgets plugin used in Jira Server and Jira Data Center before version 8.13.5, and from version 8.14.0 before version 8.15.1 allows remote anonymous attackers to obtain gadget related settings via a missing permissions check.
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 confidenceThe dashboard gadgets preference resource in Atlassian Jira Server and Data Center has a missing permissions check vulnerability. This allows remote anonymous attackers to bypass authorization and access gadget-related settings through the gadgets plugin. The vulnerability is exploitable over the network without authentication.
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
< 8.13.5
JiraApplication
< 8.13.5
Jira Data CenterApplication
>= 8.14.0, < 8.15.1
Jira ServerApplication
>= 8.14.0, < 8.15.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Jira versionIn Jira, go to Jira Administration > System > Troubleshooting and support tools > System Info to view the version. Alternatively, check the 'atlassian-jira-software' WAR file name or the version file in the Jira installation directory.Affected if Version is lower than 8.13.5, or falls within the range 8.14.0 to 8.15.0 (inclusive)
-
Confirm Gadgets plugin is enabledIn Jira Administration, navigate to Manage apps > System plugins and locate the 'Gadgets Plugin' or 'gadgets-plugin' module in the list of installed plugins.Affected if The Gadgets plugin is present and active in the system
-
Test unauthenticated access to gadget preferences endpointSend a GET request to /rest/gadgets/1.0/preferences without providing any authentication credentials (no session, no cookies, no Authorization header). Capture the HTTP response code and body.Affected if The endpoint returns HTTP 200 with gadget preference data instead of redirecting to login or returning 401 Unauthorized/403 Forbidden
If your Jira version is vulnerable (below 8.13.5 or between 8.14.0-8.14.x) and the gadget preferences endpoint is accessible without authentication, you are affected by this authorization bypass.
Generated from the published advisory. Verify against your own configuration.
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 data8.13.58.15.1
Apply the vendor-supplied patches by upgrading to Jira version 8.13.5 or later, or 8.15.1 or later, depending on your current version branch. This is a straightforward patch update requiring no code changes.
Fix this in Data Center
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-36287 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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