Vulnerabilities in pkg:npm/@netlify/ipx
PACKAGECVE-2022-39239 is a MODERATE (CVSS 6.1) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting @netlify/ipx libraries in the npm ecosystem. The issue involves @netlify/ipx vulnerable to full response ssrf and stored xss via cache poisoning and improper host validation. Remediation is available by upgrading affected packages to version 1.2.3.
pkg:npm/@netlify/ipx
Vulnerability advisories affecting package pkg:npm/@netlify/ipx. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-9jjv-524m-jm98 | CVE-2022-39239 | MODERATE | @netlify/ipx vulnerable to Full Response SSRF and Stored XSS via Cache Poisoning and Improper Host Validation |
CVE-2022-39239 at a Glance
Security Impact
CVSS: 6.1
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:R/S:C/C:L/I:L/A:N).
How to Fix CVE-2022-39239
To remediate this vulnerability, upgrade all affected @netlify/ipx 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 @netlify/ipx@1.2.3
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @netlify/ipx
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2022-39239, inspect your project dependencies using npm:
npm ls @netlify/ipx
Analyze the terminal output to locate any version of @netlify/ipx in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.3), your application is affected.
Note: The npm ls @netlify/ipx 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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In @netlify/ipx, 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-2022-39239 Affected @netlify/ipx Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@netlify/ipx
|
npm |
< 1.2.3
|
1.2.3
|
References
Frequently Asked Questions
What is CVE-2022-39239?
Which @netlify/ipx versions are affected?
What version fixes CVE-2022-39239?
Is @netlify/ipx affected?
What is the CVSS score of CVE-2022-39239?
What CWE is associated with CVE-2022-39239?
How can I check npm dependencies for CVE-2022-39239?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9jjv-524m-jm98",
"modified" : "2022-09-28T03:32:53Z",
"published" : "2022-09-21T21:42:01Z",
"aliases" : [ "CVE-2022-39239" ],
"summary" : "@netlify/ipx vulnerable to Full Response SSRF and Stored XSS via Cache Poisoning and Improper Host Validation",
"details" : "### Impact\n\nBy sending specially crafted headers an attacker can bypass the source image domain allowlist, causing the handler to load and return arbitrary images. Because the response is cached globally, this image will then be served to visitors without requiring those headers to be set. XSS can be achieved by requesting a malicious SVG with embedded scripts, which would then be served from the site domain. Note that this does not apply to images loaded in `<img>` tags, as scripts do not execute in this context. The image URL can be set in the header independently of the request URL, meaning any site images that have not previously been cached can have their cache poisoned.\n\n### Patches\nThis problem has been fixed in version 1.2.3\n\n### Workarounds\n\nThe problem is no longer exploitable on Netlify as the CDN now sanitizes the relevant header. Cached content can be cleared by re-deploying the site.\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@netlify/ipx"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.2.3"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/netlify/netlify-ipx/security/advisories/GHSA-9jjv-524m-jm98"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-39239"
}, {
"type" : "WEB",
"url" : "https://github.com/netlify/netlify-ipx/pull/61"
}, {
"type" : "WEB",
"url" : "https://github.com/netlify/netlify-ipx/commit/dfa7505a8d47a76fd527570dc40737a61500759b"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/netlify/netlify-ipx"
}, {
"type" : "WEB",
"url" : "https://github.com/netlify/netlify-ipx/releases/tag/v1.2.3"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-79" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2022-09-21T21:42:01Z",
"nvd_published_at" : "2022-09-23T08:15:00Z"
}
}