CVE-2024-42352 is a high-severity (CVSS 8.6) Server-Side Request Forgery (SSRF) vulnerability in @nuxt/icon. A fix is available for @nuxt/icon — see the affected versions and patch details below.
Server-Side Request Forgery (SSRF) in nuxt-icon
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-42352.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@nuxt/iconnpmDescription
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
fallbackToApioption.
Fix
- Ensure the host has not been changed after the path is parsed.
- Alternatively, prefix the path with
./.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @nuxt/icon | all versions | 1.4.5npm install @nuxt/icon@1.4.5 |
Affected Products
nuxtnuxtDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nuxt/icon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @nuxt/icon to 1.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-42352 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2024-42352 in your dependencies?
Find it across npm, including transitive dependencies.