Vulnerability - Upgrade bl to v2.2.1#1432
Open
sergiopereirain wants to merge 1 commit intoSOHU-Co:masterfrom
Open
Vulnerability - Upgrade bl to v2.2.1#1432sergiopereirain wants to merge 1 commit intoSOHU-Co:masterfrom
sergiopereirain wants to merge 1 commit intoSOHU-Co:masterfrom
Conversation
There was a vulnerability fixed in `bl@2.2.1`. It was also fixed in `3.0.1` and `4.0.3` but just bumping from `2.2.0` to `2.2.1` seems less risky here. > Affected versions of this package are vulnerable to Remote Memory Exposure. If user input ends up in consume() argument and can become negative, BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.
sergiopereirain
changed the title
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.
There was a vulnerability fixed in
bl@2.2.1. It was also fixed in3.0.1and4.0.3but just bumping from2.2.0to2.2.1seems less risky here.