LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14994: 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 version 3.9.16, from version 3.10.0 before version 3.16.8, from version 4.0.0 before version 4.1.3, from version 4.2.0 before version 4.2.5, from version 4.3.0 before version 4.3.4, and version 4.4.0 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 Takehigh

Analyst readout for executives and security teams

Plain-English summary

This flaw could let someone with Jira Service Desk portal access see issues they should not see. In open portals where anyone can email or raise a request, the source says an attacker may be able to give themselves portal access first.

Executive priority

Prioritize remediation for externally reachable service desks because the impact is unauthorized issue disclosure, potentially exposing customer data, internal operations, or security-sensitive tickets. Treat as high urgency where open portal registration is enabled.

Technical view

CVE-2019-14994 is a path traversal issue in the Customer Context Filter of Atlassian Jira Service Desk Server and Data Center. A remote attacker with portal access can view arbitrary issues in Jira Service Desk projects. The bundle names affected pre-fix 3.9.x, 3.10.x, 4.0.x, 4.2.x, 4.3.x, and 4.4.0 versions.

Likely exposure

Exposure is most likely in self-managed Jira Service Desk Server or Data Center deployments running affected versions, especially internet-facing customer portals or portals allowing anyone to email or raise requests.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. Public references include advisory and vulnerability write-ups, so defenders should assume technical details are publicly known while avoiding unsupported claims of live attacks.

Researcher notes

The key precondition is portal access, but the public portal setting can weaken that barrier. The bundle provides affected version ranges and fixed versions for several branches, but does not provide CVSS, CWE, KEV status, or a named 4.4.x fixed version.

Mitigation direction

  • Upgrade affected 3.9.x deployments to 3.9.16 or later vendor-supported guidance.
  • Upgrade affected 3.10.x deployments to 3.16.8 or later vendor-supported guidance.
  • Upgrade affected 4.0.x, 4.2.x, and 4.3.x to the listed fixed branch releases.
  • For 4.4.0, check Atlassian JSDSERVER-6517 for the correct fixed upgrade target.
  • Restrict portal access and disable public request creation where business requirements allow.
  • Review Service Desk issue permissions for overly broad customer visibility.

Validation and detection

  • Inventory Jira Service Desk Server and Data Center versions across all environments.
  • Check whether customer portals are internet-facing or allow anyone to raise requests.
  • Confirm each affected branch is upgraded beyond the fixed versions named in the advisory.
  • Review access logs for unusual portal activity around Service Desk issue views.
  • Validate customers cannot view issues outside their intended projects or requests.
Prepared
Confidence
high
Sources
6

Public sources used

Based on public source material and reviewed before publication.

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-14994 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
5Source 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.2.0, unspecified, 4.3.0, unspecified, 4.4.0Listed
AtlassianJira Service Desk Data Centerunspecified, 3.10.0, unspecified, 4.0.0, unspecified, 4.2.0, unspecified, 4.3.0, unspecified, 4.4.0Listed
Weakness

CWE details

No CWE listed

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