Quasar
Quasar Framework: Development TLS private keys are cached with overly permissive filesystem permissions
Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4, and @quasar/app-vite 3.3.0, the @quasar/ssl-certificate utility cached a combined private key and certificate PEM without explicitly applying owner-only filesystem permissions. Another local user able to read the cache can copy the key and impersonate a development TLS endpoint in an environment that trusts the certificate. The generated certificate was also CA-capable, carried unnecessarily broad key usages, and encoded the IPv6 loopback address as a DNS subject alternative name. This issue is fixed in @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.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
- < 3.3.0
Fixed in 3.3.0
- < 5.0.4
Fixed in 5.0.4
- < 2.1.0
Fixed in 2.1.0
Mitigation
Upgrade quasar to 2.23.3 or later.
Upgrade app-vite to 3.3.0 or later.
Upgrade cli to 5.0.4 or later.
Upgrade ssl-certificate to 2.1.0 or later.
References
- Vendor advisory github.com/quasarframework/quasar/security/adv…
- Patch github.com/quasarframework/quasar/commit/b7194…
- Release notes github.com/quasarframework/quasar/releases/tag…
1 more
- 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.