Quasar Framework: DOM Clobbering in Quasar openURL() SafariViewController Integration Causes Client-Side Denial of Service

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to 2.32.2, the openURL() utility in ui/src/utils/open-url/open-url.js trusted window.SafariViewController whenever that global existed in an iOS environment. Attacker-controlled HTML rendered by components such as QEditor can create a named SafariViewController element, causing browser named-property resolution to replace the expected native bridge object. A later openURL() call then invokes isAvailable() on the element, throws a TypeError, and disrupts external navigation, login redirects, payment redirects, and other URL-opening workflows. QSelect and QChatMessage HTML-rendering configurations can expose the same trigger when they render attacker-controlled HTML. This issue is fixed in version 2.32.2.

[ Fixes ]Fixes and patches

• quasar 2.32.2Fixed version · GitHub Advisories · npm package quasar: upgrade to 2.32.2 or later (affected <= 2.32.1)

[ Packages ]Affected open-source packages

• quasar npmAffected <= 2.32.1 · fixed in 2.32.2 · GHSA-89vp-x45c-52cq

[ References ]References

• github.com/quasarframework/quasar/commit/52d874bf55309dd3656fb02aed033ab025d477ec
• github.com/quasarframework/quasar/releases/tag/quasar-v2.32.2
• github.com/quasarframework/quasar/security/advisories/GHSA-89vp-x45c-52cq