CVE-2025-70084
Directory Traversal in OpenSatKit 2.2.1 Allows File Access
Publication date: 2026-02-11
Last updated on: 2026-02-17
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| opensatkit | opensatkit | 2.2.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2025-70084 is a directory traversal vulnerability in OpenSatKit version 2.2.1. It occurs because the FileUtil_GetFileInfo function performs limited validation on file paths supplied by users. Specifically, it does not properly sanitize or restrict path traversal sequences like "../", allowing attackers to specify crafted file paths that escape the intended directory boundaries.'}, {'type': 'paragraph', 'content': 'This flaw enables attackers to access sensitive information or delete arbitrary files outside the expected directories by supplying malicious file paths via telecommands.'}] [4]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to gain unauthorized access to sensitive files or delete arbitrary files on the system running OpenSatKit 2.2.1. By exploiting the directory traversal flaw, attackers can traverse outside the intended mission or application directories and potentially access critical system files or device files, especially on Linux or BSD-based deployments.
The impact includes exposure of confidential information, disruption of system operations through file deletion, and possible compromise of system integrity.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring for unusual or unauthorized file operations that involve directory traversal patterns, such as file paths containing "../" sequences that escape the intended directory boundaries.'}, {'type': 'paragraph', 'content': 'Since the vulnerability arises from crafted values passed to the FileUtil_GetFileInfo function and related file operations, detection can involve checking logs or telemetry for commands that attempt to access or delete files outside the expected directories.'}, {'type': 'paragraph', 'content': 'Specific commands to detect exploitation attempts are not provided in the available resources. However, general approaches include:'}, {'type': 'list_item', 'content': 'Reviewing application logs or telemetry for file operation commands containing suspicious path traversal sequences like "../".'}, {'type': 'list_item', 'content': 'Using file integrity monitoring tools to detect unexpected file deletions or modifications.'}, {'type': 'list_item', 'content': 'On the system level, commands like `grep` on logs for patterns such as "../" or unusual file paths may help identify attempts.'}, {'type': 'paragraph', 'content': 'No explicit detection commands or scripts are detailed in the provided resources.'}] [4, 3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include restricting or sanitizing input to file operation commands to prevent directory traversal sequences such as "../" from being processed.'}, {'type': 'paragraph', 'content': 'Since the vulnerability is due to insufficient validation in the FileUtil_GetFileInfo function and related file operations, applying patches or updates that fix this validation issue is recommended.'}, {'type': 'paragraph', 'content': 'If an updated version of OpenSatKit addressing this vulnerability is available, upgrading to that version is advised.'}, {'type': 'paragraph', 'content': 'In the absence of a patch, consider implementing input validation or filtering at the application or command interface level to block crafted file paths that attempt directory traversal.'}, {'type': 'paragraph', 'content': 'Additionally, limit the permissions of the OpenSatKit application to only the necessary directories and files to reduce the impact of potential exploitation.'}] [4]