dbcve.org
Data CenterApplication · Atlassian

CVE-2020-36288

MEDIUM · 6.1 CVSS v3.1 Published 2021-04-15
Fix available
A fix is available. Upgrade to 8.5.12 / 8.13.4 or later.
See remediation →
68/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
The issue navigation and search view in Jira Server and Data Center before version 8.5.12, from version 8.6.0 before version 8.13.4, and from version 8.14.0 before version 8.15.1 allows remote attackers to inject arbitrary HTML or JavaScript via a DOM Cross-Site Scripting (XSS) vulnerability caused by parameter pollution.

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

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in Jira Server and Data Center's issue navigation and search view. The vulnerability is caused by parameter pollution, allowing remote attackers to inject arbitrary HTML or JavaScript via specially crafted URL parameters that are not properly sanitized before being rendered in the page DOM.

MitigationUpgrade Jira Server/Data Center to version 8.5.12, 8.13.4, 8.15.1 or later to patch this vulnerability. As a temporary measure, users should avoid clicking untrusted links to Jira instances.

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.12
JiraApplication
Affected:< 8.5.12
Jira Data CenterApplication
Affected:>= 8.6.0, < 8.13.4>= 8.14.0, < 8.15.1
Jira ServerApplication
Affected:>= 8.6.0, < 8.13.4>= 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 version
    Navigate to Jira Administration > System > Troubleshooting and support tools > System Info, or access /secure/AboutJira.jspa to view the installed version number
    Affected if The displayed version falls within any of these ranges: < 8.5.12, OR >= 8.6.0 and < 8.13.4, OR >= 8.14.0 and < 8.15.1
  2. Confirm issue navigation or search feature is in use
    Access the issue search/navigation view (typically at /issues/ or /secure/IssueNavigator.jspa) to confirm this component is active in the environment
    Affected if The issue navigation or search view is accessible and used in the deployment
  3. Review URL handling for parameter pollution
    Examine how URL parameters are processed in the search/navigation URLs. Check if custom or untrusted parameters can be injected into URLs like /issues/?<parameter>=value without sanitization
    Affected if URL parameters in the issue navigation/search are not validated or sanitized before DOM rendering
  4. Check for recent XSS indicators
    Review server logs and browser developer console reports for any unexpected script execution, console errors related to DOM manipulation, or suspicious parameter patterns in access logs targeting issue URLs
    Affected if There are logged indicators of script injection attempts or unexpected DOM modifications in the issue search context

The environment is affected if Jira Server or Data Center version is less than 8.5.12, or falls between 8.6.0-8.13.4, or falls between 8.14.0-8.15.1, and the issue navigation/search feature is accessible to users who could click specially crafted URLs.

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.12 / 8.13.4 / 8.15.1 or later
Fixed in 8.5.128.13.48.15.1
Interim mitigation

Upgrade Jira Server/Data Center to version 8.5.12, 8.13.4, 8.15.1 or later to patch this vulnerability. As a temporary measure, users should avoid clicking untrusted links to Jira instances.

Fix this in Data Center Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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