dbcve.org
JiraApplication · Atlassian

CVE-2019-20418

MEDIUM · 6.5 CVSS v3.1 Published 2020-07-03
Fix available
A fix is available. Upgrade to 8.8.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
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to prevent users from accessing the instance via an Application Denial of Service vulnerability in the /rendering/wiki endpoint. The affected versions are before version 8.8.0.

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

Affected versions of Atlassian Jira Server and Data Center contain a denial of service vulnerability in the /rendering/wiki endpoint that allows remote attackers to crash or make the instance unavailable to legitimate users. This is an application-layer DoS that exploits the wiki rendering functionality.

MitigationUpgrade Jira Server or Data Center to version 8.8.0 or later to resolve this vulnerability.

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.8.0
Jira Software Data CenterApplication
Affected:< 8.8.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.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 checks

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

  1. Determine installed Jira version
    Access Jira Administration > Troubleshooting and support tools > System Info, or query the /rest/api/2/serverInfo endpoint, or check the <jira-install>/atlassian-jira/WEB-INF/classes/jira-config.properties file
    Affected if The reported version is less than 8.8.0
  2. Confirm the /rendering/wiki endpoint is accessible
    Send an HTTP GET request to <jira-base-url>/rest/rendering/wiki - no authentication may be required for this endpoint
    Affected if The endpoint responds (returns 200 or any HTTP status) indicating it is reachable
  3. Verify wiki rendering feature is enabled
    Check Jira Administration > General Configuration > Advanced Settings for 'wiki.render.editors.enabled' or examine the <jira-install>/atlassian-jira/WEB-INF/classes/jira-config.properties file for wiki rendering configuration
    Affected if Wiki rendering is enabled (value set to 'true' or property exists)

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.8.0 or later
Fixed in 8.8.0
Interim mitigation

Upgrade Jira Server or Data Center to version 8.8.0 or later to resolve this vulnerability.

Fix this in Jira Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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