-
-
Notifications
You must be signed in to change notification settings - Fork 6
New weaknesses regarding 3rd party libs #11
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.
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
base: main
Are you sure you want to change the base?
Changes from 5 commits
5fb602f
047f464
c5616dd
c697cd1
61b19af
3d936bf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| title: Sensitive Data Leaked via Embedded Libraries | ||
| id: MASWE-xxxA | ||
| alias: data-leak-libraries | ||
| platform: [android, ios] | ||
| profiles: [P] | ||
| mappings: | ||
| masvs-v2: [MASVS-PLATFORM-3, MASVS-STORAGE-2] | ||
| cwe: [200, 359] | ||
| draft: | ||
| description: Embedded third-party libraries (e.g. analytics, advertising, or crash reporting) can leak sensitive data to external services. Review the usage of embedded libraries to ensure they do not leak sensitive data outside of the expected SLA. This targets user Privacy. MASWE-0076 tests security. | ||
| status: placeholder | ||
|
|
||
| --- |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| title: Dependencies Know to be Malicious | ||
Diolor marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| id: MASWE-xxxB | ||
| alias: data-leak-malicious-libraries | ||
| platform: [android, ios] | ||
| profiles: [L1,L2] | ||
| mappings: | ||
| masvs-v2: [MASVS-PLATFORM-3, MASVS-STORAGE-2] | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. CODE? |
||
| cwe: [200, 359] | ||
| draft: | ||
| description: Embedded third-party libraries known to be malicious can leak sensitive data to external services. These libraries have access to e.g. ApplicationContext on Android or the full app memory on iOS. This gives them access to read data stored on the disk or in memory and thus could act as an insider threat within the app's process and boundaries. Apply supply chain security best practices to ensure the integrity of embedded libraries such as SBOM checks. | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The fact that the library/SDK is malicious should be irrelevant as weaknesses are generic. The focus here should be put on the fact that the app includes libraries/SDKs already known to be malicious. Regardless of what exactly they do. Those "bad" things they do should be all covered by other weaknesses. |
||
| status: placeholder | ||
|
|
||
| --- | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed in our previous call, this can be removed. The fact that the responsible component is an SDK vs the main app binary is typically not relevant at the MASWE level. This is very intentional, otherwise we'd have to duplicate most of the weaknesses.
This weakness should be covering for this topic:
https://mas.owasp.org/MASWE/MASVS-PRIVACY/MASWE-0112/
Title and content may be updated (on a separate PR) to reflect both collection and sharing.