feat(rules): New UAC bypass via elevated Internet Explorer add-on installer COM interface rule#622
Open
rabbitstack wants to merge 1 commit intomasterfrom
Conversation
…taller COM interface rule Identifies potential User Account Control (UAC) bypass activity involving the elevated Internet Explorer add-on installation mechanism exposed through a COM interface. Adversaries can take advantage of scenarios in which legacy Internet Explorer components are abused to execute code with high integrity outside of standard user consent flows.
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
1 participant
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.
What is the purpose of this PR / why it is needed?
Identifies potential User Account Control (UAC) bypass activity involving the elevated Internet Explorer add-on installation mechanism exposed through a COM interface. Adversaries can take advantage of scenarios in which legacy Internet Explorer components are abused to execute code with high integrity outside of standard user consent flows.
What type of change does this PR introduce?
/kind feature (non-breaking change which adds functionality)
Any specific area of the project related to this PR?
/area rules
Special notes for the reviewer
Does this PR introduce a user-facing change?