dbcve.org
NuxtApplication

CVE-2024-34344

HIGH · 8.8 CVSS v3.1 Published 2024-08-05
Fix available
A fix is available. Upgrade to 3.12.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Nuxt is a free and open-source framework to create full-stack web applications and websites with Vue.js. Due to the insufficient validation of the `path` parameter in the NuxtTestComponentWrapper, an attacker can execute arbitrary JavaScript on the server side, which allows them to execute arbitrary commands. Users who open a malicious web page in the browser while running the test locally are affected by this vulnerability, which results in the remote code execution from the malicious web page. Since web pages can send requests to arbitrary addresses, a malicious web page can repeatedly try to exploit this vulnerability, which then triggers the exploit when the test server starts.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Nuxt's NuxtTestComponentWrapper insufficiently validates the `path` parameter, allowing arbitrary JavaScript execution on the server side which escalates to arbitrary command execution. An attacker exploits this by having a user open a malicious web page while running local tests, which can repeatedly attempt exploitation when the test server starts.

MitigationUpdate Nuxt to the patched version that implements proper path parameter validation in the NuxtTestComponentWrapper. Users running tests locally should avoid opening untrusted web pages during test execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NuxtApplication
Affected:>= 3.4.0, < 3.12.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your installed Nuxt version
    Run `npm list nuxt` or `cat package.json` to find the installed nuxt version, then compare it to the affected range: >= 3.4.0 and < 3.12.4
    Affected if The installed version falls within >= 3.4.0 and < 3.12.4
  2. Verify if NuxtTestComponentWrapper is in use
    Search your codebase for imports or usage of `NuxtTestComponentWrapper` - typically found in test files using `import { NuxtTestComponentWrapper } from 'nuxt'` or similar test utilities
    Affected if Your test suite imports or uses NuxtTestComponentWrapper for component testing
  3. Determine if test server is accessible
    Check your test configuration and running processes for any test server that listens on a network port (look for `--test-server` flag, test configuration files, or running processes with test server ports)
    Affected if A test server is running and reachable from other contexts, especially if exposed to localhost or network
  4. Inspect test execution context
    Review whether tests are run while browsing other websites - the vulnerability is triggered when a user runs local tests and visits a malicious webpage that sends requests to the test server
    Affected if Tests are executed in an environment where browser access to untrusted sites is possible during test runs

You are affected if you run Nuxt version 3.4.0 through 3.12.3, use NuxtTestComponentWrapper in your tests, and have a test server that could receive requests from malicious web pages visited during testing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.12.4 or later
Fixed in 3.12.4
Interim mitigation

Update Nuxt to the patched version that implements proper path parameter validation in the NuxtTestComponentWrapper. Users running tests locally should avoid opening untrusted web pages during test execution.

Recommended fix High confidence

Nuxt 3.12.4 or later

  1. 1. Update your Nuxt version in package.json to ^3.12.4 or later (e.g., "nuxt": "^3.12.4")
  2. 2. Run `npm install` or `yarn install` to install the updated Nuxt version
  3. 3. Review the Nuxt 3.12.4 release notes for any changes that may affect your application
  4. 4. Run your test suite to verify your application still works correctly after the upgrade
  5. 5. Rebuild and restart your development server and test environment
Caveat Review Nuxt 3.12.4 release notes for potential breaking changes; major.minor version upgrades may introduce breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nuxt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34344 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data