First published: Wed Feb 01 2023(Updated: )
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.
Credit: security@atlassian.com security@atlassian.com
Affected Software | Affected Version | How to fix |
---|---|---|
Atlassian Jira Service Management | >=5.3.0<5.3.3 | |
Atlassian Jira Service Management | >=5.3.0<5.3.3 | |
Atlassian Jira Service Management | >=5.4.0<5.4.2 | |
Atlassian Jira Service Management | >=5.4.0<5.4.2 | |
Atlassian Jira Service Management | =5.5.0 | |
Atlassian Jira Service Management | =5.5.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2023-22501.
The severity of CVE-2023-22501 is critical with a CVSS score of 9.1.
The affected software is Atlassian Jira Service Management Server and Data Center versions 5.3.0 to 5.3.3, and versions 5.4.0 to 5.4.2, and version 5.5.0.
An attacker can exploit CVE-2023-22501 by impersonating another user and gaining unauthorized access to a Jira Service Management instance.
Yes, Atlassian has released a security patch to fix CVE-2023-22501. It is recommended to update to the latest version of Jira Service Management.