Samsung Devices Vulnerabilities

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.

Last Year

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 Fix105
Temporary Fix0
Workaround0
Unavailable1
Not Defined170

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

High1
Functional0
Proof-of-Concept0
Unproven1
Not Defined274

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
Physical43
Local76
Adjacent13
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
High11
Low66
None199

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
None268

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.

Last Year

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
≤311
≤417
≤525
≤651
≤758
≤833
≤976
≤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
≤311
≤418
≤527
≤651
≤756
≤837
≤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
≤317
≤423
≤530
≤680
≤713
≤8106
≤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
≤636
≤718
≤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
≤31
≤47
≤55
≤610
≤76
≤81
≤92
≤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

<1k90
<2k73
<5k113
<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

<1k253
<2k22
<5k1
<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.

Last Year

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
05/07/20246.26.0Samsung Mobile Devices Setupwizard improper authorization$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20866
05/07/20246.76.5Samsung Mobile Devices Bootloader improper authentication$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2024-20865
05/07/20246.76.5Samsung Mobile Devices HAL out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2024-20863
05/07/20246.46.2Samsung Mobile Devices SveService out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2024-20862
05/07/20246.46.2Samsung Mobile Devices SveService use after free$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20861
05/07/20243.63.6Samsung Mobile Devices TelephonyUI improper export of android application components$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2024-20860
05/07/20244.44.3Samsung Mobile Devices FactoryCamera authorization$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20859
05/07/20243.63.6Samsung Mobile Devices CocktailBarService startListening access control$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2024-20857
05/07/20242.42.3Samsung Mobile Devices Multitasking Framework access control$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20855
05/07/20244.44.3Samsung Mobile Devices DarManagerService access control$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20864
05/07/20243.63.6Samsung Mobile Devices Callback setCocktailHostCallbacks access control$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20858
05/07/20243.33.3Samsung Mobile Devices Secure Folder improper authentication$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20856
05/07/20244.34.2Samsung Mobile Devices OTP missing immutable root of trust in hardware$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20821
04/02/20246.36.2Samsung Mobile Devices Libsdffextractor out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.09CVE-2024-20849
04/02/20244.74.6Samsung Mobile Devices Libsdffextractor out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20848
04/02/20243.63.6Samsung Mobile Devices StorageManagerService improper authorization$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20847
04/02/20245.65.5Samsung Mobile Devices HCR Decoding libsavsac.so out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20846
04/02/20248.17.9Samsung Mobile Devices libsavsac.so out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2024-20845
04/02/20248.17.9Samsung Mobile Devices Codewords Parser libsavsac.so out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2024-20844
04/02/20244.94.8Samsung Mobile Devices libIfaaCa out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20843
04/02/20244.24.1Samsung Mobile Devices Apdu out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20842
03/05/20244.03.9Samsung Devices pub_crypto_recv_msg race condition$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20833
03/05/20245.65.5Samsung Devices libsec-ril IpcTxSndSetLoopbackCtrl out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2023-52432
03/05/20243.33.2Samsung Devices libsubextractor.so ssmis_get_frm out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2024-20836
03/05/20244.74.6Samsung Devices CustomFrequencyManagerService improper authorization$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2024-20835

251 more entries are not shown

more entries by Samsung

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!