This is not the latest report. Click
here to view the latest report.
CWE Statistics for Samsung Mobile as of 12/13/2022
545
40
40
16
Reference
0-69.9%
|
Reference |
40.0
Contributor
70-94.9%
Provider
95-100%
CVE | CNA Value | Alignment | NIST Value | Reason |
---|---|---|---|---|
CVE-2022-39847 (1 of 1) | CWE-416 | CWE-416 | ||
CVE-2022-39848 (1 of 1) | CWE-213 | CWE-200 | ||
CVE-2022-39852 (1 of 1) | CWE-122 | CWE-787 | ||
CVE-2022-39860 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39861 (1 of 1) | CWE-862 | CWE-862 | ||
CVE-2022-39862 (0 of 1) | CWE-285 | ≠ | CWE-863 | More specific CWE option available |
CVE-2022-39864 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39865 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39866 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39867 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39868 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39869 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39870 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39871 (0 of 1) | CWE-284 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39872 (1 of 1) | CWE-280 | CWE-755 | ||
CVE-2022-39873 (0 of 1) | CWE-285 | ≠ | CWE-863 | More specific CWE option available |
CVE-2022-39874 (0 of 1) | CWE-779 | ≠ | CWE-532 | More specific CWE option available |
CVE-2022-39876 (1 of 1) | CWE-532 | CWE-532 | ||
CVE-2022-39877 (0 of 1) | CWE-284 | ≠ | CWE-269 | More specific CWE option available |
CVE-2022-39879 (0 of 1) | CWE-285 | ≠ | CWE-862 | More specific CWE option available |
CVE-2022-39880 (1 of 1) | CWE-20 | CWE-20 | ||
CVE-2022-39881 (0 of 1) | CWE-20 | ≠ | CWE-125 | More specific CWE option available |
CVE-2022-39882 (1 of 1) | CWE-787 | CWE-787 | ||
CVE-2022-39883 (0 of 1) | CWE-285 | ≠ | CWE-732 | More specific CWE option available |
CVE-2022-39886 (0 of 1) | CWE-280 | ≠ | CWE-668 | More specific CWE option available |
CVE-2022-39887 (0 of 1) | CWE-284 | ≠ | CWE-732 | More specific CWE option available |
CVE-2022-39891 (0 of 1) | CWE-125 | ≠ | CWE-787 | More specific CWE option available |
CVE-2022-39893 (1 of 1) | CWE-532 | CWE-532 | ||
CVE-2022-39897 (0 of 1) | CWE-200 | ≠ | CWE-532 | More specific CWE option available |
CVE-2022-39899 (1 of 1) | CWE-287 | CWE-287 | ||
CVE-2022-39901 (1 of 1) | CWE-287 | CWE-287 | ||
CVE-2022-39902 (0 of 1) | CWE-285 | ≠ | CWE-863 | More specific CWE option available |
CVE-2022-39903 (0 of 1) | CWE-200 | ≠ | CWE-863 | More specific CWE option available |
CVE-2022-39904 (1 of 1) | CWE-200 | CWE-200 | ||
CVE-2022-39907 (1 of 1) | CWE-190 | CWE-190 | ||
CVE-2022-39908 (1 of 1) | CWE-367 | CWE-367 | ||
CVE-2022-39909 (1 of 1) | CWE-345 | CWE-345 | ||
CVE-2022-39912 (1 of 1) | CWE-280 | CWE-755 | ||
CVE-2022-39913 (0 of 1) | CWE-200 | ≠ | CWE-863 | More specific CWE option available |
CVE-2022-39914 (0 of 1) | CWE-200 | ≠ | CWE-863 | More specific CWE option available |