Samsung Mobile Devices O(8.x)/P(9.0)/Q(10.0) Sticker Center pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Samsung Mobile Devices O(8.x)/P(9.0)/Q(10.0). It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the component Sticker Center. This manipulation causes pathname traversal. The identification of this vulnerability is CVE-2020-26603. There is no exploit available.
Details
A vulnerability was found in Samsung Mobile Devices O(8.x)/P(9.0)/Q(10.0) (Smartphone Operating System). It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component Sticker Center. The manipulation with an unknown input leads to a pathname traversal vulnerability. The CWE definition for the vulnerability is CWE-21. As an impact it is known to affect confidentiality.
The weakness was shared 10/07/2020. The advisory is shared at security.samsungmobile.com. This vulnerability is known as CVE-2020-26603. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
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: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: Pathname traversalCWE: CWE-21 / CWE-22
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
10/06/2020 🔍10/07/2020 🔍
10/07/2020 🔍
11/17/2020 🔍
Sources
Vendor: samsung.comAdvisory: security.samsungmobile.com
Status: Not defined
CVE: CVE-2020-26603 (🔍)
GCVE (CVE): GCVE-0-2020-26603
GCVE (VulDB): GCVE-100-162349
Entry
Created: 10/07/2020 11:35Updated: 11/17/2020 03:30
Changes: 10/07/2020 11:35 (37), 11/15/2020 10:23 (4), 11/17/2020 03:25 (2), 11/17/2020 03:30 (14)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.