Quasar
Quasar Framework: SSR/SSG dev error page discloses the full shell environment and its </script> escape is bypassable
Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0, renderSSRError() in utils/render-ssr-error/src/index.js used diagnostic data from utils/render-ssr-error/src/env.js to serialize process.env, request headers, and cookies into the HTTP page returned by serve.devError(), while the development server listened on all interfaces by default. Any network-adjacent client that reaches an SSR or SSG render failure through this development-only error path can obtain shell environment secrets. The renderer escaped only one exact lowercase script closing-tag spelling, so case variants and valid closing-tag delimiter variants in reflected diagnostic data could terminate the script element and inject markup; executing the injected code in a developer browser additionally requires the payload to accompany that developer's request. This issue is fixed in @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.23.3
Fixed in 2.23.3
- < 2.2.4
Fixed in 2.2.4
- < 3.3.0
Fixed in 3.3.0
Mitigation
Upgrade quasar to 2.23.3 or later.
Upgrade render-ssr-error to 2.2.4 or later.
Upgrade app-vite to 3.3.0 or later.
References
- Vendor advisory github.com/quasarframework/quasar/security/adv…
- Patch github.com/quasarframework/quasar/commit/61c2b…
- Release notes github.com/quasarframework/quasar/releases/tag…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.