Qwik: Crashing any Qwik Server via Resource thenable
QwikDev qwik · @builder.io qwik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @builder.io/qwik npm |
|
|
| @qwik.dev/core npm |
|
|
QwikDev qwik · @builder.io qwik
| Product | Affected | Fixed in |
|---|---|---|
| @builder.io/qwik npm |
|
|
| @qwik.dev/core npm |
|
|
Qwik is a performance-focused JavaScript framework. Prior to @builder.io/qwik 1.20.0 and @qwik.dev/core 2.0.0-beta.37, default server-side qwik-json deserialization causes ResourceSerializer.$fill$ to pass resource._resolved to Promise.resolve without first rejecting attacker-controlled thenables. An unauthenticated request can provide a plain object whose then property is a QRL for an unregistered symbol, causing an orphaned asynchronous rejection that terminates Node.js under its default unhandled-rejection policy. A single request can crash a server, and repeated requests can keep replicas unavailable. This issue is fixed in @builder.io/qwik 1.20.0 and @qwik.dev/core 2.0.0-beta.37.
From the CVE record · GitHub_M
Default server-side qwik-json deserialization can pass an attacker-controlled thenable to Promise.resolve, causing an unhandled rejection that terminates Node.js under its default policy. An unauthenticated network request can crash a server without user interaction; repeated requests can keep replicas unavailable.
Check deployments using npm @builder.io/qwik before 1.20.0 or @qwik.dev/core before 2.0.0-beta37.