dbcve.org
JiraApplication · Atlassian

CVE-2018-13395

MEDIUM · 6.1 CVSS v3.0 Published 2018-08-28
Fix available
A fix is available. Upgrade to 7.6.8 / 7.7.5 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
Various resources in Atlassian Jira before version 7.6.8, from version 7.7.0 before version 7.7.5, from version 7.8.0 before version 7.8.5, from version 7.9.0 before version 7.9.3, from version 7.10.0 before version 7.10.3 and before version 7.11.1 allow remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the epic colour field of an issue while an issue is being moved.

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 cross-site scripting (XSS) vulnerability in Atlassian Jira where the epic colour field of an issue is not properly sanitized during the issue move operation. Remote attackers can inject arbitrary HTML or JavaScript that executes in the browsers of other users who view the affected issue.

MitigationUpgrade Jira to version 7.6.8, 7.7.5, 7.8.5, 7.9.3, 7.10.3, or 7.11.1 or later. Alternatively, implement input validation on the epic colour field or disable the issue move functionality until the upgrade can be performed.

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.6.8
Jira ServerApplication
Affected:>= 7.7.0, < 7.7.5>= 7.8.0, < 7.8.5>= 7.9.0, < 7.9.3>= 7.10.0, < 7.10.3>= 7.11.0, < 7.11.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.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. Check Jira version
    Access Jira administration or look at the footer of any Jira page to find the installed version number. Alternatively, query the /rest/api/2/serverInfo endpoint.
    Affected if The installed version is less than 7.6.8, or falls within any of these ranges: 7.7.0 to 7.7.4, 7.8.0 to 7.8.4, 7.9.0 to 7.9.2, 7.10.0 to 7.10.2, or 7.11.0 to 7.11.0.
  2. Verify Jira Software with epics is in use
    Check if the Jira instance has any Software projects configured with Scrum or Kanban boards that use epics. Inspect the project settings or board configuration.
    Affected if The instance hosts Software projects using epics, which is required for the vulnerable epic colour field to exist.
  3. Confirm issue move feature is accessible
    Try to move an issue between projects using the Move issue option in the issue actions menu, or check the permission scheme for the MOVE_ISSUE permission.
    Affected if The issue move operation is enabled and users have permissions to move issues between projects.
  4. Inspect epic colour field configuration
    Open any issue that is an epic, or view a board with epics, and examine the epic colour/colour field setting in the issue or board configuration.
    Affected if The epic colour field accepts custom colour values and is not being validated on input.

You are affected if your Jira version falls within the vulnerable ranges AND you have Jira Software projects using epics with the issue move functionality enabled.

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.6.8 / 7.7.5 / 7.8.5 or later
Fixed in 7.6.87.7.57.8.5
Interim mitigation

Upgrade Jira to version 7.6.8, 7.7.5, 7.8.5, 7.9.3, 7.10.3, or 7.11.1 or later. Alternatively, implement input validation on the epic colour field or disable the issue move functionality until the upgrade can be performed.

Fix this in Jira Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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