dbcve.org
JiraApplication · Atlassian

CVE-2018-13402

MEDIUM · 6.1 CVSS v3.0 Published 2018-10-23
Fix available
A fix is available. Upgrade to 7.6.9 / 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
Many resources in Atlassian Jira before version 7.6.9, 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, from version 7.11.0 before version 7.11.3, from version 7.12.0 before version 7.12.3, and before version 7.13.1 allow remote attackers to attack users, in some cases be able to obtain a user's Cross-site request forgery (CSRF) token, via a open redirect vulnerability.

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 an open redirect vulnerability in Atlassian Jira that allows remote unauthenticated attackers to redirect users to malicious URLs. The open redirect can be leveraged to obtain a user's CSRF token, enabling subsequent CSRF attacks against that user. The attacker tricks a user into visiting a crafted URL that passes through Jira's redirect mechanism.

MitigationUpgrade Jira to version 7.6.9, 7.7.5, 7.8.5, 7.9.3, 7.10.3, 7.11.3, 7.12.3, or 7.13.1 or later. Alternatively, implement URL validation to reject external redirect destinations and ensure users are warned before following outgoing links.

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.9
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.3>= 7.12.0, < 7.12.3>= 7.13.0, < 7.13.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 version from administration interface
    Log in as an administrator and navigate to Jira Administration > System > System Information, or look for the version in the footer of the Jira UI. The version is typically displayed as something like '7.x.x'
    Affected if The displayed version is lower than 7.6.9, or falls within 7.7.0-7.7.4, 7.8.0-7.8.4, 7.9.0-7.9.2, 7.10.0-7.10.2, 7.11.0-7.11.2, 7.12.0-7.12.2, or 7.13.0-7.13.0
  2. Identify Jira version via REST API
    Make a GET request to the /rest/api/2/serverInfo endpoint, for example: curl https://your-jira-host/rest/api/2/serverInfo. The response contains a 'version' field.
    Affected if The version field in the JSON response matches any of the affected version ranges listed above
  3. Confirm web accessibility of Jira
    Verify that the Jira web interface is accessible over HTTP/HTTPS from the network where potential attackers would originate. Check if Jira is exposed to the internet or internal networks.
    Affected if Jira is accessible via web and the version falls within affected ranges - the open redirect can be exploited remotely without authentication

If your Jira installation is web-accessible and its version matches any of the affected ranges (below 7.6.9, or within 7.7.0-7.7.4, 7.8.0-7.8.4, 7.9.0-7.9.2, 7.10.0-7.10.2, 7.11.0-7.11.2, 7.12.0-7.12.2, or 7.13.0), then you are affected by this open redirect vulnerability.

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

Upgrade Jira to version 7.6.9, 7.7.5, 7.8.5, 7.9.3, 7.10.3, 7.11.3, 7.12.3, or 7.13.1 or later. Alternatively, implement URL validation to reject external redirect destinations and ensure users are warned before following outgoing links.

Fix this in Jira Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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