Debian Package Tracker
Register | Log in
Subscribe

node-websocket-driver

WebSocket protocol handler with pluggable I/O for Node.js

Choose email to subscribe with

general
  • source: node-websocket-driver (main)
  • version: 0.7.5+~cs0.6.14-1
  • maintainer: Debian Javascript Maintainers (archive) (DMD)
  • uploaders: Tim Retout [DMD]
  • arch: all
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • oldstable: 0.7.4+~cs0.6.7-2
  • stable: 0.7.4+~cs0.6.7-2
  • testing: 0.7.4+~cs0.6.14-1
  • unstable: 0.7.5+~cs0.6.14-1
versioned links
  • 0.7.4+~cs0.6.7-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.7.4+~cs0.6.14-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.7.5+~cs0.6.14-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • node-websocket-driver
action needed
2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:
  • CVE-2026-54466: websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.
  • CVE-2026-54490: websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, if this library is used with the permessage-deflate extension, a WebSocket server or client can be made to accept messages that are larger than the configured maximum message size because the limit is checked against the message frames' length headers, which give the size of the compressed data, not the size after decompression in lib/websocket/driver/hybi.js. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage. This issue is fixed in version 0.7.5.
Created: 2026-07-18 Last update: 2026-08-19 00:31
2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:
  • CVE-2026-54466: websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.
  • CVE-2026-54490: websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, if this library is used with the permessage-deflate extension, a WebSocket server or client can be made to accept messages that are larger than the configured maximum message size because the limit is checked against the message frames' length headers, which give the size of the compressed data, not the size after decompression in lib/websocket/driver/hybi.js. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage. This issue is fixed in version 0.7.5.
Created: 2026-07-18 Last update: 2026-08-19 00:31
1 new commit since last upload, is it time to release? normal
vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:
commit 7271324af697a0b03e55ae2faa747839e5a1ebb2
Author: Xavier Guimard <yadd@debian.org>
Date:   Tue Aug 18 19:02:53 2026 +0200

    Add missing CVE in cheangelog


https://salsa.debian.org/api/v4/projects/js-team%2Fnode-websocket-driver API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.
Created: 2026-08-18 Last update: 2026-08-18 21:30
2 low-priority security issues in trixie low

There are 2 open security issues in trixie.

2 issues left for the package maintainer to handle:
  • CVE-2026-54466: (needs triaging) websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.
  • CVE-2026-54490: (needs triaging) websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, if this library is used with the permessage-deflate extension, a WebSocket server or client can be made to accept messages that are larger than the configured maximum message size because the limit is checked against the message frames' length headers, which give the size of the compressed data, not the size after decompression in lib/websocket/driver/hybi.js. This can lead to applications accepting larger messages than expected and exceeding their intended resource usage. This issue is fixed in version 0.7.5.

You can find information about how to handle these issues in the security team's documentation.

Created: 2026-07-18 Last update: 2026-08-19 00:31
testing migrations
  • excuses:
    • Migration status for node-websocket-driver (0.7.4+~cs0.6.14-1 to 0.7.5+~cs0.6.14-1): Waiting for test results or another package, or too young (no action required now - check later)
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for node-faye-websocket/0.11.4-2: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-sockjs/0.3.24+~0.3.36-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Autopkgtest for node-websocket-driver/0.7.5+~cs0.6.14-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Test triggered
    • ∙ ∙ Too young, only 0 of 5 days old
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-websocket-driver.html
    • ∙ ∙ Reproduced on amd64 - info
    • ∙ ∙ Reproduced on arm64 - info
    • ∙ ∙ Reproduced on armhf - info
    • ∙ ∙ Reproduced on i386 - info
    • Not considered
news
[rss feed]
  • [2026-08-18] Accepted node-websocket-driver 0.7.5+~cs0.6.14-1 (source) into unstable (Xavier Guimard)
  • [2026-03-21] node-websocket-driver 0.7.4+~cs0.6.14-1 MIGRATED to testing (Debian testing watch)
  • [2026-03-16] Accepted node-websocket-driver 0.7.4+~cs0.6.14-1 (source) into unstable (Xavier Guimard)
  • [2021-08-16] node-websocket-driver 0.7.4+~cs0.6.7-2 MIGRATED to testing (Debian testing watch)
  • [2021-08-07] Accepted node-websocket-driver 0.7.4+~cs0.6.7-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2021-08-03] node-websocket-driver REMOVED from testing (Debian testing watch)
  • [2021-07-31] Accepted node-websocket-driver 0.7.4+~cs0.6.7-1 (source) into experimental (Yadd) (signed by: Xavier Guimard)
  • [2021-01-10] node-websocket-driver 0.3.5-1.1 MIGRATED to testing (Debian testing watch)
  • [2021-01-07] Accepted node-websocket-driver 0.3.5-1.1 (source) into unstable (Holger Levsen)
  • [2014-09-14] node-websocket-driver 0.3.5-1 MIGRATED to testing (Britney)
bugs [bug history graph]
  • all: 1
  • RC: 0
  • I&N: 1
  • M&W: 0
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 0.7.4+~cs0.6.14-1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing