build(deps): bump brace-expansion patches to clear GHSA-3jxr / GHSA-mh99 - #1200
Draft
cursor[bot] wants to merge 1 commit into
Draft
build(deps): bump brace-expansion patches to clear GHSA-3jxr / GHSA-mh99#1200cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
….0.9 Refreshes stale yarn.lock resolutions for brace-expansion to pick up the latest patch releases across the three version lines that satisfy existing semver ranges (^1.1.7, ^2.0.1, ^5.0.5) held by minimatch@3.1.5, minimatch@5.1.9 and minimatch@10.2.5 (all dev/build tooling chains). Clears the following Dependabot alerts: - GHSA-3jxr-9vmj-r5cp (high) — brace-expansion DoS via exponential-time expansion of consecutive non-expanding {} groups (fixed in 2.1.2 / 5.0.7) - GHSA-mh99-v99m-4gvg (high) — brace-expansion DoS via unbounded expansion length causing an out-of-memory process crash (fixed in 1.1.17 / 2.1.3 / 5.0.8) No manifest / resolutions changes; existing tests and build pass. Co-authored-by: Andreja Kogovsek <andrejak@users.noreply.github.com>
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.
What & why
Refreshes stale
yarn.lockresolutions forbrace-expansionacross the three version lines currently pulled in as a transitive dep (all viaminimatch, all in dev/build tooling chains). Yarn had cached older versions even though the semver ranges (^1.1.7,^2.0.1,^5.0.5) held by the parent packages already accept newer patches on npm.^1.1.7minimatch@3.1.5^2.0.1minimatch@5.1.9^5.0.5minimatch@10.2.5Clears the following Dependabot alerts (both
high):{}groups (fixed in2.1.2/5.0.7).1.1.17/2.1.3/5.0.8).How
Deleted the three stale
brace-expansionblocks fromyarn.lockand re-ranyarn install, which re-resolved the ranges to the newest patch releases on the registry. Nopackage.json/resolutionschanges — the ranges upstream already allow these versions.Risk
Low. All three consumers (
minimatch@3,minimatch@5,minimatch@10) are only reached via dev/build tooling (jest, semantic-release helpers, node-gyp, etc.). No runtime code path in the published@duffel/apibundle uses these. Both advisories are DoS-only (not RCE).Verification
yarn npm audit --recursive --all— no remaining real CVEs on root (only pre-existing deprecation notices foreslint@8,glob@7,inflight,rimraf@3, etc., which are not vulnerabilities).yarn test— all 37 suites / 139 tests pass.yarn build— succeeds.Not addressed here
examples/with-nextstill hasnext@16.2.11pulling inpostcss@8.4.31(GHSA-qx2v / GHSA-6g55 / GHSA-r28c) andsharp@0.34.5(GHSA-f88m). The latest stablenext@16.2.12still pins these same versions, so it cannot be cleared by a lockfile refresh alone. This is called out on Slack for follow-up rather than force-overriding a Next.js internal dependency in an example app.