CVE-2019-15003
Last modified
CVE-2019-15003 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. 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.. EPSS estimates a 1.73% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Atlassian | Jira Service Desk | < 3.9.17 |
| Atlassian | Jira Service Desk | >= 3.10.0, < 3.16.10 |
| Atlassian | Jira Service Desk | >= 4.0.0, < 4.2.6 |
| Atlassian | Jira Service Desk | >= 4.3.0, < 4.3.5 |
| Atlassian | Jira Service Desk | >= 4.4.0, < 4.4.3 |
| Atlassian | Jira Service Desk | >= 4.5.0, < 4.5.1 |
References
- https://jira.atlassian.com/browse/JSDSERVER-6590Issue Tracking, Vendor Advisory
- https://seclists.org/bugtraq/2019/Nov/9Third Party Advisory
- https://jira.atlassian.com/browse/JSDSERVER-6590Issue Tracking, Vendor Advisory
- https://seclists.org/bugtraq/2019/Nov/9Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-15003?
How severe is CVE-2019-15003?
How do I fix CVE-2019-15003?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2019
- CVE-2019-14998The Webwork action Cross-Site Request Forgery (CSRF) protect…6.5
- CVE-2019-14999The Uninstall REST endpoint in Atlassian Universal Plugin Ma…
- CVE-2019-1500Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2019-15000The commit diff rest endpoint in Bitbucket Server and Data C…9.8
- CVE-2019-15001The Jira Importers Plugin in Atlassian Jira Server and Data …7.2
- CVE-2019-15002An exploitable CSRF vulnerability exists in Atlassian Jira, …4.3
- CVE-2019-15004The Customer Context Filter in Atlassian Jira Service Desk S…7.5
- CVE-2019-15005The Atlassian Troubleshooting and Support Tools plugin prior…4.3
- CVE-2019-15006There was a man-in-the-middle (MITM) vulnerability present i…6.5
- CVE-2019-15007The review resource in Atlassian Fisheye and Crucible before…4.8
- CVE-2019-15008The /plugins/servlet/branchreview resource in Atlassian Fish…6.1
- CVE-2019-15009The /json/profile/removeStarAjax.do resource in Atlassian Fi…4.3
Are you affected by CVE-2019-15003?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST