SyncBreeze Sync Breeze Enterprise 12.4.18 unquoted search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SyncBreeze Sync Breeze Enterprise 12.4.18 and classified as problematic. Affected by this issue is some unknown functionality. Executing a manipulation can lead to unquoted search path. This vulnerability is handled as CVE-2020-37100. It is possible to launch the attack on the local host. Additionally, an exploit exists.
Details
A vulnerability classified as critical was found in SyncBreeze Sync Breeze Enterprise 12.4.18. This vulnerability affects an unknown code. The manipulation with an unknown input leads to a unquoted search path vulnerability. The CWE definition for the vulnerability is CWE-428. The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Sync Breeze Enterprise 12.4.18 contains an unquoted service path vulnerability that allows local attackers to execute arbitrary code with elevated system privileges. Attackers can exploit the unquoted binary path by placing malicious executables in specific file system locations to hijack the service startup process.
The weakness was released by boku as 48045. The advisory is available at exploit-db.com. This vulnerability was named CVE-2020-37100 since 02/01/2026. The exploitation appears to be difficult. Local access is required to approach this attack. Technical details are unknown but a public exploit is available. This vulnerability is assigned to T1574.009 by the MITRE ATT&CK project.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (48045). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.0
VulDB Temp Score: 6.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (VulnCheck): 🔒
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: Unquoted search pathCWE: CWE-428 / CWE-426
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/01/2026 CVE reserved02/03/2026 Advisory disclosed
02/03/2026 VulDB entry created
02/03/2026 VulDB entry last update
Sources
Advisory: 48045Researcher: boku
Status: Not defined
CVE: CVE-2020-37100 (🔒)
GCVE (CVE): GCVE-0-2020-37100
GCVE (VulDB): GCVE-100-344026
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/03/2026 16:30Changes: 02/03/2026 16:30 (79)
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.