CVE-2018-6341GHSA-MVJJ-GQQ2-P4HW
React applications which rendered to HTML using the ReactDOMServer API were not escaping user-supplied attribute names at render-time.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 16.0.1, 16.1.2, 16.2.1, 16.3.3, 16.4.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
React 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Facebook react-dom
From 16.4.0; From 16.3.0; From 16.2.0; From 16.1.0; From 16.0.0
- react-domnpm
From 16.0.0 · fixed in 16.0.1
- react-domnpm
From 16.1.0 · fixed in 16.1.2
- react-domnpm
From 16.2.0 · fixed in 16.2.1
- react-domnpm
From 16.3.0 · fixed in 16.3.3
- react-domnpm
From 16.4.0 · fixed in 16.4.2