GHSA-vf6r-87q4-2vjf nuxt vulnerable to Cross-site Scripting in navigateTo if used after SSR

• npm nuxt: < 3.12.4 → fixed in 3.12.4

Summary The `navigateTo` function attempts to blockthe `javascript:` protocol, but does not correctly use API's provided by `unjs/ufo`. This library also contains parsing discrepancies. Details The function first tests to see if the specified URL has a protocol. This uses the unjs/ufo package for URL parsing. This function works effectively, and returns true for a `javascript:` protocol. After this, the URL is parsed using the `parseURL` function. This function will refuse to parse poorly formatted URLs. Parsing `javascript:alert(1)` returns null/"" for all values. Next, the protocol of the URL is then checked using the `isScriptProtocol` function. This function simply checks the input against a list of protocols, and does not perform any parsing. The combination of refusing to parse poorly formatted URLs, and not performing additional parsing means that script checks fail as no protocol can be found. Even if a protocol was identified, whitespace is not stripped in the `parseURL` implementation, bypassing the `isScriptProtocol` checks. Certain special protocols are identified at the top of `parseURL`. Inserting a newline or tab into this sequence will block the special protocol check, and bypass the latter checks. PoC POC - https://stackblitz.com/edit/nuxt-xss-navigateto?file=app.vue Attempt payload X, then attempt payload Y. Impact XSS, access to cookies, make requests on user's behalf. Recommendations As always with these bugs, the `URL` constructor provided by the browser is always the safest method of parsing a URL. Given the cross-platform requirements of nuxt/ufo a more appropriate solution is to make parsing consistent between functions, and to adapt parsing to be more consistent with the WHATWG URL specification. Note I've reported this vulnerability here as it is unclear if this is a bug in ufo or a misuse of the ufo library. This ONLY has impact after SSR has occurred, the `javascript:` protocol within a location header does not trigger XSS.