dbcve.org
Jira Data CenterApplication · Atlassian

CVE-2022-36801

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to 8.20.8 or later.
See remediation →
68/100
Remediation priority · Elevated
High EPSS 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 anonymous remote attackers to inject arbitrary HTML or JavaScript via a Reflected Cross-Site Scripting (RXSS) vulnerability in the TeamManagement.jspa endpoint. The affected versions are before version 8.20.8.

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 reflected cross-site scripting (RXSS) vulnerability in Atlassian Jira Server and Data Center's TeamManagement.jspa endpoint. Anonymous remote attackers can inject arbitrary HTML or JavaScript through unsanitized user input that gets reflected back in the HTTP response, potentially allowing session hijacking or credential theft.

MitigationUpgrade Jira Server and Data Center to version 8.20.8 or later. If immediate patching is not possible, consider temporarily restricting access to the TeamManagement.jspa endpoint or implementing WAF rules to block XSS attack patterns.

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.20.8
Jira ServerApplication
Affected:< 8.20.8

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check Jira version
    Access the Jira administration about page (e.g., /secure/AdminSummary.jspa or /plugins/servlet/about) to view the installed version number
    Affected if The version displayed is lower than 8.20.8 (e.g., 8.20.7, 8.13.x, 8.5.x, 7.x)
  2. Verify TeamManagement.jspa endpoint exists
    Attempt to access /secure/TeamManagement.jspa on your Jira instance (e.g., https://your-jira-host/secure/TeamManagement.jspa)
    Affected if The endpoint returns a page rather than a 404 error, indicating the vulnerable component is present
  3. Confirm anonymous access is enabled
    Check Jira user management settings: go to Administration > User management > Default permissions or inspect if unauthenticated requests to /secure/TeamManagement.jspa return a valid page instead of redirecting to login
    Affected if The TeamManagement.jspa endpoint is accessible without authentication (anonymous users can reach it)
  4. Inspect HTTP response for unsanitized input reflection
    Send a crafted request to TeamManagement.jspa with a test payload in a parameter (e.g., ?name=<script>alert(1)</script>) and examine if the response contains the raw, unescaped payload
    Affected if The HTTP response reflects the injected script tags or HTML markup verbatim without encoding

You are affected if your Jira version is below 8.20.8 AND the TeamManagement.jspa endpoint is accessible (especially to anonymous users), allowing unsanitized user input to be reflected in the response.

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.20.8 or later
Fixed in 8.20.8
Interim mitigation

Upgrade Jira Server and Data Center to version 8.20.8 or later. If immediate patching is not possible, consider temporarily restricting access to the TeamManagement.jspa endpoint or implementing WAF rules to block XSS attack patterns.

Recommended fix High confidence

8.20.8

  1. Verify current Jira version by navigating to Administration > System > Troubleshooting and support > System info
  2. Review Jira 8.20.8 release notes at jira.atlassian.com for any migration or compatibility notes
  3. Perform a full backup of your Jira database and home directory
  4. Test the upgrade in a staging environment before production deployment
  5. Download Jira 8.20.8 from official Atlassian distribution
  6. Stop the Jira application service
  7. Run the installer or extract upgrade files to the Jira installation directory
  8. Start the Jira application service
Caveat Review 8.20.x release notes for any breaking changes or required migration steps before upgrading

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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