Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0
Affected releases · next
- 12.x12.0.0 – 12.0.10Fixed in 12.1.0
- 11.x and older10.0.0 – 11.1.4No fix, no longer updated
On 12.x, the newest line:
npm install next@12.1.0Not affected
16.0.0 – 16.4.2
45 releases, latest
Affected
12.0.0 – 12.0.10
11 releases
Fixed
12.1.0 – 12.3.7
22 releases
Affected
11.0.0 – 11.1.4
7 releases
Affected
10.0.0 – 10.2.3
18 releases
Is your project affected?
Paste your package.json, or type the range you declare for next. It is read in your browser and sent nowhere.
What happens
Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the next.config.js file must have an images.domains array assigned and the image host assigned in images.domains must allow user-provided SVG. If the next.config.js file has images.loader assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change next.config.js to use a different loader configuration other than the default.
Impact
Affected: All of the following must be true to be affected
Next.js between version 10.0.0 and 12.0.10
The
next.config.jsfile has images.domains array assignedThe image host assigned in images.domains allows user-provided SVG
Not affected: The
next.config.jsfile has images.loader assigned to something other than default
Patches
Workarounds
Change next.config.js to use a different loader configuration other than the default, for example:
module.exports = {
images: {
loader: 'imgix',
path: 'https://example.com/myaccount/',
},
}Or if you want to use the loader prop on the component, you can use custom:
module.exports = {
images: {
loader: 'custom',
},
}