Fix unmanaged resource leak in NTLM RC4 key generation#1989
Closed
rustamque wants to merge 1 commit intojstedfast:masterfrom
Closed
Fix unmanaged resource leak in NTLM RC4 key generation#1989rustamque wants to merge 1 commit intojstedfast:masterfrom
rustamque wants to merge 1 commit intojstedfast:masterfrom
Conversation
Owner
|
Thanks |
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.
RandomNumberGenerator.Create()allocates unmanaged cryptographic resources (e.g., CSP handles on Windows) inRC4.GenerateKey(), butDispose()is not explicitly called.In high-throughput scenarios or cyclic calls, this can lead to resource exhaustion before the Garbage Collector has a chance to run the finalizers.
Wrapped the
RandomNumberGenerator.Create()instantiation in ausingblock to ensure deterministic disposal of the cryptographic resources.Found by Linux Verification Center (linuxtesting.org) with SVACE.