Skip to content

[DependOnMe] Critical security fix - 1 issue(s) - #354

Open
dependonme-github-app[bot] wants to merge 2 commits into
masterfrom
dependonme/bulk-fix-e51c736a
Open

dependonme-github-app[bot] wants to merge 2 commits into
masterfrom
dependonme/bulk-fix-e51c736a

Conversation

@dependonme-github-app

Copy link
Copy Markdown

Bulk Security Fix

This pull request was automatically generated by DependOnMe to fix 1 critical security issue(s).

Issues Fixed

  • Critical: 1
  • High: 0
  • Medium: 0
  • Low: 0

Files Modified

  • package.json

AI Summary

Fixed 1 security issue:

CVE-2026-54466websocket-driver: Message corruption via abuse of protocol length headers

  • Change: Added "websocket-driver": "0.7.5" to the overrides section in package.json
  • Reason: websocket-driver versions prior to 0.7.5 are vulnerable to message corruption attacks via malformed protocol length headers. An attacker could abuse this to corrupt WebSocket messages.
  • Approach: Used npm overrides (consistent with the existing pattern in this package.json) to force all transitive consumers of websocket-driver to use the patched version 0.7.5. This is appropriate because websocket-driver is a transitive dependency (used internally by packages like jest-websocket-mockmock-socket and potentially webpack dev tooling), and there is no single root package upgrade that would resolve this across all dependency paths.
  • No breaking changes expected: 0.7.5 is a patch-level fix to the existing 0.7.x line, maintaining full API compatibility.

⚠️ Risk Assessment:

  • Low Risk: This is a patch version update (0.7.x → 0.7.5) with no breaking API changes. The fix only addresses the protocol length header parsing bug. The override pattern is already heavily used in this repository and is consistent with the existing maintenance approach.

🧪 Testing Checklist:

  • Run npm install (or npm ci) to regenerate package-lock.json with the overridden version
  • Verify websocket-driver@0.7.5 appears in package-lock.json (no older versions should remain)
  • Run the full test suite: npm test
  • Specifically run any WebSocket-related tests (using jest-websocket-mock)
  • Run npm run build to confirm the production build succeeds
  • Run npm run dev and verify the development server starts correctly
  • Run npm audit to confirm the CVE is no longer flagged after the lock file is regenerated

Manual Steps Required:

  1. After applying the package.json change, run npm install to regenerate package-lock.json
  2. Commit both package.json and the updated package-lock.json

This PR was created by DependOnMe - Automated Security Issue Management

dependonme-github-app Bot and others added 2 commits July 18, 2026 17:34
Automatically regenerated by DependOnMe bot after package.json update.
Branch: dependonme/bulk-fix-e51c736a
Package manager: npm
@vercel

vercel Bot commented Jul 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
deriv-api-docs Ready Ready Preview Jul 18, 2026 5:42pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants