CyberRota Analysis
AI-GeneratedThe Pathling Server prior to version 2.0.0 is vulnerable due to improper handling of the `/$result` endpoint, allowing attackers to exploit path traversal sequences in the `file` parameter to access unauthorized files within the warehouse database. This vulnerability could lead to unauthorized data exposure, impacting the confidentiality of sensitive health data. Organizations using Pathling for health data analytics should prioritize this issue and upgrade to version 2.0.0 or implement the recommended mitigations to secure their systems.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Pathling is a set of tools that make it easier to use FHIR and clinical terminology within health data analytics. Prior to version 2.0.0 of Pathling Server, Pathling's `/$result` endpoint allows a caller who can obtain any valid async export job ID to supply `file` parameter values containing path traversal sequences. The handler verifies only the supplied `job` and never normalises or confines the requested `file` path to that job's `jobs/<jobId>` directory before opening it as a filesystem resource. Because async export scratch space lives under the same warehouse database root as persisted resource tables, an attacker can use their own export job to read other files from the warehouse. This is fixed in Pathling Server 2.0.0. As an interim mitigation, disable the async export operations (`pathling.operations.exportEnabled`, `patientExportEnabled`, `groupExportEnabled`, `bulkSubmitEnabled`) or enable authentication and restrict export capability to trusted callers.