dbcve.org
JiraApplication · Atlassian

CVE-2020-14173

MEDIUM · 5.4 CVSS v3.1 Published 2020-07-03
Fix available
A fix is available. Upgrade to 8.5.4 / 8.6.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 file upload feature in Atlassian Jira Server and Data Center in affected versions allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability. The affected versions are before version 8.5.4, from version 8.6.0 before 8.6.2, and from version 8.7.0 before 8.7.1.

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 stored Cross-Site Scripting (XSS) vulnerability in Jira Server and Data Center's file upload feature allows remote attackers to inject malicious HTML or JavaScript into uploaded files. When other users view or access these uploaded files, the injected script executes in their browsers, potentially enabling session hijacking, credential theft, or defacement.

MitigationUpgrade Jira to version 8.5.4, 8.6.2, or 8.7.1 or later to apply the security patch. As a temporary control, restrict file upload permissions to trusted users and consider implementing content-disposition headers for file uploads.

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.5.4
Jira Data CenterApplication
Affected:>= 8.6.0, < 8.6.2>= 8.7.0, < 8.7.1
Jira ServerApplication
Affected:>= 8.6.0, < 8.6.2>= 8.7.0, < 8.7.1
Jira Software Data CenterApplication
Affected:< 8.5.4

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Check Jira version
    Log in as an administrator, navigate to Jira Administration > System > System Info, or run the command: java -jar atlassian-jira-core-*.jar --version or check the <install-dir>/atlassian-jira/WEB-INF/classes/application-info.xml file
    Affected if The installed version is less than 8.5.4, or falls between 8.6.0 (inclusive) and 8.6.2 (exclusive), or between 8.7.0 (inclusive) and 8.7.1 (exclusive)
  2. Verify file upload functionality is enabled
    Navigate to Jira Administration > System > File Attachments settings, or check the <jira-home>/jira-config.properties file for the 'attachement.enabled' setting
    Affected if File attachments are enabled (attachment.enabled is set to true or not explicitly set to false)
  3. Identify which users can upload files
    Navigate to Jira Administration > Security > Default folder permissions or check project-level permission schemes for the 'Create Attachments' permission
    Affected if Users other than administrators or trusted users have the ability to upload files to issues
  4. Check if uploaded files are served with content-disposition headers
    Inspect HTTP response headers when downloading an attached file - look for 'Content-Disposition: attachment; filename=...' header
    Affected if Uploaded files are served with inline content-disposition or without security headers, allowing the browser to render the file content

You are affected if your Jira version falls within the vulnerable ranges (below 8.5.4, between 8.6.0-8.6.2, or between 8.7.0-8.7.1) AND the file upload feature is accessible to untrusted users.

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.4 / 8.6.2 / 8.7.1 or later
Fixed in 8.5.48.6.28.7.1
Interim mitigation

Upgrade Jira to version 8.5.4, 8.6.2, or 8.7.1 or later to apply the security patch. As a temporary control, restrict file upload permissions to trusted users and consider implementing content-disposition headers for file uploads.

Fix this in Jira Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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