JiraApplication · Atlassian
CVE-2018-13401
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 · uneditedThe XsrfErrorAction resource 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 allows remote attackers to obtain a user's Cross-site request forgery (CSRF) token through an 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 confidenceThe XsrfErrorAction resource in Atlassian Jira contains an open redirect vulnerability that allows remote attackers to obtain a user's CSRF token. By tricking users into visiting a crafted URL, attackers can harvest CSRF tokens through the redirect mechanism, potentially enabling subsequent CSRF attacks against the user.
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
< 7.6.9
Jira ServerApplication
>= 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.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Jira versionLocate the version number in the application footer or access /rest/api/2/serverInfo to retrieve the version detailsAffected if The installed version falls within any of these ranges: < 7.6.9, >= 7.7.0 and < 7.7.5, >= 7.8.0 and < 7.8.5, >= 7.9.0 and < 7.9.3, >= 7.10.0 and < 7.10.3, >= 7.11.0 and < 7.11.3, >= 7.12.0 and < 7.12.3, >= 7.13.0 and < 7.13.1
-
Verify XsrfErrorAction endpoint existsAccess the URL path /plugins/servlet/XsrfErrorAction in a browser or via curl and observe the responseAffected if The endpoint returns a valid HTTP response (200 or 302) rather than a 404 error, indicating the vulnerable component is present
-
Test for open redirect behaviorVisit a crafted URL such as /plugins/servlet/XsrfErrorAction?os_destination=https://example.com and observe whether the application redirects to the supplied external domainAffected if The application redirects to the attacker-controlled destination instead of validating or rejecting the parameter
You are affected if your Jira version is within any of the affected ranges listed above AND the XsrfErrorAction endpoint is accessible and permits arbitrary redirects.
Generated from the published advisory. Verify against your own configuration.
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 data7.6.97.7.57.8.5
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, 7.13.1 or later. Alternatively, apply the appropriate security patch for the installed major version.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-13401 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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