CVE-2022-39239 json
nefly-ipx subject to Server-Side Request Forgery and Stored Cross-Site Scripting via Cache Poisoning and Improper Host Validation
published 4y ago modified 4mo ago also GHSA-9jjv-524m-jm98 , EUVD-2022-6760
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
netlify-ipx is an on-Demand image optimization for Netlify using ipx. In versions prior to 1.2.3, an attacker can bypass the source image domain allowlist by sending specially crafted headers, 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. This problem has been fixed in version 1.2.3. As a workaround, cached content can be cleared by re-deploying the site.
Patch / fix
- npm @netlify/ipx 1.2.3
- nuxtjs netlify-ipx 1.2.3
Is CVE-2022-39239 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @netlify/ipx | <1.2.3 |
1.2.3 |
Affected products
- netlify netlify-ipx
Classification
References
-
github.com
/netlify/netlify-ipx/pull/61
web
-
github.com
/netlify/netlify-ipx/commit/dfa7505a8d47a76fd527570dc40737a61500759b
web
-
github.com
/netlify/netlify-ipx/security/advisories/GHSA-9jjv-524m-jm98
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-39239
advisory
-
github.com
/netlify/netlify-ipx
package
-
github.com
/netlify/netlify-ipx/releases/tag/v1.2.3
web
Sources
- CVE List CVE-2022-39239
- GitHub Advisory GHSA-9jjv-524m-jm98
- NVD CVE-2022-39239
Fencer Intel 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.