JiraApplication · Atlassian
CVE-2019-11585
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 startup.jsp resource in Jira before version 7.13.6, from version 8.0.0 before version 8.2.3, and from version 8.3.0 before version 8.3.2 allows remote attackers to redirect users to a different website which they may use as part of performing a phishing attack via an open redirect.
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 confidenceThis is an open redirect vulnerability in Atlassian Jira's startup.jsp resource. Attackers can craft malicious URLs containing the vulnerable endpoint that redirect users to arbitrary external websites, enabling phishing attacks. The vulnerability affects multiple Jira versions: before 7.13.6, 8.0.0-8.2.2, and 8.3.0-8.3.1.
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.13.6
Jira ServerApplication
>= 8.0.0, < 8.2.3>= 8.3.0, < 8.3.2CVSS 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 installation and versionAccess the Jira administration console or check /rest/api/2/serverInfo endpoint. The version is also displayed in the footer of Jira pages or in the About dialog (gear icon > Applications > About).Affected if The installed Jira version is < 7.13.6, OR between 8.0.0-8.2.2 inclusive, OR between 8.3.0-8.3.1 inclusive
-
Confirm Jira Server product typeVerify the installed product is Jira Server (not Jira Cloud) by checking the About page or the serverinfo API response for the 'deploymentType' field.Affected if The product is Jira Server or Jira Core Server with a version in the affected ranges from step 1
-
Test startup.jsp endpoint accessibilitySend an HTTP request to your Jira base URL with /startup.jsp?redirect=http://example.com appended. Check if the response includes a 302 redirect to an external domain.Affected if The server responds with a Location header pointing to an external domain (not your Jira base URL), confirming the open redirect is present and exploitable
-
Check if startup.jsp existsAttempt to access /startup.jsp directly via browser or curl. A 200 response indicates the file exists and may be reachable without authentication.Affected if The endpoint responds with 200 OK and is accessible without authentication
You are affected if Jira Server is running a version less than 7.13.6, or between 8.0.0-8.2.2, or between 8.3.0-8.3.1, AND the /startup.jsp endpoint is accessible and can be induced to redirect to arbitrary external URLs.
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.13.68.2.38.3.2
Upgrade Jira to version 7.13.6, 8.2.3, 8.3.2, or later to patch the vulnerable startup.jsp resource. Until patching is possible, consider blocking or restricting access to the startup.jsp endpoint at the web application firewall or reverse proxy level.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11585 — 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-2019-11585 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