CVE-2024-42352: Server-Side Request Forgery (SSRF) in nuxt-icon
First published: Mon Aug 05 2024(Updated: )
### 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 `./`.
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| npm/@nuxt/icon | <=1.4.4 | 1.4.5 |
| nCipher | <1.4.5 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-42352?
CVE-2024-42352 has been classified with a severity rating that indicates a serious risk due to the SSRF vulnerability.
How do I fix CVE-2024-42352?
To fix CVE-2024-42352, you should upgrade to @nuxt/icon version 1.4.5 or later.
What causes CVE-2024-42352?
CVE-2024-42352 is caused by improper parsing of the proxied request path in the nuxt/icon API.
What damages could result from CVE-2024-42352?
Exploitation of CVE-2024-42352 could allow attackers to conduct Server Side Request Forgery (SSRF) attacks.
Which software versions are affected by CVE-2024-42352?
CVE-2024-42352 affects @nuxt/icon versions up to 1.4.4 and all versions of Nuxt prior to 1.4.5.
- agent/weakness
- agent/first-publish-date
- agent/title
- agent/type
- agent/description
- agent/event
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-cxgv-px37-4mp2
- alias/CVE-2024-42352
- agent/software-canonical-lookup
- agent/references
- agent/author
- collector/mitre-cve
- source/MITRE
- collector/nvd-cve
- source/NVD
- collector/github-advisory
- agent/last-modified-date
- agent/severity
- agent/trending
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- agent/software-canonical-lookup-request
- package-manager/npm
- vendor/nuxt
- canonical/ncipher