chore: upgrade glob from 10_2_7 to 10_5_0#33
Draft
alchemain-qa-bot[bot] wants to merge 2 commits into
Draft
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 upgrades the
globdependency from version 10.2.7 to 10.5.0.Why this upgrade is needed:
The primary driver for this change is to address a critical security vulnerability (GHSA-5j98-mcp5-4vw2) in the
globCLI. In versions prior to 10.5.0, the-c/--cmdoption executed matched file paths usingshell:true, which allowed command injection. An attacker could craft a malicious file name that, when matched by a glob pattern, would execute arbitrary shell commands.Code changes:
No code changes were required. The upgrade is a straightforward version bump in the dependency manifest, as the fix is entirely contained within the
globlibrary itself. The new version resolves the vulnerability without altering any of our application's existing usage patterns or APIs.