Vulnerabilities in pkg:npm/@nuxt/icon

PACKAGE
Advisory Identifier: GHSA-cxgv-px37-4mp2
Share
Advisory Summary

CVE-2024-42352 is a HIGH (CVSS 8.6) nuxt icon affected by a vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting @nuxt/icon libraries in the npm ecosystem. The issue involves nuxt icon affected by a server-side request forgery (ssrf). Remediation is available by upgrading affected packages to version 1.4.5.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@nuxt/icon

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@nuxt/icon. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-cxgv-px37-4mp2 CVE-2024-42352 HIGH Nuxt Icon affected by a Server-Side Request Forgery (SSRF)

CVE-2024-42352 at a Glance

CVE Identifier CVE-2024-42352
GHSA Identifier GHSA-cxgv-px37-4mp2
Severity HIGH
CVSS v3.1 Base Score 8.6
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product @nuxt/icon
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2024-42352

To remediate this vulnerability, upgrade all affected @nuxt/icon dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@nuxt/icon fixed: 1.4.5 
npm install @nuxt/icon@1.4.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @nuxt/icon

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2024-42352, inspect your project dependencies using npm:

npm ls @nuxt/icon

Analyze the terminal output to locate any version of @nuxt/icon in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.4.5), your application is affected.

Note: The npm ls @nuxt/icon command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In @nuxt/icon, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `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. ### Details 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. ### PoC Make a request to `/api/_nuxt_icon/http:example.com`, observe the data returned has been fetched from a different resource than intended. I typically try to find an example within Nuxt infrastructure that is vulnerable to these types of bugs, but I could not identify any with this endpoint enabled. ### Impact + SSRF, potential sensitive data exposure. + I do not believe this can be chained into an XSS, but it may be possible. + Does not have a security impact on services deployed on Cloudflare Workers. + Does not impact certain builds and modes (like static builds). + Can be mitigated using by disabling the `fallbackToApi` option. ### Fix + Ensure the host has not been changed after the path is parsed. + Alternatively, prefix the path with `./`.

CVE-2024-42352 Affected @nuxt/icon Versions

1 component(s)
Fixed Versions:
1.4.5
Product / Package Ecosystem Affected Versions Fixed Version
@nuxt/icon
npm/@nuxt/icon
npm
< 1.4.5
1.4.5

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nuxt/icon/security/advisories/GHSA-cxgv-px37-4mp2
NVD — CVE-2024-42352 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-42352
Security Fix Commit FIX COMMIT
https://github.com/nuxt/icon/commit/4564518c2b2ed8235a7715056ccdfce96ca3d0ff
@nuxt/icon Source Repository REPOSITORY
https://github.com/nuxt/icon

Frequently Asked Questions

What is CVE-2024-42352?
CVE-2024-42352 is a security vulnerability in @nuxt/icon involving Nuxt Icon affected by a Server-Side Request Forgery (SSRF) under CWE-918: Server-Side Request Forgery (SSRF).
Which @nuxt/icon versions are affected?
Affected versions include releases prior to 1.4.5 across affected packages: @nuxt/icon.
What version fixes CVE-2024-42352?
Upgrading to 1.4.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @nuxt/icon affected?
Yes, @nuxt/icon is affected in releases prior to 1.4.5. Upgrade your dependency to 1.4.5 or later.
What is the CVSS score of CVE-2024-42352?
CVE-2024-42352 has a CVSS v3.1 base score of 8.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2024-42352?
CVE-2024-42352 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for CVE-2024-42352?
Run the dependency tree command: 'npm ls @nuxt/icon'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cxgv-px37-4mp2",
  "modified" : "2024-08-06T14:41:54Z",
  "published" : "2024-08-05T19:49:55Z",
  "aliases" : [ "CVE-2024-42352" ],
  "summary" : "Nuxt Icon affected by a Server-Side Request Forgery (SSRF)",
  "details" : "### Summary\n`nuxt/icon` provides an API to allow client side icon lookup. This endpoint is at `/api/_nuxt_icon/[name]`.\n\nThe 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.\n\n### Details\nThe `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.\n\nAs 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. \n\n### PoC\nMake a request to `/api/_nuxt_icon/http:example.com`, observe the data returned has been fetched from a different resource than intended. \n\nI typically try to find an example within Nuxt infrastructure that is vulnerable to these types of bugs, but I could not identify any with this endpoint enabled.\n\n### Impact\n+ SSRF, potential sensitive data exposure.\n+ I do not believe this can be chained into an XSS, but it may be possible.\n+ Does not have a security impact on services deployed on Cloudflare Workers.\n+ Does not impact certain builds and modes (like static builds).\n+ Can be mitigated using by disabling the `fallbackToApi` option.\n\n### Fix\n+ Ensure the host has not been changed after the path is parsed.\n+ Alternatively, prefix the path with `./`.\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nuxt/icon"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.4.5"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.4.4"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nuxt/icon/security/advisories/GHSA-cxgv-px37-4mp2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-42352"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nuxt/icon/commit/4564518c2b2ed8235a7715056ccdfce96ca3d0ff"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nuxt/icon"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-08-05T19:49:55Z",
    "nvd_published_at" : "2024-08-05T21:15:38Z"
  }
}