Jira ServerApplication · Atlassian
CVE-2019-20401
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 · uneditedVarious installation setup resources in Jira before version 8.5.2 allow remote attackers to configure a Jira instance, which has not yet finished being installed, via Cross-site request forgery (CSRF) vulnerabilities.
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 confidenceCSRF vulnerability in Jira's installation setup resources allows remote attackers to trigger configuration actions on a Jira instance that has not yet completed installation. An attacker could potentially inject malicious configuration during the setup phase by tricking an administrator who is in the process of installing Jira into visiting a crafted page.
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
Jira ServerApplication
>= 7.6.15, < 8.5.2>= 8.5.3, < 8.6.0CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Server versionAccess Jira Administration > System > Troubleshooting and support tools > View product information, or check the <install_dir>/atlassian-jira/WEB-INF/classes/jira-app.properties file for the 'jira.version' propertyAffected if The installed version falls within 7.6.15 to 8.5.1, or 8.5.3 to 8.5.x versions below 8.6.0
-
Determine if initial setup has been completedAttempt to access the Jira setup wizard at /secure/SetupWizard.jspa or check if the <jira-home>/dbconfig.xml file exists and contains a configured datasourceAffected if The instance shows the setup wizard or has not yet created a database configuration file indicating initial setup is incomplete or was never run
-
Check for lingering setup mode indicatorsReview the <jira-home>/directory for presence of setup.lock file or inspect the Jira configuration to confirm the application is in a fully configured state rather than awaiting initial setupAffected if A setup.lock file exists in the Jira home directory suggesting the installation workflow may still be active or was interrupted
You are affected if your Jira Server version is 7.6.15 through 8.5.1 or 8.5.3 through 8.5.x and the instance has not completed its initial setup wizard or is in a state where setup could be re-triggered.
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 data8.5.28.6.0
Upgrade Jira to version 8.5.2 or later. During installation, ensure the setup process is conducted in an isolated environment and avoid browsing other sites until installation is complete.
Fix this in Jira Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20401 — 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-20401 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