chore: upgrade glob from 10_2_7 to 10_5_0 - #19
Closed
alchemain-syedali[bot] wants to merge 1 commit into
Closed
Conversation
Open
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.
This pull request updates the
globdependency from version 10.2.7 to 10.5.0. The primary motivation is to address a security vulnerability identified as GHSA-5j98-mcp5-4vw2, which affects the glob CLI’s-c/--cmdflag. In vulnerable versions, when the--cmdoption is used, the matched file paths are passed to a shell command withshell: true, creating a command injection vector. An attacker who can control the file names (e.g., through a crafted repository or upload) could execute arbitrary shell commands.Upgrading to 10.5.0 resolves this by ensuring that matched paths are properly escaped or handled in a way that prevents injection. No code changes were required in our repository—the dependency version was updated in the package manifest, and the rest of our usage is compatible without modification.