Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update devdependency @nuxt/devtools to v1 [security] #194

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 6, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/devtools (source) ^0.8.5 -> ^1.3.9 age adoption passing confidence

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

  1. Create a new project with nuxt.new.
  2. Place the project inside your home directory.
  3. Run pnpm run dev.
  4. 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

Compare Source

Bug Fixes
  • capture for circular reference in state editor (841fd76)
  • introduce client.revision to trigger state editor update (418a22e)
  • modules: update compatibility check for Nuxt 3 and 4 (#​689) (2354da7)
  • use ofetch for fast-npm-meta (4188f8d)

v1.3.8

Compare Source

Performance Improvements
  • avoid deps on npm-registry-fetch, save install size (3d74691)

v1.3.7

Compare Source

Bug Fixes
Features
Performance Improvements
  • use npm-registry-fetch instead of pacote to deduce the package size (a049c52)

v1.3.6

Compare Source

Features

v1.3.5

Compare Source

Bug Fixes
  • downgrade module-builder (de79dc4)

v1.3.4

Compare Source

Bug Fixes

v1.3.3

Compare Source

Bug Fixes

v1.3.2

Compare Source

Bug Fixes

v1.3.1

Compare Source

Bug Fixes
  • module builder chunk path patch (87199a1)

v1.3.0

Compare Source

Bug Fixes
Features

v1.2.0

Compare Source

Bug Fixes

1.1.5 (2024-03-28)

Features

1.1.4 (2024-03-26)

Bug Fixes

1.1.3 (2024-03-21)

Bug Fixes

1.1.2 (2024-03-21)

Bug Fixes
Features

1.1.1 (2024-03-20)

Bug Fixes

v1.1.5

Compare Source

Features

v1.1.4

Compare Source

Bug Fixes

v1.1.3

Compare Source

Bug Fixes

v1.1.2

Compare Source

Bug Fixes
Features

v1.1.1

Compare Source

Bug Fixes

v1.1.0

Compare Source

Bug Fixes
Features

1.0.8 (2024-01-11)

Bug Fixes

1.0.7 (2024-01-11)

Bug Fixes
  • devtools: update default types to module.d.ts/.mts (#​559) (2ecd32c)
  • make twitter og tags optional (41ee5ec)
  • open-graph: fix type error, close #​563 (c63055a)
  • support iframeProps option for CSP, fix Stackblitz (0eb7a82)
  • timeline-helper-wrapper: Fix return value in timeline wrapper for promises (#​567) (0645e35)
  • update title of Eye Dropper command (#​558) (ea58139)
Features
  • server-routes: implement persisting input values in localStorage (#​545) (67dbf65)

1.0.6 (2023-12-13)

Bug Fixes

1.0.5 (2023-12-07)

Bug Fixes
  • allow iframe to work in stricter cross-origin policy (7ec0d3c)
  • devtools: don't enable devtools when in test mode (#​532) (3a7f143)
Features

1.0.4 (2023-11-27)

Bug Fixes
  • pip: check for https support (#​522) (5360cf4)
  • require auth token with getImageMeta and getTextAssetContent (69316c4)
  • require token for restartNuxt (09384af)
Features

1.0.3 (2023-11-20)

Bug Fixes
Features
  • disable devtools in test mode (51e8de6)

1.0.2 (2023-11-11)

Bug Fixes
  • do not show false connecting overlay on legacy Vite, close #​497 (a48c248)
  • timeline: do not inject for macro module, close #​507 (923edaf)

1.0.1 (2023-11-09)

Bug Fixes

v1.0.8

Compare Source

Bug Fixes

v1.0.7

Compare Source

Bug Fixes
  • devtools: update default types to module.d.ts/.mts (#​559) (2ecd32c)
  • make twitter og tags optional (41ee5ec)
  • open-graph: fix type error, close #​563 (c63055a)
  • support iframeProps option for CSP, fix Stackblitz (0eb7a82)
  • timeline-helper-wrapper: Fix return value in timeline wrapper for promises (#​567) (0645e35)
  • update title of Eye Dropper command (#​558) (ea58139)
Features
  • server-routes: implement persisting input values in localStorage (#​545) (67dbf65)

v1.0.6

Compare Source

Bug Fixes

v1.0.5

Compare Source

Bug Fixes
  • allow iframe to work in stricter cross-origin policy (7ec0d3c)
  • devtools: don't enable devtools when in test mode (#​532) (3a7f143)
Features

v1.0.4

Compare Source

Bug Fixes
  • pip: check for https support (#​522) (5360cf4)
  • require auth token with getImageMeta and getTextAssetContent (69316c4)
  • require token for restartNuxt (09384af)
Features

v1.0.3

Compare Source

Bug Fixes
Features
  • disable devtools in test mode (51e8de6)

v1.0.2

Compare Source

Bug Fixes
  • do not show false connecting overlay on legacy Vite, close #​497 (a48c248)
  • timeline: do not inject for macro module, close #​507 (923edaf)

v1.0.1

Compare Source

Bug Fixes

v1.0.0

Compare Source

Features

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.

@renovate renovate bot requested a review from Hebilicious as a code owner August 6, 2024 07:12
Copy link

cloudflare-workers-and-pages bot commented Aug 6, 2024

Deploying authjs-nuxt with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0f98af8
Status:🚫  Build failed.

View logs

@renovate renovate bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from 309238b to 40c27c0 Compare October 9, 2024 11:46
@renovate renovate bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 2 times, most recently from ce5e4a9 to 5c3194b Compare October 28, 2024 20:11
@renovate renovate bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 5c3194b to a355e07 Compare December 2, 2024 12:33
Copy link

changeset-bot bot commented Dec 2, 2024

⚠️ No Changeset found

Latest commit: 0f98af8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from a355e07 to 126cd9a Compare December 2, 2024 16:41
@renovate renovate bot changed the title chore(deps): update devdependency @nuxt/devtools to v1 [security] chore(deps): update devdependency @nuxt/devtools to v1 [security] - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/npm-nuxt-devtools-vulnerability branch December 8, 2024 18:59
@renovate renovate bot changed the title chore(deps): update devdependency @nuxt/devtools to v1 [security] - autoclosed chore(deps): update devdependency @nuxt/devtools to v1 [security] Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 3 times, most recently from 98e8a2c to d642886 Compare December 15, 2024 15:25
@renovate renovate bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch 3 times, most recently from 1ee0696 to 1fbfb22 Compare December 22, 2024 15:48
@renovate renovate bot force-pushed the renovate/npm-nuxt-devtools-vulnerability branch from 1fbfb22 to 0f98af8 Compare December 22, 2024 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants