@nuxt/icon
Affected
- introduced
0, fixed1.4.5(semver)
Fixed versions
1.4.5
Fix
- Fixed version
1.4.5npm install @nuxt/[email protected]
Advisory
Also known as: CVE-2024-42352
Nuxt Icon affected by a Server-Side Request Forgery (SSRF)
Summarynuxt/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
fallbackToApi option.Fix
./.High Basis: The source's own band: HIGH
0, fixed 1.4.5 (semver)1.4.5
1.4.5npm install @nuxt/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0