Samsung SyncThru Web Service SPL 5.93 06-09-2014 channel accessible
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Samsung SyncThru Web Service SPL 5.93 06-09-2014. This affects an unknown part. This manipulation causes channel accessible. This vulnerability is registered as CVE-2021-35309. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as problematic was found in Samsung SyncThru Web Service SPL 5.93 06-09-2014. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a channel accessible vulnerability. The CWE definition for the vulnerability is CWE-300. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. As an impact it is known to affect integrity. The summary by CVE is:
An issue discovered in Samsung SyncThru Web Service SPL 5.93 06-09-2014 allows attackers to gain escalated privileges via MITM attacks.
The weakness was published 08/23/2023. The advisory is shared at github.com. This vulnerability is known as CVE-2021-35309 since 06/23/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1557 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
Exploiting
Class: Channel accessibleCWE: CWE-300
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/23/2021 🔍08/23/2023 🔍
08/23/2023 🔍
10/03/2024 🔍
Sources
Vendor: samsung.comAdvisory: github.com
Status: Not defined
CVE: CVE-2021-35309 (🔍)
GCVE (CVE): GCVE-0-2021-35309
GCVE (VulDB): GCVE-100-237745
Entry
Created: 08/23/2023 08:20Updated: 10/03/2024 22:56
Changes: 08/23/2023 08:20 (36), 09/14/2023 17:50 (11), 10/03/2024 22:56 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.