Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2019-15003

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.

Security Impact Summary

This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.3, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts limited data confidentiality, for affected systems. Impacting 1 product from atlassian organizations running these solutions should prioritize assessment and patching.

Historical Context

First disclosed in 2019, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.

Published

2019-11-07T04:15:10.550

Last Modified

2024-11-21T04:27:51.237

Status

Modified

Source

[email protected]

Severity

CVSSv3.1: 5.3 (MEDIUM)

CVSSv2 Vector

AV:N/AC:M/Au:N/C:P/I:N/A:N

Access Vector: NETWORK
Access Complexity: MEDIUM
Authentication: NONE
Confidentiality Impact: PARTIAL
Integrity Impact: NONE
Availability Impact: NONE

Exploitability Score

8.6

Impact Score

2.9

Weaknesses

Type: Primary
CWE-22

Affected Vendors & Products

Type	Vendor	Product	Version/Range	Vulnerable?
Application	atlassian	jira_service_desk	< 3.9.17	Yes
Application	atlassian	jira_service_desk	< 3.9.17	Yes
Application	atlassian	jira_service_desk	< 3.16.10	Yes
Application	atlassian	jira_service_desk	< 3.16.10	Yes
Application	atlassian	jira_service_desk	< 4.2.6	Yes
Application	atlassian	jira_service_desk	< 4.2.6	Yes
Application	atlassian	jira_service_desk	< 4.3.5	Yes
Application	atlassian	jira_service_desk	< 4.3.5	Yes
Application	atlassian	jira_service_desk	< 4.4.3	Yes
Application	atlassian	jira_service_desk	< 4.4.3	Yes
Application	atlassian	jira_service_desk	< 4.5.1	Yes
Application	atlassian	jira_service_desk	< 4.5.1	Yes

References

http://packetstormsecurity.com/files/155214/Jira-Service-Desk-Server-Data-Center-Path-Traversal.html Third Party Advisory ([email protected])
https://jira.atlassian.com/browse/JSDSERVER-6590 Issue Tracking, Vendor Advisory ([email protected])
https://seclists.org/bugtraq/2019/Nov/9 Third Party Advisory ([email protected])
http://packetstormsecurity.com/files/155214/Jira-Service-Desk-Server-Data-Center-Path-Traversal.html Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)
https://jira.atlassian.com/browse/JSDSERVER-6590 Issue Tracking, Vendor Advisory (af854a3a-2127-422b-91ae-364da2661108)
https://seclists.org/bugtraq/2019/Nov/9 Third Party Advisory (af854a3a-2127-422b-91ae-364da2661108)

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For atlassian's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.