This page was not yet optimized for use on mobile devices.
Google Android 2020-06-01
Configuration details
| CPE title | Google Android 2020-06-01 |
|---|---|
| URI | cpe:2.3:o:google:android:2020-06-01:*:*:*:*:*:*:* |
Linked CVEs
196 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2008-7298 | MEDIUM | 5.8 | 09.08.2011 | |
| CVE-2011-0419 | MEDIUM | 4.3 | 16.05.2011 | |
| CVE-2012-4016 | MEDIUM | 4.3 | 28.09.2012 | |
| CVE-2012-4017 | MEDIUM | 4.3 | 28.09.2012 | |
| CVE-2014-9411 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9935 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2014-9936 | HIGH | 7.0 | 16.05.2017 | |
| CVE-2014-9937 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2014-9960 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2014-9961 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2014-9962 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2014-9963 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2014-9964 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2014-9965 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2014-9966 | HIGH | 7.0 | 13.06.2017 | |
| CVE-2014-9967 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2014-9968 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9969 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9971 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9972 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9973 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9974 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9975 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9976 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9977 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9978 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9979 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9980 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2014-9981 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-0574 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-0575 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-0576 | HIGH | 7.0 | 18.08.2017 | |
| CVE-2015-1529 | HIGH | 7.5 | 23.05.2017 | |
| CVE-2015-8592 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-8593 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-8594 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-8595 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-8596 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-8995 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2015-8996 | HIGH | 7.0 | 16.05.2017 | |
| CVE-2015-8997 | HIGH | 7.0 | 16.05.2017 | |
| CVE-2015-8998 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2015-8999 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2015-9000 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2015-9001 | MEDIUM | 5.5 | 16.05.2017 | |
| CVE-2015-9002 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2015-9003 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2015-9020 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9021 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2015-9022 | HIGH | 7.0 | 13.06.2017 | |
| CVE-2015-9023 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9024 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2015-9025 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9026 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9027 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9028 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9029 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9030 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9031 | LOW | 3.3 | 13.06.2017 | |
| CVE-2015-9032 | LOW | 3.3 | 13.06.2017 | |
| CVE-2015-9033 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2015-9034 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9035 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9036 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9037 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9038 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9039 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9040 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9041 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9042 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9043 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9044 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9045 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9046 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9047 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9048 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9049 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9050 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9051 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9052 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9053 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9054 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9055 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9060 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9061 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9062 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9063 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9064 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9065 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9066 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9067 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9068 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9069 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9070 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9071 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9072 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2015-9073 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10239 | HIGH | 7.8 | 16.05.2017 | |
| CVE-2016-10332 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2016-10333 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2016-10334 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2016-10335 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2016-10336 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2016-10337 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2016-10338 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2016-10339 | HIGH | 7.1 | 13.06.2017 | |
| CVE-2016-10340 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2016-10341 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2016-10342 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2016-10343 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10344 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10346 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10347 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10380 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10381 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10382 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10383 | HIGH | 8.1 | 18.08.2017 | |
| CVE-2016-10384 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10385 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10386 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10387 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10388 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10389 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2016-10390 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10391 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-10392 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-1940 | MEDIUM | 5.3 | 31.01.2016 | |
| CVE-2016-1948 | MEDIUM | 5.3 | 31.01.2016 | |
| CVE-2016-2813 | MEDIUM | 6.5 | 30.04.2016 | |
| CVE-2016-5347 | MEDIUM | 4.7 | 16.08.2017 | |
| CVE-2016-5853 | HIGH | 7.0 | 16.08.2017 | |
| CVE-2016-5854 | MEDIUM | 4.7 | 16.08.2017 | |
| CVE-2016-5855 | MEDIUM | 4.7 | 16.08.2017 | |
| CVE-2016-5858 | MEDIUM | 4.7 | 16.08.2017 | |
| CVE-2016-5859 | HIGH | 7.0 | 16.08.2017 | |
| CVE-2016-5860 | HIGH | 7.0 | 16.08.2017 | |
| CVE-2016-5861 | HIGH | 8.8 | 16.08.2017 | |
| CVE-2016-5862 | HIGH | 7.0 | 16.08.2017 | |
| CVE-2016-5863 | HIGH | 7.8 | 16.08.2017 | |
| CVE-2016-5864 | HIGH | 7.8 | 16.08.2017 | |
| CVE-2016-5867 | HIGH | 7.0 | 16.08.2017 | |
| CVE-2016-5871 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2016-5872 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2017-0843 | HIGH | 7.8 | 16.11.2017 | |
| CVE-2017-0862 | HIGH | 7.8 | 16.11.2017 | |
| CVE-2017-0863 | HIGH | 7.8 | 16.11.2017 | |
| CVE-2017-0864 | HIGH | 7.8 | 16.11.2017 | |
| CVE-2017-0865 | HIGH | 7.8 | 16.11.2017 | |
| CVE-2017-6421 | HIGH | 8.8 | 16.08.2017 | |
| CVE-2017-7364 | CRITICAL | 9.8 | 18.08.2017 | |
| CVE-2017-7365 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-7366 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2017-7367 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-7368 | HIGH | 7.0 | 13.06.2017 | |
| CVE-2017-7369 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-7370 | HIGH | 7.0 | 13.06.2017 | |
| CVE-2017-7371 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-7372 | HIGH | 7.0 | 13.06.2017 | |
| CVE-2017-7373 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-8233 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-8234 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-8235 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2017-8236 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-8237 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-8238 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-8239 | MEDIUM | 5.5 | 13.06.2017 | |
| CVE-2017-8240 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-8241 | HIGH | 7.8 | 13.06.2017 | |
| CVE-2017-8242 | MEDIUM | 5.9 | 13.06.2017 | |
| CVE-2017-8243 | HIGH | 7.8 | 16.08.2017 | |
| CVE-2017-8253 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-8254 | MEDIUM | 5.5 | 18.08.2017 | |
| CVE-2017-8255 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-8256 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-8257 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-8260 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-8261 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-8262 | HIGH | 7.0 | 18.08.2017 | |
| CVE-2017-8263 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-8265 | HIGH | 7.0 | 18.08.2017 | |
| CVE-2017-8266 | HIGH | 7.0 | 18.08.2017 | |
| CVE-2017-8267 | HIGH | 7.0 | 18.08.2017 | |
| CVE-2017-8268 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-8270 | HIGH | 7.0 | 18.08.2017 | |
| CVE-2017-8272 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-9678 | HIGH | 7.8 | 18.08.2017 | |
| CVE-2017-9679 | HIGH | 7.5 | 18.08.2017 | |
| CVE-2017-9680 | HIGH | 7.5 | 18.08.2017 | |
| CVE-2017-9682 | MEDIUM | 4.7 | 18.08.2017 | |
| CVE-2017-9684 | HIGH | 7.0 | 18.08.2017 | |
| CVE-2017-9685 | HIGH | 8.1 | 18.08.2017 | |
| CVE-2019-20606 | CRITICAL | 9.3 | 24.03.2020 | |
| CVE-2024-29748 | HIGH | 7.8 | 05.04.2024 | |
| CVE-2024-44100 | HIGH | 7.5 | 25.10.2024 | |
| CVE-2024-47020 | HIGH | 7.5 | 25.10.2024 | |
| CVE-2024-47022 | HIGH | 7.5 | 25.10.2024 |
Showing 5 out of 196.
Matched certificates
This CPE has no matched certificates.