dbcve.org
JiraApplication · Atlassian

CVE-2019-11583

MEDIUM · 6.5 CVSS v3.0 Published 2019-06-26
Fix available
A fix is available. Upgrade to 8.1.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The issue searching component in Jira before version 8.1.0 allows remote attackers to deny access to Jira service via denial of service vulnerability in issue search when ordering by "Epic Name".

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

A denial of service vulnerability exists in Jira's issue search component before version 8.1.0. Remote attackers can cause service unavailability by crafting search queries that order results by 'Epic Name', potentially consuming excessive resources or causing the search to fail.

MitigationUpgrade Jira to version 8.1.0 or later to resolve this vulnerability. If immediate upgrading is not possible, consider restricting access to the search functionality or implementing rate limiting as a temporary mitigation.

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:< 8.1.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Jira version
    Access Jira administration or check the application footer/banner for the version number, or query the /rest/api/2/serverInfo endpoint
    Affected if Version is lower than 8.1.0 (e.g., 8.0.x, 7.x, etc.)
  2. Verify Jira search functionality is accessible
    Confirm that issue search features are available to users, typically at /secure/IssueNavigator.jspa or through the search API
    Affected if Search functionality is enabled and accessible to users or anonymous attackers
  3. Confirm Epic Link field is configured
    Check if the Epic Link custom field (customfield_10014 by default) exists in your Jira instance under Issues > Custom Fields
    Affected if Epic Link field is present, as this is required for 'Epic Name' ordering to be possible

Your Jira instance is affected if it runs version 8.1.0 or earlier AND the search feature with Epic Name ordering is accessible to the attackers who could exploit this DoS 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 8.1.0 or later
Fixed in 8.1.0
Interim mitigation

Upgrade Jira to version 8.1.0 or later to resolve this vulnerability. If immediate upgrading is not possible, consider restricting access to the search functionality or implementing rate limiting as a temporary mitigation.

Fix this in Jira Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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