Codex/issue 2386 glob security - #2442
Closed
SarthakDudhe wants to merge 2 commits into
Closed
Conversation
|
Any news on this? We tracked down a vulnerability potential in Glob@10.5.0 coming from js-beautify. #2427 is a PR that updates to a fully non-vulnerable version* |
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.
Updated the project’s glob dependency from ^10.5.0 to ^11.1.0 to address the reported security vulnerability. Regenerated package-lock.json so the lockfile now resolves to glob@11.1.0 with its updated transitive dependencies. This is a dependency-only fix, so no application code changes were needed.