dbcve.org
Jira Data CenterApplication · Atlassian

CVE-2021-43941

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-15
Fix available
A fix is available. Upgrade to 8.13.5 / 8.20.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 modify several resources (including CsvFieldMappingsPage.jspa and ImporterValueMappingsPage.jspa) via a Cross-Site Request Forgery (CSRF) vulnerability in the jira-importers-plugin. The affected versions are before version 8.13.15, and from version 8.14.0 before 8.20.3.

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

This is a Cross-Site Request Forgery (CSRF) vulnerability in the jira-importers-plugin of Atlassian Jira Server and Data Center. Remote attackers can exploit this to modify specific resources (CsvFieldMappingsPage.jspa and ImporterValueMappingsPage.jspa) by tricking authenticated users into submitting malicious requests.

MitigationUpgrade Jira Server and Data Center to version 8.13.15 or 8.20.3 or later to obtain the patched version of the jira-importers-plugin that includes CSRF protection tokens.

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 Data CenterApplication
Affected:< 8.13.5>= 8.14.0, < 8.20.3
Jira ServerApplication
Affected:< 8.13.5>= 8.14.0, < 8.20.3

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

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

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. Identify Jira product and version
    Access Jira administration or check the /rest/api/2/serverInfo endpoint to retrieve the installed Jira version and determine if it is Server or Data Center edition
    Affected if The installed version falls within < 8.13.5 OR >= 8.14.0 and < 8.20.3
  2. Confirm jira-importers-plugin is present
    Navigate to Jira administration > Manage apps or check the /rest/plugins/1.0/ endpoint to verify the jira-importers-plugin is installed and enabled
    Affected if The jira-importers-plugin is installed and active
  3. Check for CSRF protection on vulnerable endpoints
    Inspect the HTTP responses and form submissions for CsvFieldMappingsPage.jspa and ImporterValueMappingsPage.jspa pages to verify if CSRF tokens are included in the requests
    Affected if The pages do not require CSRF tokens for state-changing operations
  4. Verify user session context
    Confirm that Jira users are authenticated and have access to the importers plugin functionality, as the CSRF attack requires an authenticated user session
    Affected if Users with importer permissions are logged in and can access the vulnerable pages

A Jira Server or Data Center instance is affected if the installed version is 8.13.x below 8.13.5, or 8.14.0 through 8.20.3, and the jira-importers-plugin is enabled with the CsvFieldMappingsPage.jspa or ImporterValueMappingsPage.jspa endpoints lacking CSRF token validation.

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.

dbcve · scoped
Upgrade available Upgrade to 8.13.5 / 8.20.3 or later
Fixed in 8.13.58.20.3
Interim mitigation

Upgrade Jira Server and Data Center to version 8.13.15 or 8.20.3 or later to obtain the patched version of the jira-importers-plugin that includes CSRF protection tokens.

Recommended fix High confidence

8.13.15 or 8.20.3 (or later respective releases)

  1. Identify the current Jira version by navigating to Jira Administration > System > System Info
  2. Determine which upgrade path is appropriate: either upgrade to 8.13.15 or later in the 8.13.x line, or upgrade to 8.20.3 or later in the 8.20.x line
  3. Review Jira release notes and upgrade guide for the target version
  4. Create a complete backup of the Jira database and home directory
  5. Test the upgrade in a non-production environment first
  6. Apply the upgrade following Atlassian's standard upgrade documentation
  7. Verify the upgrade was successful and the CSRF vulnerability is resolved
Caveat Review Atlassian release notes for the target version for any breaking changes or required configuration updates

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

Fix this in Jira Data Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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