Data CenterApplication · Atlassian

CVE-2021-39123

HIGH · 7.5 CVSS v3.1 Published 2021-09-14

Fix available

A fix is available. Upgrade to 8.16.0 or later.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Affected versions of Atlassian Jira Server and Data Center allow unauthenticated remote attackers to impact the application's availability via a Denial of Service (DoS) vulnerability in the /rest/gadget/1.0/createdVsResolved/generate endpoint. The affected versions are before version 8.16.0.

Technical summary

dbcve analysis · high confidence

Unauthenticated remote attackers can exploit a DoS vulnerability in Jira's /rest/gadget/1.0/createdVsResolved/generate endpoint to impact application availability. The vulnerability affects all Jira Server and Data Center versions prior to 8.16.0.

MitigationUpgrade Jira Server or Data Center to version 8.16.0 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Data CenterApplication

Affected:< 8.16.0

JiraApplication

Affected:< 8.16.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected?

dbcve checks

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

Check Jira version

Navigate to Jira Administration > System > Troubleshooting and support tools, or check the footer of any Jira page for the version number

Affected if Version is listed as lower than 8.16.0 (e.g., 8.13.x, 8.14.x, 8.15.x)
Verify the /rest/gadget/1.0/createdVsResolved endpoint exists

Send an HTTP GET request to https://YOUR-JIRA-HOST/rest/gadget/1.0/createdVsResolved/generate (no authentication required)

Affected if The endpoint responds with HTTP 200 or any JSON response rather than 404 or 403 (indicating the gadget API is accessible)
Confirm Jira Server or Data Center deployment

Check the Jira administration console or installation artifacts to confirm whether the deployment is Jira Server or Data Center

Affected if The deployment is Atlassian Jira Server or Data Center and the version is below 8.16.0

Your Jira instance is affected if it is a Server or Data Center deployment running any version lower than 8.16.0 and the /rest/gadget/1.0/createdVsResolved/generate endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 8.16.0 or later

Fixed in 8.16.0

Interim mitigation

Upgrade Jira Server or Data Center to version 8.16.0 or later to remediate this vulnerability.

Recommended fix High confidence

8.16.0 or later

Back up your Jira database and home directory before proceeding with any upgrade
Review Atlassian's official upgrade documentation for Jira Server/Data Center at https://confluence.atlassian.com/jira/
Download Jira Server or Data Center version 8.16.0 or later from https://www.atlassian.com/software/jira/download
Stop the Jira application server
Follow Atlassian's standard upgrade procedure: run the installer or extract the new version, then start Jira
Verify the upgrade was successful by checking the Jira version in About Jira > Troubleshooting and support
Confirm the /rest/gadget/1.0/createdVsResolved/generate endpoint is now patched

Caveat Review Atlassian's upgrade notes for any breaking changes between your current version and 8.16.0; major version jumps may have configuration or compatibility considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Center 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-2021-39123 — 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

Primary sources

jira.atlassian.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-39123 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2021-39123?

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.

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

At a glance

A fix existsUpgrade to 8.16.0 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 1.6%

Affects: Data Center

Remediation

A high-priority fix

Fix this in Data Center 12 hrs · Moderate

Typical engagement from $2,130

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2021-39123 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References