Fix recommended deny rule for BGInfo#423
Open
h0pless wants to merge 4 commits intoMicrosoftDocs:mainfrom
Open
Conversation
Author
|
@microsoft-github-policy-service agree |
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.
The current recommended (template) rule for denying vulnerable versions of BGInfo.exe is incorrectly set to
MinimumFileVersion="4.21.0.0"even though all versions up to and including 4.21 are the vulnerable ones.This pull requests fixes these by replacing it with
MaximumFileVersion="4.21.0.0", therefore no longer blocking the fixed versions of BGInfo.Reference:
"1 A vulnerability in bginfo.exe was fixed in version 4.22. If you use BGInfo, for security, make sure to download and run the latest version of BGInfo. BGInfo versions earlier than 4.22 are still vulnerable and should be blocked."
https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/design/applications-that-can-bypass-appcontrol
Fixed in v4.22:
"This release of Bginfo honors Device Guard policy for VB scripts specified as the source of field data."
https://techcommunity.microsoft.com/blog/sysinternals-blog/sysinternals-update-procdump-v9-autoruns-v13-71-bginfo-v4-22-livekd-v5-62-proces/726072