dbcve.org
JiraApplication · Atlassian

CVE-2021-41308

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-26
Fix available
A fix is available. Upgrade to 8.6.0 / 8.13.12 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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 authenticated yet non-administrator remote attackers to edit the File Replication settings via a Broken Access Control vulnerability in the `ReplicationSettings!default.jspa` endpoint. The affected versions are before version 8.6.0, from version 8.7.0 before 8.13.12, and from version 8.14.0 before 8.20.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
How this class of weakness works · CWE-285

The application confirms who you are but does not properly check whether you are permitted to perform a given action, so authenticated users reach functions or data meant for others. Attackers test roles and object references to find the gap. Remediation is an authorization check on every request, evaluated against the acting user's actual permissions.

General guidance for the improper authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.6.0
Jira Data CenterApplication
Affected:>= 8.7.0, < 8.13.12
Jira ServerApplication
Affected:>= 8.7.0, < 8.13.12>= 8.14.0, < 8.20.1
Jira Software Data CenterApplication
Affected:< 8.6.0>= 8.14.0, < 8.20.1

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
High
Availability
None

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

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.

dbcve · scoped
Upgrade available Upgrade to 8.6.0 / 8.13.12 / 8.20.1 or later
Fixed in 8.6.08.13.128.20.1
Vendor patch jira.atlassian.com →
Recommended fix High confidence

8.20.1 (or latest 8.x LTS/8.20.x release for maximum stability)

  1. 1. Identify the currently installed Jira version by navigating to Jira Administration > System > System Info
  2. 2. Determine the appropriate target version based on current version: if < 8.6.0, upgrade to 8.6.0 or later; if >= 8.7.0 and < 8.13.12, upgrade to 8.13.12 or later; if >= 8.14.0 and < 8.20.1, upgrade to 8.20.1 or later
  3. 3. Review Atlassian upgrade documentation and release notes for the target version
  4. 4. Perform a full backup of the Jira database and home directory before upgrading
  5. 5. Download the target Jira version from Atlassian's official download center
  6. 6. Stop the Jira application service
  7. 7. Run the installer or deploy the new WAR files according to Atlassian's upgrade instructions
  8. 8. Start the Jira application and verify the upgrade was successful
Caveat Review Atlassian upgrade notes for potential compatibility changes between your current version and target version; ensure third-party apps/plugins are compatible

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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