Synchrony up to 2.4.3 LiteralMap prototype pollution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Synchrony up to 2.4.3. It has been classified as problematic. Affected is the function LiteralMap. Performing a manipulation results in prototype pollution.
This vulnerability is known as CVE-2023-45811. Attacking locally is a requirement. No exploit is available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Synchrony up to 2.4.3. It has been classified as problematic. This affects the function LiteralMap. The manipulation with an unknown input leads to a prototype pollution vulnerability. CWE is classifying the issue as CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Synchrony deobfuscator is a javascript cleaner & deobfuscator. A `__proto__` pollution vulnerability exists in versions before v2.4.4. Successful exploitation could lead to arbitrary code execution. A `__proto__` pollution vulnerability exists in the `LiteralMap` transformer allowing crafted input to modify properties in the Object prototype. A fix has been released in `[email protected]`. Users are advised to upgrade. Users unable to upgrade should launch node with the [--disable-proto=delete][disable-proto] or [--disable-proto=throw][disable-proto] flags
The weakness was published 10/18/2023 as GHSA-jg82-xh3w-rhxx. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2023-45811 since 10/13/2023. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.
Upgrading to version 2.4.4 eliminates this vulnerability. Applying the patch b583126be94c4db7c5a478f1c5204bfb4162cf40 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 4.5
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 8.1
CNA Vector (GitHub, Inc.): 🔍
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: 🔍
Exploiting
Class: Prototype pollutionCWE: CWE-1321 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: Synchrony 2.4.4
Patch: b583126be94c4db7c5a478f1c5204bfb4162cf40
Timeline
10/13/2023 🔍10/18/2023 🔍
10/18/2023 🔍
07/22/2025 🔍
Sources
Advisory: GHSA-jg82-xh3w-rhxxStatus: Confirmed
CVE: CVE-2023-45811 (🔍)
GCVE (CVE): GCVE-0-2023-45811
GCVE (VulDB): GCVE-100-242835
Entry
Created: 10/18/2023 07:48Updated: 07/22/2025 18:36
Changes: 10/18/2023 07:48 (51), 11/10/2023 23:35 (11), 07/22/2025 18:36 (15)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.