dbcve.org
JiraApplication · Atlassian

CVE-2018-13387

MEDIUM · 6.1 CVSS v3.0 Published 2018-07-16
Fix available
A fix is available. Upgrade to 7.6.7 / 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
The IncomingMailServers resource in Atlassian JIRA Server before version 7.6.7, 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 and from version 7.10.0 before version 7.10.2 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the messagesThreshold parameter as the fix for CVE-2017-18039 was incomplete.

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 XSS vulnerability in Atlassian JIRA Server's IncomingMailServers resource. Attackers can inject malicious HTML or JavaScript via the messagesThreshold parameter, which was not properly sanitized even after the fix for CVE-2017-18039, allowing the previous mitigation to be bypassed.

MitigationUpgrade JIRA Server to version 7.6.7, 7.7.5, 7.8.5, 7.9.3, 7.10.2 or later. If immediate patching is not possible, consider restricting administrative access to the IncomingMailServers configuration area.

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

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 product type and version
    Navigate to Jira Administration > System > System Info or check the /secure/AdminHome.jspa page to confirm you are using JIRA Server (not Jira Cloud) and note the exact version number.
    Affected if The installed version is less than 7.6.7, OR between 7.7.0 and 7.7.5, OR between 7.8.0 and 7.8.5, OR between 7.9.0 and 7.9.3, OR between 7.10.0 and 7.10.2.
  2. Confirm Incoming Mail feature is accessible
    Navigate to Jira Administration > Mail > Incoming Mail. Verify the page loads and the configuration area for incoming mail servers is accessible.
    Affected if The user has administrative access to the IncomingMailServers configuration area.
  3. Locate messagesThreshold parameter
    In the Incoming Mail configuration, examine the mail server settings for any field that controls message threshold or limit settings. Inspect the HTML form elements for a parameter named 'messagesThreshold' or similar.
    Affected if A messagesThreshold parameter exists in the Incoming Mail server configuration form and accepts user-supplied input.
  4. Check for stored XSS indicators
    Use the browser developer tools or a proxy to inspect the HTTP requests when saving incoming mail server settings. Look for unsanitized input being stored and reflected in the response.
    Affected if The messagesThreshold value is stored and reflected in the UI without proper HTML encoding or sanitization.

You are affected if you run an affected JIRA Server version (as listed in step 1) AND have administrative access to the IncomingMailServers configuration where the messagesThreshold parameter can be manipulated with unsanitized input.

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

Upgrade JIRA Server to version 7.6.7, 7.7.5, 7.8.5, 7.9.3, 7.10.2 or later. If immediate patching is not possible, consider restricting administrative access to the IncomingMailServers configuration area.

Fix this in Jira Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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