Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update MASWE-0002.md #3050

Merged
merged 1 commit into from
Nov 7, 2024
Merged

Update MASWE-0002.md #3050

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions weaknesses/MASVS-STORAGE/MASWE-0002.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,15 @@ mappings:

refs:
- https://developer.android.com/about/versions/nougat/android-7.0-changes#permfilesys
- https://developer.android.com/privacy-and-security/security-tips#internal-storage
draft:
description: Sensitive data may be stored in internal locations without ensuring
exclusive app access (e.g. by using the wrong file permissions) and may be accessible
to other apps.
topics:
- File permissions (Android)
- improperly configured FileProvider (Android)
- [Avoid the deprecated MODE_WORLD_WRITEABLE and MODE_WORLD_READABLE modes for IPC files](https://developer.android.com/privacy-and-security/security-tips#internal-storage). They don't provide the ability to limit data access to particular applications, and they don't provide any control of data format. If you want to share your data with other app processes, consider using a content provider instead, which offers read and write permissions to other apps and can make dynamic permission grants on a case-by-case basis.
status: draft

---
Expand Down
Loading