Jira ServerApplication · Atlassian
CVE-2020-14177
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 · uneditedAffected versions of Atlassian Jira Server and Data Center allow remote attackers to impact the application's availability via a Regex-based Denial of Service (DoS) vulnerability in JQL version searching. The affected versions are before version 7.13.16; from version 7.14.0 before 8.5.7; from version 8.6.0 before 8.10.2; and from version 8.11.0 before 8.11.1.
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 confidenceAffected versions of Atlassian Jira Server and Data Center contain a Regex-based Denial of Service (ReDoS) vulnerability in JQL version searching. Remote attackers can craft malicious JQL queries that trigger excessive regex processing, causing the application to become unresponsive or unavailable.
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.13.16>= 7.14.0, < 8.5.7>= 8.6.0, < 8.10.2>= 8.11.0, < 8.11.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
-
Determine installed Jira versionLog in as an administrator and navigate to the About page (typically at /secure/About.jspa) or check the version in the installation directory's atlassian-jira/WEB-INF/built.jar or version.properties fileAffected if The version falls within any of these ranges: < 7.13.16, >= 7.14.0 and < 8.5.7, >= 8.6.0 and < 8.10.2, >= 8.11.0 and < 8.11.1
-
Verify JQL search accessibilityCheck whether untrusted or unauthenticated users have access to the search functionality. Navigate to Administration > System > Global Permissions and review which groups have the 'Browse Projects' or 'Create Issues' permissions that enable JQL searchingAffected if Untrusted users, including anonymous users if enabled, can execute JQL searches
-
Confirm external JQL query exposureTest whether JQL search endpoints are reachable without authentication by attempting a search request to the REST API (e.g., /rest/api/2/search?jql=) from an unauthenticated session or untrusted accountAffected if JQL queries can be submitted by unauthenticated or untrusted users over the network
Your environment is affected if the installed Jira version is vulnerable AND untrusted or anonymous users can submit JQL queries to the system.
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.168.5.78.10.2
Upgrade Jira to version 7.13.16, 8.5.7, 8.10.2, 8.11.1 or later. Alternatively, restrict JQL search permissions to trusted users until patching can be completed.
Fix this in Jira Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14177 — 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-2020-14177 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