# CVE-2022-0540: Auth bypass in Jira Core Server

> Remote unauthenticated attackers can bypass authentication in Jira Server and Data Center via crafted HTTP requests, requiring immediate upgrades.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2022
- **Updated:** 24 Oct 2024
- **Also known as:** GHSA-h5cm-vc68-69h9

## What is CVE-2022-0540?

CVE-2022-0540 is a critical authentication bypass vulnerability in Atlassian Jira Data Center, published on 20 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP request. This affects Atlassian Jira Server and Data Center versions before 8.13.18, versions 8.14.0 and later before 8.20.6, and versions 8.21.0 and later before 8.22.0. This also affects Atlassian Jira Service Management Server and Data Center versions before 4.13.18, versions 4.14.0 and later before 4.20.6, and versions 4.21.0 and later before 4.22.0.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-0540?

It affects 3 products.


Products: Atlassian Jira Data Center, Atlassian Jira Server, Atlassian Jira Service Management.

## How do I fix CVE-2022-0540?

No fix has been published for CVE-2022-0540 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-0540 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0540 exists.

Public exploit code:

- Atlassian Jira Seraph Authentication Bypass RCE（CVE-2022-0540） (github_poc): https://github.com/Pear1y/CVE-2022-0540-RCE
- Atlassian Jira Seraph - Authentication Bypass (nuclei): http/cves/2022/CVE-2022-0540.yaml

## Other vulnerabilities in Atlassian Jira Data Center

- [CVE-2021-26086](https://insights.sbomify.com/CVE-2021-26086/): Atlassian Jira Server and Data Center Path Traversal (medium 5.3, exploited in the wild)
- [CVE-2020-36239](https://insights.sbomify.com/CVE-2020-36239/): Deserialization in Jira Core Data Center (critical 9.8)
- [CVE-2025-22167](https://insights.sbomify.com/CVE-2025-22167/): Path traversal in Jira Software Data Center (high 8.7)
- [CVE-2019-20419](https://insights.sbomify.com/CVE-2019-20419/): Other in Jira Server (high 7.8)
- [CVE-2024-21685](https://insights.sbomify.com/CVE-2024-21685/): Information disclosure in Jira Core Data Center (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0540 and fix it if it is affected.

What it is: CVE-2022-0540 is a critical authentication bypass vulnerability in Atlassian Jira Data Center, published on 20 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0540 exists.

Affected product: Atlassian Jira Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0540/ (Markdown: https://insights.sbomify.com/CVE-2022-0540/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0540
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0540
- OSV: https://osv.dev/vulnerability/CVE-2022-0540

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0540/
Summaries are generated and may contain mistakes; the official description above is the record.