Skip to content

Bump websocket-driver 0.7.4 -> 0.7.5 in vrs/website - #265

Closed
kongchen1992 wants to merge 1 commit into
facebookresearch:mainfrom
kongchen1992:export-D116379479
Closed

Bump websocket-driver 0.7.4 -> 0.7.5 in vrs/website#265
kongchen1992 wants to merge 1 commit into
facebookresearch:mainfrom
kongchen1992:export-D116379479

Conversation

@kongchen1992

@kongchen1992 kongchen1992 commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Summary:
websocket-driver@0.7.4 in arvr/libraries/vrs/website/yarn.lock is flagged by
CVE-2026-54466
(CWE-130, Improper Handling of Length Parameter Inconsistency, CVSS >= 7). The fixed
version is 0.7.5.

The VM auto-remediator (VMRemediatorTPLUpgrader) already tried and failed on this
asset — it fed the asset XID to the upgrader as if it were a path and bailed with
Invalid value: Project path 'arvr/libraries/vrs/website/yarn.lock#pkg:npm/websocket-driver@..' does not exist.
So this is the manual bump.

websocket-driver is transitive-only here, pulled in twice via webpack-dev-server:

  • sockjs@0.3.24 -> websocket-driver@^0.7.4
  • faye-websocket@0.11.4 -> websocket-driver@>=0.5.1

Both ranges already admit 0.7.5, so the lockfile is the only place the version actually
moves. Per PiotrBrzyski's review, this also adds a resolutions floor in package.json so
the fix survives a future re-resolve — see the test plan for a concrete case where the
lockfile alone would silently regress. That matches what the other docusaurus sites in
fbsource do for this exact package (fbcode/whatsapp/elp/website uses ^0.7.5,
fbcode/buck2/website uses >=0.7.5 <0.8.0), and the file already carries six
resolutions entries of the same shape.

0.7.5 keeps the same dependency set (http-parser-js, safe-buffer,
websocket-extensions), so no other lockfile entries move.

Reviewed By: PiotrBrzyski

Differential Revision: D116379479

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 17, 2026
@meta-codesync

meta-codesync Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

@kongchen1992 has exported this pull request. If you are a Meta employee, you can view the originating Diff in D116379479.

Summary:
`websocket-driver@0.7.4` in `arvr/libraries/vrs/website/yarn.lock` is flagged by
[CVE-2026-54466](https://www.internalfb.com/intern/vulnerability_management/vulnerabilities/CVE-2026-54466)
(CWE-130, Improper Handling of Length Parameter Inconsistency, CVSS >= 7). The fixed
version is 0.7.5.

The VM auto-remediator (`VMRemediatorTPLUpgrader`) already tried and failed on this
asset — it fed the asset XID to the upgrader as if it were a path and bailed with
`Invalid value: Project path 'arvr/libraries/vrs/website/yarn.lock#pkg:npm/websocket-driver@..' does not exist.`
So this is the manual bump.

`websocket-driver` is transitive-only here, pulled in twice via `webpack-dev-server`:
- `sockjs@0.3.24` -> `websocket-driver@^0.7.4`
- `faye-websocket@0.11.4` -> `websocket-driver@>=0.5.1`

Both ranges already admit 0.7.5, so the lockfile is the only place the version actually
moves. Per PiotrBrzyski's review, this also adds a `resolutions` floor in `package.json` so
the fix survives a future re-resolve — see the test plan for a concrete case where the
lockfile alone would silently regress. That matches what the other docusaurus sites in
fbsource do for this exact package (`fbcode/whatsapp/elp/website` uses `^0.7.5`,
`fbcode/buck2/website` uses `>=0.7.5 <0.8.0`), and the file already carries six
`resolutions` entries of the same shape.

0.7.5 keeps the same dependency set (`http-parser-js`, `safe-buffer`,
`websocket-extensions`), so no other lockfile entries move.

Reviewed By: PiotrBrzyski

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

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant