fix(deps): bump js-yaml to patched 4.2.0/4.3.0 for DoS advisory (supersedes #10843)#10873
Open
mrveiss wants to merge 2 commits into
Open
fix(deps): bump js-yaml to patched 4.2.0/4.3.0 for DoS advisory (supersedes #10843)#10873mrveiss wants to merge 2 commits into
mrveiss wants to merge 2 commits into
Conversation
…rsedes #10843) js-yaml >=4.0.0,<=4.1.1 has a MODERATE quadratic-complexity DoS in merge-key handling (GHSA, patched in 4.2.0). Dependabot's security scan opened #10843 against main (security updates bypass dependabot.yml target-branch), leaving the deployed branch Dev_new_gui unpatched. This applies the same npm-validated lockfile changes directly on Dev_new_gui: - autobot-frontend: js-yaml 4.1.1 -> 4.2.0 (+ @redocly/openapi-core 1.34.15 -> 1.34.17, which pins js-yaml exactly at 4.2.0) - mcp-task-manager-server: js-yaml 4.1.1 -> 4.3.0 Both transitive/dev-only (build-time). Lockfile-only; no package.json changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
✅ SSOT Configuration Compliance: Passing🎉 No hardcoded values detected that have SSOT config equivalents! |
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.
Thinking Path
Dependabot #10843 (js-yaml DoS advisory) opened against
main— security updates bypassdependabot.yml'starget-branch, so the deployed branchDev_new_guistays unpatched. Retarget +@dependabot rebasejust reverts base tomain.Dev_new_gui's lockfiles are at the identical baseline as #10843's base, so the npm-validated hunks apply cleanly here.What Changed
autobot-frontend/package-lock.json:js-yaml4.1.1 → 4.2.0 (+@redocly/openapi-core1.34.15 → 1.34.17, which pins js-yaml exactly).autobot-infrastructure/.../mcp-task-manager-server/package-lock.json:js-yaml4.1.1 → 4.3.0.dev/build-time. Dropped an unrelatedlicense: ISC→GPL-3.0-onlymetadata flip from the Dependabot diff to keep this security-focused.Verification
>=4.0.0,<=4.1.1MODERATE quadratic-complexity DoS in merge-key handling → patched 4.2.0. Confirmed via GHsecurityVulnerabilitiesAPI.js-yaml-4.1.1.tgzrefs remain.Model Used
Opus 4.8 (1M context)
Supersedes #10843 (closed as mis-targeted at
main).