Skip to content

fastify/websocket vulnerable to uncaught exception via crash on malformed packet

High severity GitHub Reviewed Published Nov 4, 2022 in fastify/fastify-websocket • Updated Mar 29, 2023

Package

npm @fastify/websocket (npm)

Affected versions

>= 6.0.0, < 7.1.1
>= 5.0.0, < 5.0.1

Patched versions

7.1.1
5.0.1
npm fastify-websocket (npm)
<= 4.3.0
None

Description

Impact

Any application using @fastify/websocket could crash if a specific, malformed packet is sent.

All versions of fastify-websocket are also impacted. That module is deprecated, so it will not be patched.

Patches

This has been patched in v7.1.1 (fastify v4) and v5.0.1 (fastify v3).

Workarounds

No known workaround is available. However, it should be possible to attach the error handler manually.
The recommended path is upgrading to the patched versions.

Credits

marcolanaro for finding and patching this vulnerability

For more information

If you have any questions or comments about this advisory:

References

@mcollina mcollina published to fastify/fastify-websocket Nov 4, 2022
Published to the GitHub Advisory Database Nov 7, 2022
Reviewed Nov 7, 2022
Published by the National Vulnerability Database Nov 8, 2022
Last updated Mar 29, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.089%
(40th percentile)

Weaknesses

CVE ID

CVE-2022-39386

GHSA ID

GHSA-4pcg-wr6c-h9cq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.