Skip to content
Fencer Intel
critical 9.1

GHSA-v36f-rjg3-3v46 json

Message corruption and denial of service triggered by crafted client message

published 16h ago modified 16h ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository faye/websocket-driver-node. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
9.1
version 3.1, the maintainers
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of faye/websocket-driver-node for websocket-driver: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • npm websocket-driver >=0.8.0

Is GHSA-v36f-rjg3-3v46 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
the maintainers 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm websocket-driver
<0.8.0
>=0.8.0

Classification

Weakness
  • CWE-248 Uncaught Exception
  • CWE-456 Missing Initialization of a Variable

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of faye/websocket-driver-node published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.