You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Opening a malicious website while running a Nuxt dev server could allow read-only access to code
Moderate severity
GitHub Reviewed
Published
Jan 24, 2025
in
nuxt/nuxt
•
Updated Jan 27, 2025
Summary
Nuxt allows any websites to send any requests to the development server and read the response due to default CORS settings.
Details
While Vite patched the default CORS settings to fix GHSA-vg6x-rcgg-rjx6, nuxt uses its own CORS handler by default (nuxt/nuxt#23995).
https://github.com/nuxt/nuxt/blob/7d345c71462d90187fd09c96c7692f306c90def5/packages/vite/src/client.ts#L257-L263
That CORS handler sets
Access-Control-Allow-Origin: *
.Important
If on an affected version, it may be possible to opt-out of the default Nuxt CORS handler by configuring
vite.server.cors
.PoC
nuxt dev
.http://localhost:3000/_nuxt/app.vue
(fetch('http://localhost:3000/_nuxt/app.vue')
) from a different origin page.Impact
Users with the default server.cors option using Vite builder may get the source code stolen by malicious websites
Additional Information
/__nuxt_vite_node__/manifest
//__nuxt_vite_node__/module
also seems to haveAccess-Control-Allow-Origin: *
, so it maybe also possible to exploit that handler.https://github.com/nuxt/nuxt/blob/7d345c71462d90187fd09c96c7692f306c90def5/packages/vite/src/vite-node.ts#L39
Although I didn't find a valid module id.
Note that this handler is probably also vulnerable to DNS rebinding attacks as I didn't find any host header checks.
References