dbcve.org
JiraApplication · Atlassian

CVE-2017-18098

MEDIUM · 6.1 CVSS v3.0 Published 2018-04-06
Fix available
A fix is available. Upgrade to 7.6.1 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 searchrequest-xml resource in Atlassian Jira before version 7.6.1 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability through various fields.

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's searchrequest-xml resource. Remote attackers can inject arbitrary HTML or JavaScript through various search fields that are rendered without proper sanitization when the XML output is displayed, affecting versions prior to 7.6.1.

MitigationUpgrade Jira to version 7.6.1 or later to receive the vendor patch, or apply the specific security patch provided by Atlassian.

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.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. Identify Jira installation version
    Access the Jira about page (typically at /secure/About.jspa or /about.jsp) or navigate to Administration > System > System Info to view the installed version number
    Affected if The displayed version is any version prior to 7.6.1 (e.g., 7.6.0, 7.5.x, 7.4.x, etc.)
  2. Confirm the searchrequest-xml module exists
    Verify that the searchrequest-xml plugin/module is loaded by accessing a search results page and attempting to append '-xml' to the view (such as /sr/jira.issueviews:searchrequest-xml/)
    Affected if The XML view of search results is accessible and returns XML output without errors
  3. Test XML output rendering
    Perform a search in Jira and switch to XML view (or construct a searchrequest-xml URL manually), then inspect whether the returned XML contains unsanitized user input from search fields
    Affected if The XML output displays search field values (e.g., issue titles, descriptions, custom fields) without proper XML encoding/sanitization

You are affected if your Jira version is below 7.6.1 AND the searchrequest-xml feature is accessible and returns unescaped content in its XML output.

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.1 or later
Fixed in 7.6.1
Interim mitigation

Upgrade Jira to version 7.6.1 or later to receive the vendor patch, or apply the specific security patch provided by Atlassian.

Fix this in Jira Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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