Description
The Customer Context Filter in Atlassian Jira Service Desk Server and Jira Service Desk Data Center before 3.9.17, from 3.10.0 before 3.16.10, from 4.0.0 before 4.2.6, from 4.3.0 before 4.3.5, from 4.4.0 before 4.4.3, and from 4.5.0 before 4.5.1 allows remote attackers with portal access to view arbitrary issues in Jira Service Desk projects via authorization bypass. Note that when the 'Anyone can email the service desk or raise a request in the portal' setting is enabled, an attacker can grant themselves portal access, allowing them to exploit the vulnerability.
Affected products
- Atlassian / Jira Service Desk Data Centerunspecified – 4.5.1
- Atlassian / Jira Service Desk Data Centerunspecified – 3.9.17
- Atlassian / Jira Service Desk Data Center3.10.0 – unspecified
- Atlassian / Jira Service Desk Data Centerunspecified – 3.16.10
- Atlassian / Jira Service Desk Data Center4.0.0 – unspecified
- Atlassian / Jira Service Desk Data Centerunspecified – 4.2.6
- Atlassian / Jira Service Desk Data Center4.3.0 – unspecified
- Atlassian / Jira Service Desk Data Centerunspecified – 4.3.5
- Atlassian / Jira Service Desk Data Center4.4.0 – unspecified
- Atlassian / Jira Service Desk Data Centerunspecified – 4.4.3
- Atlassian / Jira Service Desk Data Center4.5.0 – unspecified
- Atlassian / Jira Service Desk Serverunspecified – 3.9.17
- Atlassian / Jira Service Desk Server3.10.0 – unspecified
- Atlassian / Jira Service Desk Serverunspecified – 3.16.10
- Atlassian / Jira Service Desk Server4.0.0 – unspecified
- Atlassian / Jira Service Desk Serverunspecified – 4.2.6
- Atlassian / Jira Service Desk Server4.3.0 – unspecified
- Atlassian / Jira Service Desk Serverunspecified – 4.3.5
- Atlassian / Jira Service Desk Server4.4.0 – unspecified
- Atlassian / Jira Service Desk Serverunspecified – 4.4.3
- Atlassian / Jira Service Desk Server4.5.0 – unspecified
- Atlassian / Jira Service Desk Serverunspecified – 4.5.1