GHSA-9JJV-524M-JM98
Vulnerability from github – Published: 2022-09-21 21:42 – Updated: 2022-09-28 03:32Impact
By 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.
Patches
This problem has been fixed in version 1.2.3
Workarounds
The 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.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@netlify/ipx"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-39239"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2022-09-21T21:42:01Z",
"nvd_published_at": "2022-09-23T08:15:00Z",
"severity": "MODERATE"
},
"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 `\u003cimg\u003e` 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",
"id": "GHSA-9jjv-524m-jm98",
"modified": "2022-09-28T03:32:53Z",
"published": "2022-09-21T21:42:01Z",
"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"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "@netlify/ipx vulnerable to Full Response SSRF and Stored XSS via Cache Poisoning and Improper Host Validation"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.