fix(deps): bump ws to 8.21.0 (GHSA-96hv-2xvq-fx4p)#112
Merged
Conversation
Memory-exhaustion DoS from tiny fragments/data chunks affects ws 8.0.0 - 8.20.1. The declared range (^8.18.0) already permits the patched 8.21.0; only the lockfile pin moves. Usage is transitive loopback-only client, never an exposed ws server, so real risk is low, but the patch is direct and API-compatible. Unblocks deps-audit on main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ClodoCapeo
force-pushed
the
keeper/ws-8.21.0-cve-fix
branch
from
236786f to
4fc73b1
Compare
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.
Contexte
deps-auditéchoue surmain:npm audit --omit=dev --audit-level=highflagge ws (GHSA-96hv-2xvq-fx4p, DoS mémoire par petits fragments/chunks, affecte8.0.0 - 8.20.1). Cela bloque le merge de PR #111.Fix
Bump
ws→8.21.0(patché). La plage déclarée dans les workspaces (pulsar-bundle-full,pulsar-bundle,pulsar-client) est déjà^8.18.0, qui permet8.21.0: seul le pin du lockfile bouge, aucunpackage.jsonnioverridesrequis.Vérification locale
npm audit --omit=dev --audit-level=high→ found 0 vulnerabilitiesnpm ci --dry-run→ lockfile synchro, pas de driftobs-websocket-js ^8.13.0,isomorphic-ws *, devDep^8.18.0(patch API-compatible)Risque
Faible : usage transitif client loopback-only, jamais serveur
wsexposé. Patch direct → pas de raison d'accepter le risque (verdict Bastion).Une fois mergé, PR #111 peut rebaser et reverdir sa CI.