Files or Directories Accessible to External Parties@nuxt/schema is a Nuxt types and default configuration
Affected versions of this package are vulnerable to Files or Directories Accessible to External Parties via incorrect resolution of workspaceDir in packages/schema/src/utils/workspace-dir.ts, which can select a parent directory as the workspace root when that directory contains a stray lockfile (while the project is outside a Git repository and has no workspace file above it) or a pnpm-workspace.yaml without a packages list, or a deno.json/deno.jsonc without a workspace field. Because Vite's dev server permits /_nuxt/@fs/ requests for any path beneath workspaceDir, an unauthenticated attacker who can reach the dev server can read arbitrary files in that widened directory, including SSH keys, cloud credentials, and the Nuxt DevTools auth token.
Note: This is only exploitable when the dev server is reachable from an untrusted network (e.g. via --host, --tunnel, a published container port, or a proxy) and a parent directory contains one of the qualifying files described above; the default localhost bind and production builds are unaffected.
How to fix Files or Directories Accessible to External Parties? Upgrade @nuxt/schema to version 4.6.4, 4.0.0 or higher.
| >=3.5.0 <4.6.4>=3.5.0 <4.0.0 |
Files or Directories Accessible to External Parties@nuxt/schema is a Nuxt types and default configuration
Affected versions of this package are vulnerable to Files or Directories Accessible to External Parties via the findWorkspaceDir utility in packages/schema/src/config/common.ts, which can resolve workspaceDir to a parent directory that contains only a stray lockfile (e.g. package-lock.json, pnpm-lock.yaml) or a settings-only workspace file (e.g. pnpm-workspace.yaml without a packages list, or deno.json without a workspace field). Because the Vite dev server permits /_nuxt/@fs/ requests for any file under workspaceDir, an attacker who can reach the dev server can read arbitrary files in that parent directory and all subdirectories, including SSH keys, cloud credentials, and the Nuxt DevTools auth token.
Note: This is only exploitable when a parent directory contains a qualifying stray lockfile or settings file and the dev server is reachable from the network (e.g. via --host, --tunnel, a published container port, or a proxy onto the dev port); the default localhost bind limits exposure to local processes.
How to fix Files or Directories Accessible to External Parties? Upgrade @nuxt/schema to version 4.6.4, 4.0.0 or higher.
| >=3.5.0 <4.6.4>=3.5.0 <4.0.0 |