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.

According to its self-reported version number, the Atlassian Jira Service Management application running on the remote host is version 5.3.0 prior to version 5.3.3, 5.4.0 prior to 5.4.2 or 5.5.0 prior to 5.3.3. It is, therefore, affected by a critical authentication vulnerability which allows a attacker to impersonate another user and gain access 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 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.

Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

The instance of  Atlassian Service Desk hosted on the remote web server is 5.3 prior to 5.3.3, 5.4 prior to 5.4.2 or 5.5 prior to 5.5.1. Is is, therefore, affected by an authentication vulnerability. A remote attacker included on Jira issues or requests with other users can impersonate those users if they are forwarded or otherwise gain access to emails containing a 'View Request' link from one of those users.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number

ID	Name	Product	Family	Severity
113891	Atlassian Jira Service Management 5.5.0 < 5.3.3 Critical Authentication Vulnerability	Web App Scanning	Component Vulnerability	critical
113890	Atlassian Jira Service Management 5.4.0 < 5.4.2 Critical Authentication Vulnerability	Web App Scanning	Component Vulnerability	critical
113889	Atlassian Jira Service Management 5.3.0 < 5.3.3 Critical Authentication Vulnerability	Web App Scanning	Component Vulnerability	critical
170980	Atlassian JIRA Service Desk 5.3.x < 5.3.3 / 5.4.x < 5.4.2 / 5.5.x < 5.5.1 Impersonation (JSDSERVER-12312)	Nessus	Misc.	critical

Detections

Analytics

CVE-2023-22501

critical

Tenable Plugins

critical

critical

critical

critical