Skip to content

Denial of Service in soketi

High severity GitHub Reviewed Published Jan 7, 2022 in soketi/soketi • Updated Feb 3, 2023

Package

npm @soketi/soketi (npm)

Affected versions

< 0.24.1

Patched versions

0.24.1

Description

Impact

What kind of vulnerability is it? Who is impacted?

There was a wrong behavior when reading POST requests, making the server crash if it couldn't read the body. In case a POST request was sent to any endpoint of the server with an empty body, even unauthenticated with the Pusher Protocol, it would simply just crash the server for trying to send a response after the request closed.

All users that run the server are affected by it and it's highly recommended to upgrade to the latest patch.

Patches

Has the problem been patched? What versions should users upgrade to?

Updating to at least 0.24.1 or the latest version.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

No. Upgrading is the only solution.

References

Are there any links users can visit to find out more?

https://github.com/soketi/soketi/releases/tag/0.24.1

For more information

If you have any questions or comments about this advisory:

References

@rennokki rennokki published to soketi/soketi Jan 7, 2022
Reviewed Jan 7, 2022
Published to the GitHub Advisory Database Jan 8, 2022
Published by the National Vulnerability Database Jan 10, 2022
Last updated Feb 3, 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.174%
(56th percentile)

Weaknesses

CVE ID

CVE-2022-21667

GHSA ID

GHSA-86ch-6w7v-v6xf

Source code

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