GHSA-HGRW-M6VC-WRWR
Cloudflare Pages Adapter Stores private/no-store Responses in Shared Worker Cache (Cache Poisoning leading to Cross-User Information Disclosure)
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 1.20.2 | @builder.io/qwik-city · -7 d desde divulgación | |
| Divulgación | Publicada | GHSA-HGRW-M6VC-WRWR divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Description
In `@builder.io/qwik-city` 1.20.0, the Cloudflare Pages adapter attempts to call `cache.put()` for every successful response containing a `Cache-Control` header. This condition is broader than necessary because it does not inspect whether the header contains directives such as `private`, `no-store`, or `no-cache`.
This behavior does not establish that Cloudflare stores private responses. Cloudflare’s Workers Cache API applies the response’s `Cache-Control` directives when processing `cache.put()` and reports an error when those directives prohibit caching. Qwik City emits `Cache-Control: no-cache, private` for `requestEv.cacheControl('private')` and `Cache-Control: no-store` for `{ noStore: true }`; both therefore prevent the claimed shared-cache entry from being created. ([Cloudflare Cache API https://developers.cloudflare.com/workers/runtime-apis/cache/](https://developers.cloudflare.com/workers/runtime-apis/cache/), [RFC 9111 https://www.rfc-editor.org/rfc/rfc9111.html](https://www.rfc-editor.org/rfc/rfc9111.html))
The supplied verification evaluates only Qwik’s condition for calling `cache.put()` using Node’s Web API implementation. It does not execute Cloudflare’s Cache API, confirm a successful write, or show a subsequent request retrieving the stored response. The absence of a `Vary` header matters only after a response has been stored, so it does not establish the claimed cross-user replay.
Impact
No cross-user disclosure or other confidentiality impact has been demonstrated. Under Cloudflare’s documented behavior, responses marked `private` or `no-store` are not entered into the shared cache, preventing another visitor from retrieving them through `cache.match()`.
Filtering uncacheable directives before calling `cache.put()` would still be useful defense in depth. It would avoid unnecessary rejected operations and protect against incomplete cache implementations in tests or third-party emulators. Those benefits do not support classifying the behavior as CWE-524, assigning CVSS 7.5, or publishing a High-severity advisory without an actual Cloudflare deployment demonstrating that a prohibited response was both stored and served to a different requester.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npm@builder.io/qwik-city |
Corregida | 1.20.2 | -7 d | 1.20.4 no afectada |
1.20.2Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/QwikDev/qwik/security/advisories/GHSA-hgrw-m6vc-wrwrLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
