@nuxt/vite-server@4.6.2

Experimental pure Vite server builder for Nuxt

  • latest version

    4.6.4

  • latest non vulnerable version

  • first published

    2 months ago

  • latest version published

    15 days ago

  • licenses detected

  • Direct Vulnerabilities

    Known vulnerabilities in the @nuxt/vite-server package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Interpretation Conflict

    @nuxt/vite-server is an Experimental pure Vite server builder for Nuxt

    Affected versions of this package are vulnerable to Interpretation Conflict via routeRules matching in the route-rules resolution logic, which compares route rules against the raw request path while leaving encoded slashes (%2F) encoded. A catch-all page route such as app/pages/[...slug].vue or a custom multi-segment page route decodes %2F into a route parameter, creating a mismatch where getRouteRules returns an incomplete result. An unauthenticated attacker can send a request with %2F in the path to render a page without the redirect, headers, proxy, ssr, noScripts, appMiddleware, or appLayout rules configured for the decoded path.

    Note: Protected content is exposed only when the page interprets the decoded parameter accordingly: a custom multi-segment parameter resolves the decoded path directly, while a repeatable catch-all exposes it only when the page joins the slug array with /; pages that load content via route.path are not affected because that property retains the encoding.

    How to fix Interpretation Conflict?

    Upgrade @nuxt/vite-server to version 4.6.4 or higher.

    >=4.6.0 <4.6.4