React up to 16.4.1 ReactDOMServer API Application cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in React up to 16.0.0/16.1.1/16.2.0/16.3.2/16.4.1. Affected by this issue is some unknown functionality of the component ReactDOMServer API. Executing a manipulation as part of Application can lead to cross site scripting. This vulnerability is tracked as CVE-2018-6341. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in React up to 16.0.0/16.1.1/16.2.0/16.3.2/16.4.1 (JavaScript Library). This vulnerability affects an unknown code block of the component ReactDOMServer API. The manipulation as part of a Application leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. CVE summarizes:
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.
The bug was discovered 08/01/2018. The weakness was disclosed 12/31/2018 (Website). The advisory is available at reactjs.org. This vulnerability was named CVE-2018-6341 since 01/26/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 152 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 16.0.1, 16.1.2, 16.2.1, 16.3.3 or 16.4.2 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: React 16.0.1/16.1.2/16.2.1/16.3.3/16.4.2
Timeline
01/26/2018 🔍08/01/2018 🔍
12/31/2018 🔍
12/31/2018 🔍
01/01/2019 🔍
05/06/2025 🔍
Sources
Advisory: reactjs.orgStatus: Confirmed
CVE: CVE-2018-6341 (🔍)
GCVE (CVE): GCVE-0-2018-6341
GCVE (VulDB): GCVE-100-128602
Entry
Created: 01/01/2019 12:18Updated: 05/06/2025 22:34
Changes: 01/01/2019 12:18 (59), 04/25/2020 16:30 (1), 05/06/2025 22:34 (19)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.