chore(deps): update dependency @nuxt/devtools to v1.3.9 [security]
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @nuxt/devtools (source) | 1.3.1 -> 1.3.9 |
GitHub Vulnerability Alerts
CVE-2024-23657
Summary
Nuxt Devtools is missing authentication on the getTextAssetContent RPC function which is vulnerable to path traversal. Combined with a lack of Origin checks on the WebSocket handler, an attacker is able to interact with a locally running devtools instance and exfiltrate data abusing this vulnerability.
In certain configurations an attacker could leak the devtools authentication token and then abuse other RPC functions to achieve RCE.
Details
The getTextAssetContent function does not check for path traversals (source), this could allow an attacker to read arbitrary files over the RPC WebSocket.
The WebSocket server does not check the origin of the request (source) leading to CSWSH. This may be intentional to allow certain configurations to work correctly.
Nuxt Devtools authentication tokens are placed within the home directory of the current user (source).
In the scenario that:
- The user has a Nuxt3 Project running
- Devtools is enabled and running
- The project is placed within the users home directory.
- The user visits a malicious webpage
- User has authenticated with devtools at least once
The malicious webpage can connect to the Devtools WebSocket, perform a directory traversal brute force to find the authentication token, then use the authenticated writeStaticAssets function to create a new Component, Nitro Handler or app.vue file which will run automatically as the file is changed.
PoC
POC will exploit the Devtools server on localhost:3000 (you may need to manually restart the server as the restart hook does not always work).
POC: https://devtools-exploit.pages.dev
- Create a new project with nuxt.new.
- Place the project inside your home directory.
- Run
pnpm run dev. - Open the POC page.
The POC will:
- Identify devtools version.
- Leak your devtools token.
- Create a new server handler with an insecure eval.
Impact
- All new Nuxt projects by default (devtools is enabled) are vulnerable to arbitrary file read.
- Certain Nuxt configurations are vulnerable to Remote Code Execution
Release Notes
nuxt/devtools (@nuxt/devtools)
v1.3.9
Bug Fixes
- capture for circular reference in state editor (841fd76)
- introduce
client.revisionto trigger state editor update (418a22e) - modules: update compatibility check for Nuxt 3 and 4 (#689) (2354da7)
- use
ofetchforfast-npm-meta(4188f8d)
v1.3.8
Performance Improvements
- avoid deps on
npm-registry-fetch, save install size (3d74691)
v1.3.7
Bug Fixes
- OpenGraph layout (#685) (760f149)
- scrollable sidebar (#682) (df459f9)
- server-routes: unable to clear all params (#684) (d88b003)
Features
Performance Improvements
- use
npm-registry-fetchinstead ofpacoteto deduce the package size (a049c52)
v1.3.6
Features
v1.3.5
Bug Fixes
- downgrade module-builder (de79dc4)
v1.3.4
Bug Fixes
v1.3.3
Bug Fixes
v1.3.2
Bug Fixes
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Deploying nuxt-devtools with
Cloudflare Pages
| Latest commit: |
399cbf9
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://74e0ab2c.nuxt-devtools.pages.dev |
| Branch Preview URL: | https://renovate-npm-nuxt-devtools-v.nuxt-devtools.pages.dev |