LiveActive security incident?Get immediate response
CVE Record

CVE-2019-15004: The Customer Context Filter in Atlassian Jira Service Desk Server and Jira Service Desk Data Center before...

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 a path traversal vulnerability. 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2019-15004 lets someone with Jira Service Desk portal access view issues they should not be able to see. If open request creation is enabled, an outside attacker may be able to gain portal access themselves, increasing business risk where service desk issues contain customer, employee, or incident data. Exposure is most likely on affected Jira Service Desk Server or Data Center deployments, especially internet-facing service desks and portals allowing anyone to email the desk or raise portal requests. Prioritize remediation for internet-facing or open-registration service desks because the issue can expose arbitrary service desk issues, potentially including sensitive customer, employee, or incident information. Mitigation focus: Upgrade to Atlassian fixed versions or later for the affected release train.; Review Atlassian advisory JSDSERVER-6589 for vendor-specific upgrade guidance.; Disable or restrict open portal request creation where business needs allow..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-15004 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianJira Service Desk Serverunspecified, 3.10.0, unspecified, 4.0.0, unspecified, 4.3.0, unspecified, 4.4.0, unspecified, 4.5.0, unspecifiedListed
AtlassianJira Service Desk Data Centerunspecified, 3.10.0, unspecified, 4.0.0, unspecified, 4.3.0, unspecified, 4.4.0, unspecified, 4.5.0, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.