CVE-2022-21667

soketi is an open-source WebSockets server. There is an unhandled case when reading POST requests which results in the server crashing if it could not read the body of a request. In the event that a POST request is sent to any endpoint of the server with an empty body, even unauthenticated with the Pusher Protocol, it will crash the server. All users that run the server are affected by this vulnerability and it's highly recommended to upgrade to the latest patch. There are no workarounds for this issue.

soketi is an open-source WebSockets server. There is an unhandled case when reading POST requests which results in the server crashing if it could not read the body of a request. In the event that a POST request is sent to any endpoint of the server with an empty body, even unauthenticated with the Pusher Protocol, it will crash the server. All users that run the server are affected by this vulnerability and it's highly recommended to upgrade to the latest patch. There are no workarounds for this issue.

### 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: * Open an issue in [the issues board](https://github.com/soketi/soketi/issues) * Email us at [alex@renoki.org](mailto:alex@renoki.org)

### 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: * Open an issue in [the issues board](https://github.com/soketi/soketi/issues) * Email us at [alex@renoki.org](mailto:alex@renoki.org)

soketi es un servidor de WebSockets de código abierto. Se presenta un caso no manejado cuando son leídas peticiones POST que hace que el servidor se bloquee si no puede leer el cuerpo de una petición. En el caso de que sea enviado una petición POST a cualquier endpoint del servidor con un cuerpo vacío, incluso sin autenticar con el protocolo Pusher, bloqueará el servidor. Todos los usuarios que ejecutan el servidor están afectados por esta vulnerabilidad y es muy recomendable actualizar al último parche. No se presentan medidas de mitigación para este problema