SPFx solutions as a spyware #1893
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Category
Contents of the Pull Request
SharePoint solutions may read all user's SharePoint data and user's auth token (2 lines of code for this one) and send it to external APIs without administrator's or user's consent.
It's impossible to disable it or control it in any way.
We are typically focusing on Microsoft Graph, but I feel like nobody realizes (or talks about) the risks associated with these solutions being practically full trust code. And as much as I love the PnP Samples, I would like more users, administrators, governance teams implement more robust security audits.
It's time we talk about it openly =)