Attack Chain

1. An attacker crafts a malicious HTTP request targeting a pygeoapi instance configured with a STAC collection resource.
2. The crafted request includes a URL containing path traversal sequences (e.g., ../) to navigate the file system.
3. pygeoapi’s STAC FileSystemProvider plugin receives the request and attempts to resolve the file path.
4. Due to the raw string path concatenation vulnerability, the path traversal sequences are not properly sanitized.
5. The application constructs an incorrect file path, allowing access to files and directories outside of the intended STAC collection directory.
6. The attacker retrieves sensitive information or configuration files located in the exposed directories.
7. The attacker could potentially use the exposed information to further compromise the system.
8. The final objective is unauthorized access to sensitive data and potentially system compromise.

Impact

The path traversal vulnerability in pygeoapi allows unauthorized access to directories and files, potentially exposing sensitive data, configuration files, or even source code. The impact depends on the data stored in the exposed directories. Successful exploitation can lead to information disclosure, privilege escalation, and further system compromise. Organizations using vulnerable pygeoapi versions are at risk until they upgrade to version 0.23.3 or implement the recommended workaround.

Recommendation

• Upgrade to pygeoapi version 0.23.3 to patch the vulnerability as detailed in the advisory (https://github.com/advisories/GHSA-f6pr-83pg-ghh6).
• As an immediate mitigation, disable STAC collection-based resources in the pygeoapi configuration as described in the advisory (https://github.com/advisories/GHSA-f6pr-83pg-ghh6).
• Deploy the Sigma rule “pygeoapi Path Traversal Attempt” to detect exploitation attempts in web server logs.