Product Samsung Mobile Devices

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

P(9.0)141
O(8.x)124
N(7.x)74
Q(10.0)69
M(6.0)14

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix73
Temporary Fix0
Workaround0
Unavailable0
Not Defined171

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept0
Unproven1
Not Defined243

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical38
Local50
Adjacent12
Network144

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High2
Low47
None195

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required8
None236

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤310
≤49
≤516
≤648
≤749
≤833
≤974
≤105

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤310
≤410
≤518
≤647
≤748
≤835
≤971
≤105

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤314
≤413
≤526
≤674
≤76
≤8104
≤91
≤106

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤312
≤48
≤58
≤634
≤717
≤870
≤910
≤1083

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k64
<2k68
<5k112
<10k0
<25k0
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k173
<2k32
<5k39
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (23): 7.0, 8.0, 9.0, 10.0, 11.0, 2017-11-03, 2020-04-02, Go(8.1), Go(9.0), L, L(5.0), L(5.1), M, M(6.0), N, N(7.0), N(7.1), O(8.0), O(8.1), O(8.X), P(9.0), Q(10.0), R(11.0)

Link to Product Website: https://www.samsung.com/

Software Type: Smartphone Operating System

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
03/05/20215.75.4Samsung Mobile Devices HArx memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-25339
03/05/20215.75.4Samsung Mobile Devices RKP access control$0-$5k$0-$5kNot DefinedOfficial Fix0.09CVE-2021-25338
03/05/20215.95.7Samsung Mobile Devices Clipboard Service access control$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-25337
03/05/20214.13.9Samsung Mobile Devices NotificationManagerService privileges management$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-25336
03/05/20212.42.3Samsung Mobile Devices Lockscreen access control$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-25335
03/05/20215.04.8Samsung Mobile Devices Application denial of service$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-25334
11/08/20206.66.4Samsung Mobile Devices NPU Driver memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2020-28343
11/08/20206.05.8Samsung Mobile Devices S Secure Application improper authentication$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2020-28342
11/08/20206.66.4Samsung Mobile Devices S3K250AF Secure Element CC EAL 5+ Chip buffer overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2020-28341
11/08/20207.67.3Samsung Mobile Devices Factory Reset Protection Privilege Escalation$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2020-28340
10/07/20207.67.6Samsung Mobile Devices TimaService privileges management$0-$5k$0-$5kNot DefinedNot Defined0.07CVE-2020-26607
10/07/20206.56.5Samsung Mobile Devices Secure Folder information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.06CVE-2020-26606
10/07/20205.55.5Samsung Mobile Devices Log information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2020-26605
10/07/20206.56.5Samsung Mobile Devices Pendingintent privileges management$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2020-26604
10/07/20204.44.4Samsung Mobile Devices Sticker Center pathname traversal$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2020-26603
10/07/20206.56.5Samsung Mobile Devices Pendingintent exposure of resource$0-$5k$0-$5kNot DefinedNot Defined0.06CVE-2020-26602
09/11/20205.55.5Samsung Mobile Devices Debugging Command privileges management$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2020-25280
09/11/20208.58.5Samsung Mobile Devices Exynos Chipset buffer overflow$0-$5k$0-$5kNot DefinedNot Defined0.09CVE-2020-25279
09/11/20208.58.5Samsung Mobile Devices Quram Image Codec Library out-of-bounds write$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2020-25278
08/31/20208.58.5Samsung Mobile Devices Persona Service authorization$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2020-25055
08/31/20208.28.2Samsung Mobile Devices Exynos Modem Chipset input validation$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2020-25054
08/31/20208.58.5Samsung Mobile Devices RKP code injection$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2020-25053
08/31/20208.58.5Samsung Mobile Devices H-Arx input validation$0-$5k$0-$5kNot DefinedNot Defined0.06CVE-2020-25052
08/31/20207.47.4Samsung Mobile Devices Factory Reset Protection privileges management$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2020-25051
08/31/20206.46.4Samsung Mobile Devices CMC Service information disclosure$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2020-25050

219 more entries are not shown

more entries by Samsung

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!