dbcve.org
NuxtApplication

CVE-2024-42352

HIGH · 7.5 CVSS v3.1 Published 2024-08-05
Fix available
A fix is available. Upgrade to 1.4.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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. `nuxt/icon` provides an API to allow client side icon lookup. This endpoint is at `/api/_nuxt_icon/[name]`. The proxied request path is improperly parsed, allowing an attacker to change the scheme and host of the request. This leads to SSRF, and could potentially lead to sensitive data exposure. The `new URL` constructor is used to parse the final path. This constructor can be passed a relative scheme or path in order to change the host the request is sent to. This constructor is also very tolerant of poorly formatted URLs. As a result we can pass a path prefixed with the string `http:`. This has the effect of changing the scheme to HTTP. We can then subsequently pass a new host, for example `http:127.0.0.1:8080`. This would allow us to send requests to a local server. This issue has been addressed in release version 1.4.5 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

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

The nuxt/icon module's endpoint at /api/_nuxt_icon/[name] improperly parses proxied request paths using the new URL constructor, which accepts relative schemes and paths. Attackers can exploit this by passing malicious URL strings like 'http:127.0.0.1:8080' to trigger Server-Side Request Forgery (SSRF), enabling access to internal services and potential sensitive data exposure.

MitigationUpgrade nuxt/icon to version 1.4.5 or later. No workarounds exist for this vulnerability.

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:< 1.4.5

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Locate nuxt/icon module in project dependencies
    Search for nuxt-icon in package.json, package-lock.json, or yarn.lock. Run 'npm list nuxt-icon' or 'cat package.json | grep nuxt-icon' to identify if the module is installed.
    Affected if nuxt-icon is listed as a dependency in the project configuration files.
  2. Determine installed nuxt-icon version
    Run 'npm list nuxt-icon' or 'cat node_modules/nuxt-icon/package.json | grep version' to find the exact version number installed.
    Affected if The installed version is lower than 1.4.5 (e.g., 1.4.4, 1.4.0, or any version < 1.4.5).
  3. Verify /api/_nuxt_icon endpoint exists
    Make a GET request to /api/_nuxt_icon/test or /api/_nuxt_icon/[anyname] on the application's base URL. Inspect the response to confirm the endpoint is routing requests.
    Affected if The endpoint responds with icon data or any Nuxt-related response, indicating the module is active.
  4. Confirm icon module is enabled in Nuxt config
    Examine nuxt.config.ts or nuxt.config.js for 'nuxt-icon' or '@nuxt/icon' in the modules array. Run 'grep -r "nuxt.icon\|nuxt-icon" nuxt.config.*' if available.
    Affected if The module is listed in the Nuxt configuration under the modules section.

If nuxt-icon is installed, the version is below 1.4.5, and the /api/_nuxt_icon endpoint is accessible, the environment is vulnerable to CVE-2024-42352 SSRF attacks.

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 1.4.5 or later
Fixed in 1.4.5
Interim mitigation

Upgrade nuxt/icon to version 1.4.5 or later. No workarounds exist for this vulnerability.

Recommended fix High confidence

nuxt/icon version 1.4.5

  1. Upgrade the nuxt/icon module to version 1.4.5 or later by running: npm install nuxt-icon@^1.4.5 or npm install @nuxt/icon@^1.4.5
  2. Alternatively, upgrade the entire Nuxt framework to a version that includes the patched nuxt/icon module (v1.4.5 or newer)
  3. After upgrading, verify the fix by ensuring the /api/_nuxt_icon/[name] endpoint no longer accepts arbitrary URL schemes in the path parameter

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

Fix this in Nuxt Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-42352 — 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-42352 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