dbcve.org
JiraApplication · Atlassian

CVE-2017-16863

MEDIUM · 6.1 CVSS v3.0 Published 2018-01-18
Fix available
A fix is available. Upgrade to 7.5.3 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 PieChart gadget in Atlassian Jira before version 7.5.3 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability through the name of a project or filter.

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 a stored (persistent) cross-site scripting (XSS) vulnerability in the PieChart gadget of Atlassian Jira. Attackers can inject malicious HTML or JavaScript through project or filter names, which then execute when other users view the PieChart visualization.

MitigationUpgrade Jira to version 7.5.3 or later to patch the XSS vulnerability in the PieChart gadget.

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.5.3

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.0/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 installation and version
    Check the Jira installation directory for the version file, or access the Jira administration 'About' page (Jira Administration > System > Troubleshooting and support > View product information). Alternatively, check the response header 'X-Jira-Build-Number' or the '/rest/api/2/serverInfo' API endpoint.
    Affected if The installed Jira version is 7.5.2 or earlier (any version below 7.5.3).
  2. Confirm PieChart gadget is accessible
    Navigate to Jira Dashboards and verify if the PieChart gadget is available in the gadget directory or currently added to any dashboard. Check the gadget registry at /rest/gadget/1.0/available or examine dashboard XML configurations.
    Affected if The PieChart gadget exists and can be added to dashboards in the Jira instance.
  3. Check for user-created projects or filters with script content
    Review project names in Administration > Projects > View all projects, and filter names in Issues > Manage Filters. Look for any project or filter names containing HTML tags (<script>, <img onerror=>, javascript:, etc.) or unusual encoded characters.
    Affected if Any project or filter name contains executable JavaScript or HTML that could trigger XSS when rendered in the PieChart gadget.

You are affected if your Jira version is below 7.5.3 AND the PieChart gadget is accessible to users who could inject malicious project or filter names.

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.5.3 or later
Fixed in 7.5.3
Interim mitigation

Upgrade Jira to version 7.5.3 or later to patch the XSS vulnerability in the PieChart gadget.

Fix this in Jira Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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