MASWE-0082: Unsafe Handling of Data From Local Storage
Content in BETA
This content is in beta and still under active development, so it is subject to change any time (e.g. structure, IDs, content, URLs, etc.).
Placeholder Weakness
This weakness hasn't been created yet and it's a placeholder. But you can check its status or start working on it yourself. If the issue has not yet been assigned, you can request to be assigned to it and submit a PR with the new content for that weakness by following our guidelines.
Check our GitHub Issues for MASWE-0082
Initial Description or Hints¶
When data is read from local storage, it should be treated as untrusted.
Relevant Topics¶
- Internal Storage
- External Storage
- UIDocumentPickerViewController used by the receiver app
- The app does not validate or sanitize input from local storage, which may lead to injection vulnerabilities when the data is interpreted or used in sensitive operations (CWE-20).
- The app does not validate or sanitize file paths read from local storage, enabling potential path traversal attacks (CWE-22).
- Paths to local files are influenced by attacker-controlled input, and their content can be modified (common in external storage or document pickers), leading to unintended file access or tampering (CWE-73).
- The app processes data from local storage as if it were inherently trustworthy, without isolating or verifying it, allowing attackers to alter app state or behavior (CWE-349).
References¶
- https://developer.android.com/topic/security/risks/path-traversal
- https://developer.android.com/topic/security/risks/zip-path-traversal
MASTG v1 Coverage¶
No MASTG v1 tests are related to this weakness.