Cross-Site Scripting in react-dom
Facebook react-dom
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| react-dom npm |
|
|
Facebook react-dom
| Product | Affected | Fixed in |
|---|---|---|
| react-dom npm |
|
|
16.3.316.4.2React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attribute names at render-time. That lack of escaping could lead to a cross-site scripting vulnerability. This issue affected minor releases 16.0.x, 16.1.x, 16.2.x, 16.3.x, and 16.4.x. It was fixed in 16.0.1, 16.1.2, 16.2.1, 16.3.3, and 16.4.2.
From the CVE record · facebook
ReactDOMServer did not escape user-supplied attribute names when rendering HTML. An attacker who can supply an attribute name to an affected application could cause cross-site scripting; the input does not specify authentication or user-interaction requirements.
Engineers running npm react-dom versions >=16.0.0 <16.0.1, >=16.1.0 <16.1.2, >=16.2.0 <16.2.1, >=16.3.0 <16.3.3, or >=16.4.0 <16.4.2 should check their applications.