Server-Side Request Forgery (SSRF) Affecting @nuxt/icon package, versions <1.4.5
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-NUXTICON-7641072
- published6 Aug 2024
- disclosed5 Aug 2024
- creditOhB00
Introduced: 5 Aug 2024
CVE-2024-42352 (opens in a new tab)How to fix?
Upgrade @nuxt/icon to version 1.4.5 or higher.
Overview
@nuxt/icon is a
Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) due to improper user input sanitization in the new URL constructor used in the /api/_nuxt_icon endpoint. By modifying the scheme and host within the URL, an attacker can manipulate the request URL to redirect requests to an unintended server.
Workaround
This vulnerability can be mitigated by disabling the fallbackToApi option or ensuring the host has not been changed after the path is parsed.
PoC
/api/_nuxt_icon/http:example.com