Bump webpack-dev-server to fix CVE-2022-1650#12460
Open
knopp10000 wants to merge 1 commit into
Open
Conversation
Fix was made in webpack-dev-server with this push: webpack/webpack-dev-server@e765182
|
Any updates on this? |
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
3 participants
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.
Fix was made in webpack-dev-server with this push: webpack/webpack-dev-server@e765182
Problem description
Exposure of Sensitive Information in eventsource
When fetching an url with a link to an external site (Redirect), the users Cookies & Autorisation headers are leaked to the third party application. According to the same-origin-policy, the header should be "sanitized."
Severity Score
Critical 9.3 / 10 - according to dependabot
Background
That PR then updates webpack-dev-server's dependency on sockjs to v. 1.6.1 which includes this commit: sockjs/sockjs-client@1cf4a5a which updates eventsource to a version > 1.0.0.
This is the commit which fixes the security issue in Eventsource: EventSource/eventsource@f9f6416