nuxt 3.21.9

Direct Vulnerabilities

Known vulnerabilities in the nuxt 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

Vulnerability	Vulnerable Version
M Information Exposure Affected versions of this package are vulnerable to Information Exposure via the Chrome DevTools workspace endpoint when the development server is bound to a network-reachable interface and `experimental.chromeDevtoolsProjectSettings` is enabled. An attacker can obtain the absolute project root path and a persistent workspace UUID by sending unauthenticated requests to the endpoint. This is only exploitable if the development server is accessible beyond loopback and the relevant experimental feature is enabled. How to fix Information Exposure? Upgrade `nuxt` to version 3.21.10, 4.5.1 or higher.	>=3.21.7 <3.21.10>=4.4.7 <4.5.1
H Incorrect Authorization Affected versions of this package are vulnerable to Incorrect Authorization in the route rule matching. An attacker can gain unauthorized access to protected pages and sensitive data by crafting requests to mixed-case paths that bypass authentication middleware. How to fix Incorrect Authorization? Upgrade `nuxt` to version 3.21.10, 4.5.1 or higher.	>=3.21.7 <3.21.10>=4.4.7 <4.5.1
H Improper Validation of Specified Quantity in Input Affected versions of this package are vulnerable to Improper Validation of Specified Quantity in Input via the `v-for` in server-side rendering of islands or server components. An attacker can cause the server to allocate excessive memory and crash by sending a request with a large integer value for a prop used in `v-for`, leading to unbounded expansion during rendering. This can be exploited remotely without authentication by crafting requests that trigger excessive iteration counts in the rendering logic. How to fix Improper Validation of Specified Quantity in Input? Upgrade `nuxt` to version 3.21.10, 4.5.1 or higher.	>=3.1.0 <3.21.10>=4.0.0 <4.5.1
M Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') Affected versions of this package are vulnerable to Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') via the `as` prop in server island components that forward attacker-controlled values into dynamic component resolution. An attacker can instantiate any globally-registered Vue component or native HTML element by supplying a crafted value, potentially leading to unauthorized access or manipulation of application behavior. Note: This is only exploitable if a server island component forwards untrusted input into a dynamic component path, either explicitly or via attribute fallthrough when the island's root is a polymorphic component. How to fix Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')? Upgrade `nuxt` to version 3.21.10, 4.5.1 or higher.	>=3.1.0 <3.21.10>=4.0.0 <4.5.1
C Arbitrary Code Injection Affected versions of this package are vulnerable to Arbitrary Code Injection via the `/__nuxt_island/` endpoint when `vue.runtimeCompiler` is enabled and a server island component forwards attacker-controlled props into Vue's dynamic component resolution. An attacker can execute arbitrary code on the server by injecting a `template` key into the island props, which is then compiled and executed in the server process. Note: This is only exploitable if `vue.runtimeCompiler` is set to true and the application has a server island component that forwards attacker-controlled values into a dynamic-component path, either explicitly or via attribute fallthrough. How to fix Arbitrary Code Injection? Upgrade `nuxt` to version 3.21.10, 4.5.1 or higher.	>=3.4.0 <3.21.10>=4.0.0 <4.5.1
H Allocation of Resources Without Limits or Throttling Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the `island renderer endpoint` when attacker-controlled input is decoded and hashed before URL-resident hash validation. An attacker can exhaust CPU resources and degrade or stall the server by sending large, deeply nested JSON payloads to the endpoint, causing the server to process and reject the request only after significant computation. Note: This is only exploitable if the server is accessible to unauthenticated users and does not enforce request body size or nesting depth limits. How to fix Allocation of Resources Without Limits or Throttling? Upgrade `nuxt` to version 3.21.10, 4.5.1 or higher.	>=3.1.0 <3.21.10>=4.0.0 <4.5.1

Vulnerability

Vulnerable Version

Information Exposure

Affected versions of this package are vulnerable to Information Exposure via the Chrome DevTools workspace endpoint when the development server is bound to a network-reachable interface and experimental.chromeDevtoolsProjectSettings is enabled. An attacker can obtain the absolute project root path and a persistent workspace UUID by sending unauthenticated requests to the endpoint. This is only exploitable if the development server is accessible beyond loopback and the relevant experimental feature is enabled.

How to fix Information Exposure?