React-Admin vulnerable to Cross-Site-Scripting attack on `<RichTextField>`
marmelab react-admin
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| react-admin npm |
|
|
| ra-ui-materialui npm |
|
marmelab react-admin
| Product | Affected | Fixed in |
|---|---|---|
| react-admin npm |
|
|
| ra-ui-materialui npm |
|
4.7.63.19.12react-admin is a frontend framework for building browser applications on top of REST/GraphQL APIs. react-admin prior to versions 3.19.12 and 4.7.6, along with ra-ui-materialui prior to 3.19.12 and 4.7.6, are vulnerable to cross-site scripting. All React applications built with react-admin and using the `<RichTextField>` are affected. `<RichTextField>` outputs the field value using `dangerouslySetInnerHTML` without client-side sanitization. If the data isn't sanitized server-side, this opens a possible cross-site scripting (XSS) attack. Versions 3.19.12 and 4.7.6 now use `DOMPurify` to escape the HTML before outputting it with React and `dangerouslySetInnerHTML`. Users who already sanitize HTML data server-side do not need to upgrade. As a workaround, users may replace the `<RichTextField>` by a custom field doing sanitization by hand.
From the CVE record · GitHub_M
The `<RichTextField>` component in affected react-admin applications renders HTML without client-side sanitization. If the data is not sanitized server-side, an attacker who can place malicious HTML in a field can trigger cross-site scripting when someone views it. The input does not specify whether authentication is required to place that data.
Engineers running applications that use `<RichTextField>` should check react-admin and ra-ui-materialui versions earlier than 3.19.12 or from 4.0.0 through 4.7.5.