Atlassian Jira Service Management 5.5.0 Data Center Edition
Approved changes feed: RSS · Atom
cpe:2.3:a:atlassian:jira_service_management:5.5.0:*:*:*:data_center:*:*:*
part: a version: 5.5.0 update: *
| Vendor | Atlassian (8acde0d4-2b83-5bd8-8d3f-60d59e0b022e) |
|---|---|
| Product | Jira Service Management (ef0bce49-6288-522c-aa71-834eefcdd5a3) |
| Edition | * |
| Language | * |
| Software edition | data_center |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-22501 |
vulnerable | 2026-06-03 14:49:19.498984 |
Details available
CRITICAL (9.4)
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.
Published: 2023-02-01T18:00:36.982Z
Updated: 2024-10-01T15:10:37.485Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.