dbcve.org
Jira Data CenterApplication · Atlassian

CVE-2022-36799

HIGH · 7.2 CVSS v3.1 Published 2022-08-01
Fix available
A fix is available. Upgrade to 8.13.19 / 8.20.7 or later.
See remediation →
78/100
Remediation priority · High
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
This issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented. Affected versions of Atlassian Jira Server and Data Center allowed remote attackers with system administrator permissions to execute arbitrary code via Template Injection leading to Remote Code Execution (RCE) in the Email Templates feature. In this case the security improvement was to protect against using the XStream library to be able to execute arbitrary code in velocity templates. The affected versions are before version 8.13.19, from version 8.14.0 before 8.20.7, and from version 8.21.0 before 8.22.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 · high confidence

Template injection vulnerability in Jira Server and Data Center's Email Templates feature allowed remote attackers with system administrator permissions to execute arbitrary code via XStream library exploitation in velocity templates, leading to Remote Code Execution (RCE).

MitigationUpgrade Jira to version 8.13.19, 8.20.7, 8.22.1 or later to patch the template injection vulnerability in the Email Templates feature.

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.19>= 8.14.0, < 8.20.7>= 8.21.0, < 8.22.1
Jira ServerApplication
Affected:< 8.13.19>= 8.14.0, < 8.20.7>= 8.21.0, < 8.22.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Check Jira installation version
    Navigate to Jira Administration > System > System Info or run the command: /rest/api/2/healthcheck or check the atlassian-jira/WEB-INF/atlassian-bundled-plugins.properties or the jira-application.properties file for the version number
    Affected if The installed version falls within any of these ranges: < 8.13.19, >= 8.14.0 and < 8.20.7, or >= 8.21.0 and < 8.22.1
  2. Verify Email Templates feature accessibility
    Log in as a system administrator and navigate to Jira Administration > System > Email > Email Templates. Confirm the Email Templates configuration page loads successfully.
    Affected if The Email Templates feature is present and accessible to system administrators in the affected version range
  3. Confirm XStream library is in use
    Inspect the Jira installation directory for the XStream JAR file in the lib or WEB-INF/lib folder, or check the classpath for XStream deserialization handlers.
    Affected if XStream library is present in the Jira installation and the version is vulnerable to the deserialization gadget chain used in this template injection
  4. Check for system administrator accounts
    Review Jira user directory for accounts with Jira System Administrator global permission. This permission grants access to the Email Templates feature.
    Affected if Any user account possesses system administrator permissions, enabling access to the vulnerable Email Templates configuration area
  5. Inspect velocity template processing
    Review Jira logs for any custom velocity template modifications in the email-templates directory or look for recent changes to template files under the Jira home directory.
    Affected if Custom velocity templates are in use or have been modified, which could indicate attempted exploitation of the template injection vector

A user is affected if their Jira Server or Data Center version is below 8.13.19, between 8.14.0-8.20.6, or between 8.21.0-8.22.0 AND the Email Templates feature is accessible to system administrators with XStream library present.

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.19 / 8.20.7 / 8.22.1 or later
Fixed in 8.13.198.20.78.22.1
Interim mitigation

Upgrade Jira to version 8.13.19, 8.20.7, 8.22.1 or later to patch the template injection vulnerability in the Email Templates feature.

Recommended fix High confidence

Upgrade to Jira 8.13.19 (if on <8.14.0), 8.20.7 (if on 8.14.0-8.20.x), or 8.22.1 (if on 8.21.0-8.22.0)

  1. 1. Identify current Jira version by navigating to Jira Administration > System > System Info
  2. 2. Based on current version, determine upgrade target: if < 8.13.19 upgrade to 8.13.19; if >= 8.14.0 and < 8.20.7 upgrade to 8.20.7; if >= 8.21.0 and < 8.22.1 upgrade to 8.22.1
  3. 3. Review Atlassian upgrade documentation and release notes for the target version
  4. 4. Perform a full backup of Jira database and home directory before upgrading
  5. 5. Download the target version from Atlassian official downloads page
  6. 6. Stop Jira application services
  7. 7. Run the installer or deploy the new version following standard Jira upgrade procedures
  8. 8. Start Jira and verify the upgrade completed successfully
Caveat Standard Jira minor version upgrade risks apply - review release notes for behavioral changes, ensure app/compatibility, test in staging first

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

Fix this in Jira Data Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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