dbcve.org
Jira Service DeskApplication · Atlassian

CVE-2021-43959

MEDIUM · 5.7 CVSS v3.1 Published 2022-07-26
Fix available
A fix is available. Upgrade to 4.13.20 / 4.20.8 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 Service Management Server and Data Center allow authenticated remote attackers to access the content of internal network resources via a Server-Side Request Forgery (SSRF) vulnerability in the CSV importing feature of JSM Insight. When running in an environment like Amazon EC2, this flaw may be used to access to a metadata resource that provides access credentials and other potentially confidential information. The affected versions are before version 4.13.20, from version 4.14.0 before 4.20.8, and from version 4.21.0 before 4.22.2.

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

Atlassian Jira Service Management Server and Data Center contains an SSRF vulnerability in the CSV importing feature of JSM Insight. Authenticated remote attackers can trick the server into making requests to internal network resources, including cloud metadata services (e.g., AWS EC2 metadata) that may expose sensitive credentials.

MitigationUpgrade Jira Service Management to version 4.13.20, 4.20.8, 4.22.2 or later. Additionally, network segmentation and restricting metadata service access can limit exposure in cloud environments.

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 Service DeskApplication
Affected:< 4.13.20
Jira Service ManagementApplication
Affected:>= 4.14.0, < 4.20.8>= 4.21.0, < 4.22.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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. Verify JSM Insight app is installed
    Navigate to Jira Administration > Apps > Manage apps (or /plugins/servlet/upm/manage/com.atlassian.servicedesk.analytics-ui-plugin). Look for 'Insight - Asset Management' or 'JSM Insight' in the list of installed apps.
    Affected if The Insight app is not listed or is disabled, the vulnerability does not apply.
  2. Check Jira Service Management version
    Navigate to Jira Administration > System > System info (or /secure/admin/ViewSystemInfo.jspa). Locate the 'Version' field showing the installed JSM version.
    Affected if The version is < 4.13.20, OR >= 4.14.0 and < 4.20.8, OR >= 4.21.0 and < 4.22.2 - the environment falls within affected version ranges.
  3. Confirm CSV import feature exists
    Navigate to JSM Insight > Object schemas > any schema > Import (or /plugins/servlet/insight/import). Verify the CSV import option is present and accessible.
    Affected if The CSV import feature is visible and the Insight app is enabled on an affected version, the vulnerability is present.
  4. Verify user authentication settings
    Check Jira Administration > Security > Global permissions to confirm external users or non-admin users have access to Jira. The SSRF requires an authenticated attacker.
    Affected if Any authenticated user (including low-privilege users) can access the system, they could potentially trigger the CSV import feature for SSRF.

A user is affected if JSM Insight (Insight - Asset Management) is installed and enabled on an affected Jira Service Management version (less than 4.13.20, 4.14.0-4.20.7, or 4.21.0-4.22.1) and the CSV import feature is accessible to authenticated users.

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 4.13.20 / 4.20.8 / 4.22.2 or later
Fixed in 4.13.204.20.84.22.2
Interim mitigation

Upgrade Jira Service Management to version 4.13.20, 4.20.8, 4.22.2 or later. Additionally, network segmentation and restricting metadata service access can limit exposure in cloud environments.

Recommended fix High confidence

Upgrade to Jira Service Management 4.22.2 or later (or the earliest fixed version in your upgrade path: 4.13.20, 4.20.8, or 4.22.2 depending on current version)

  1. 1. Identify the current Jira Service Management version by navigating to Settings > Apps > Manage apps and checking the version number
  2. 2. Determine which vulnerable version range your installation falls into: < 4.13.20, >= 4.14.0 and < 4.20.8, or >= 4.21.0 and < 4.22.2
  3. 3. Review the Atlassian upgrade guide and release notes for the target version at jira.atlassian.com
  4. 4. Perform a complete backup of the Jira database and configuration files
  5. 5. Test the upgrade in a staging or development environment first
  6. 6. Schedule a maintenance window for the production upgrade
  7. 7. Apply the upgrade: download the appropriate fixed version from Atlassian's official download center and run the installation or upgrade
  8. 8. After upgrade, verify the Jira Service Management version shows the patched release
Caveat Standard Jira upgrade considerations apply - review deprecated features and test custom integrations in staging before production deployment

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

Fix this in Jira Service Desk 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-43959 — 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-43959 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