High, CVSS 7.7npmAmendedPublished
Nuxt Icon affected by a Server-Side Request Forgery (SSRF)
CVE-2024-42352 · GHSA-cxgv-px37-4mp2
- Affected
- npm @nuxt/icon <= 1.4.4
- Fixed in
- 1.4.5· Vendor fix available
- Issue
- nuxt/icon provides an API to allow client side icon lookup. This endpoint is at /api/nuxticon/[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/nuxticon/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…
Recommended action: Upgrade to 1.4.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.