high
8.8
CWE
22 24
Advisory Published
CVE Published
Updated

CVE-2024-23657: Path Traversal: '../filedir' in Nuxt Devtools

First published: Mon Aug 05 2024(Updated: )

### 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)](https://github.com/nuxt/devtools/blob/c4f2b68281203fc3f61ffc97d9c6623fbfde46bb/packages/devtools/src/server-rpc/assets.ts#L88C48-L88C48), 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)](https://github.com/nuxt/devtools/blob/c4f2b68281203fc3f61ffc97d9c6623fbfde46bb/packages/devtools/src/server-rpc/index.ts#L109) leading to [CSWSH](https://portswigger.net/web-security/websockets/cross-site-websocket-hijacking). 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)](https://github.com/nuxt/devtools/blob/c4f2b68281203fc3f61ffc97d9c6623fbfde46bb/packages/devtools/src/dev-auth.ts#L14). 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](https://github.com/nuxt/devtools/blob/c4f2b68281203fc3f61ffc97d9c6623fbfde46bb/packages/devtools/src/server-rpc/assets.ts#L96C11-L96C28) 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

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
npm/@nuxt/devtools<1.3.9
1.3.9
nCipher<1.3.9

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-23657?

    CVE-2024-23657 has a critical severity rating due to its potential for unauthorized access and data exfiltration.

  • How do I fix CVE-2024-23657?

    To fix CVE-2024-23657, update the @nuxt/devtools package to version 1.3.9 or later.

  • What systems are affected by CVE-2024-23657?

    CVE-2024-23657 affects instances of the @nuxt/devtools package and any Nuxt applications utilizing the affected versions.

  • What type of vulnerability is CVE-2024-23657?

    CVE-2024-23657 is a path traversal vulnerability combined with improper authentication and Origin checks.

  • Can CVE-2024-23657 be exploited remotely?

    Yes, CVE-2024-23657 can be exploited remotely if an attacker gains access to a locally running devtools instance.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203