Repository navigation
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
4 of 11 tasks
This file contains hidden or 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.
📖 Description
Standardizes and broadens the blocks in place to prevent elevated processes from acting on data writable at a lower integrity level. The goal of this change is to prevent the potential for EoP attacks via system artifacts for packages.
I am hoping to follow it up reasonably soon with another change to allow these scenarios to function once again, but safely by running the intended action at a lower integrity level.
🔍 Validation
Tests are added, but mostly to ensure the security aspects. This will certainly cause failures in some scenarios that previously worked, but that is unavoidable without the much more complex change mentioned earlier.
Microsoft Reviewers: Open in CodeFlow