# CVE-2023-22501: Auth bypass in Jira Service Management Data Center

> Attackers can impersonate users and gain access to Jira Service Management instances by exploiting signup tokens under specific configuration conditions.

- **Severity:** Critical 9.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-jm25-87xp-4h76

## What is CVE-2023-22501?

CVE-2023-22501 is a critical authentication bypass vulnerability in Atlassian Jira Service Management Data Center, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication vulnerability was discovered in Jira Service Management Server and Data Center which allows an attacker to impersonate another user and gain access to a Jira Service Management instance under certain circumstances_._ With write access to a User Directory and outgoing email enabled on a Jira Service Management instance, an attacker could gain access to signup tokens sent to users with accounts that have never been logged into. Access to these tokens can be obtained in two cases:

* If the attacker is included on Jira issues or requests with these users, or
* If the attacker is forwarded or otherwise gains access to emails containing a “View Request” link from these users.

Bot accounts are particularly susceptible to this scenario. On instances with single sign-on, external customer accounts can be affected in projects where anyone can create their own account.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-22501?

It affects 1 product.


Products: Atlassian Jira Service Management.

## How do I fix CVE-2023-22501?

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

## Is CVE-2023-22501 being exploited?

There is no known exploitation of CVE-2023-22501 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Jira Service Management Data Center

- [CVE-2021-43943](https://insights.sbomify.com/CVE-2021-43943/): Cross-site scripting in Jira Service Management Data Center (medium 4.8)
- [CVE-2022-36800](https://insights.sbomify.com/CVE-2022-36800/): Information disclosure in Jira Service Management Data Center (medium 4.3)
- [CVE-2021-43948](https://insights.sbomify.com/CVE-2021-43948/): Missing authorization in Jira Service Management Data Center (medium 4.3)
- [CVE-2021-43950](https://insights.sbomify.com/CVE-2021-43950/): Missing authorization in Jira Service Management Data Center (medium 4.3)
- [CVE-2021-43949](https://insights.sbomify.com/CVE-2021-43949/): Missing authorization in Jira Service Management Data Center (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22501 and fix it if it is affected.

What it is: CVE-2023-22501 is a critical authentication bypass vulnerability in Atlassian Jira Service Management Data Center, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22501 in the wild and no public exploit code.

Affected product: Atlassian Jira Service Management 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-2023-22501/ (Markdown: https://insights.sbomify.com/CVE-2023-22501/index.md)
```

## Sources

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

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