Summary
Denial of Service in soketi
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
- Email us at [email protected]
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.
CVE-2022-21667 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.24.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Has the problem been patched? What versions should users upgrade to?
Updating to at least 0.24.1 or the latest version.
Frequently Asked Questions
- What is CVE-2022-21667? CVE-2022-21667 is a high-severity security vulnerability in @soketi/soketi (npm), affecting versions < 0.24.1. It is fixed in 0.24.1.
- How severe is CVE-2022-21667? CVE-2022-21667 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @soketi/soketi are affected by CVE-2022-21667? @soketi/soketi (npm) versions < 0.24.1 is affected.
- Is there a fix for CVE-2022-21667? Yes. CVE-2022-21667 is fixed in 0.24.1. Upgrade to this version or later.
- Is CVE-2022-21667 exploitable, and should I be worried? Whether CVE-2022-21667 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-21667 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-21667? Upgrade
@soketi/soketito 0.24.1 or later.