dbcve.org
JiraApplication · Atlassian

CVE-2017-18101

MEDIUM · 6.5 CVSS v3.1 Published 2018-04-10
Fix available
A fix is available. Upgrade to 7.6.5 / 7.7.3 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 administrative external system import resources in Atlassian JIRA Server (including JIRA Core) before version 7.6.5, from version 7.7.0 before version 7.7.3, from version 7.8.0 before version 7.8.3 and before version 7.9.0 allow remote attackers to run import operations and to determine if an internal service exists through missing permission checks.

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 missing authorization vulnerability in Atlassian JIRA Server's external system import functionality. Multiple import resources lack proper permission checks, allowing remote attackers to trigger import operations and probe for internal services without authentication or proper authorization.

MitigationUpgrade JIRA Server to version 7.6.5, 7.7.3, 7.8.3, 7.9.0 or later. Until patched, restrict network access to JIRA administrative interfaces to mitigate unauthorized import execution and service enumeration.

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.5
Jira ServerApplication
Affected:>= 7.7.0, < 7.7.3>= 7.8.0, < 7.8.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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Verify JIRA version
    Access JIRA Administration > System > System Info or check the installed version file in the JIRA home directory. The version is typically displayed in the system information page or in a version.properties file.
    Affected if The installed version falls into any of these ranges: version < 7.6.5, OR version >= 7.7.0 and < 7.7.3, OR version >= 7.8.0 and < 7.8.3
  2. Confirm external import functionality is accessible
    Attempt to access JIRA REST import endpoints without authentication. Common endpoints include /rest/api/2/import/ and similar paths under /rest/ that handle external system imports. Use a tool like curl to send unauthenticated requests to these endpoints.
    Affected if The import endpoints return successful responses or prompts for import configuration without requiring valid credentials or session authentication
  3. Review JIRA access logs for import activity
    Examine JIRA access logs (typically found in the logs directory) for requests to import-related endpoints. Look for POST or GET requests to import paths originating from unauthenticated or unexpected IP addresses.
    Affected if Logs show import operations or import-related requests executed without corresponding authentication records or from unauthorized sources
  4. Check network exposure of JIRA administrative interfaces
    Verify that JIRA server is directly accessible from the internet or untrusted networks. Test whether the JIRA base URL and its REST API endpoints are reachable without VPN or firewall restrictions.
    Affected if JIRA is exposed to untrusted networks without proper access controls, allowing external attackers to reach the vulnerable import functionality

A JIRA instance is affected if it runs any version before 7.6.5, between 7.7.0-7.7.2, or between 7.8.0-7.8.2 AND the external import endpoints are accessible without authentication or proper authorization checks.

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.5 / 7.7.3 / 7.8.3 or later
Fixed in 7.6.57.7.37.8.3
Interim mitigation

Upgrade JIRA Server to version 7.6.5, 7.7.3, 7.8.3, 7.9.0 or later. Until patched, restrict network access to JIRA administrative interfaces to mitigate unauthorized import execution and service enumeration.

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-2017-18101 — 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-18101 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