CVE-2023-49799 json
Server-Side Request Forgery in nuxt-api-party
published 2023-12-08 2 y ago modified 2026-09-10 1 mo ago also GHSA-3wfp-253j-5jxv , EUVD-2023-3089
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
`nuxt-api-party` is an open source module to proxy API requests. nuxt-api-party attempts to check if the user has passed an absolute URL to prevent the aforementioned attack. This has been recently changed to use the regular expression `^https?://`, however this regular expression can be bypassed by an absolute URL with leading whitespace. For example `\nhttps://whatever.com` which has a leading newline. According to the fetch specification, before a fetch is made the URL is normalized. "To normalize a byte sequence potentialValue, remove any leading and trailing HTTP whitespace bytes from potentialValue.". This means the final request will be normalized to `https://whatever.com` bypassing the check and nuxt-api-party will send a request outside of the whitelist. This could allow us to leak credentials or perform Server-Side Request Forgery (SSRF). This vulnerability has been addressed in version 0.22.1. Users are advised to upgrade. Users unable to upgrade should revert to the previous method of detecting absolute URLs.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/johannschopplich/nuxt-api-party/security/advisories/GHSA-3wfp-253j-5jxv referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | nuxt-api-party | <0.22.0 |
0.22.0 |
Affected products
- johannschopplich nuxt-api-party
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/johannschopplich/nuxt-api-party/commit/72762a200fc19d997a0f84bce578c28698dc5270
web
-
github.com
/johannschopplich/nuxt-api-party/security/advisories/GHSA-3wfp-253j-5jxv
web, exploit, mitigation, vendor-advisory
-
fetch.spec.whatwg.org
/
not-applicable
-
fetch.spec.whatwg.org
/#http-whitespace-byte
web, not-applicable
-
github.com
/johannschopplich/nuxt-api-party/blob/777462e1e3af1d9f8938aa33f230cd8cb6e0cc9a/src/runtime/server/handler.ts#L
web, issue-tracking
-
infra.spec.whatwg.org
/#byte-sequence
web, not-applicable
-
nvd.nist.gov
/vuln/detail/CVE-2023-49799
advisory
-
fetch.spec.whatwg.org
web
-
github.com
/johannschopplich/nuxt-api-party
package
Sources
- CVE List CVE-2023-49799
- GitHub Advisory GHSA-3wfp-253j-5jxv
- NVD CVE-2023-49799
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.