This page was not yet optimized for use on mobile devices.
Microsoft windows 2.0
Configuration details
| CPE title | Microsoft windows 2.0 |
|---|---|
| URI | cpe:2.3:o:microsoft:windows:2.0:*:*:*:*:*:*:* |
Linked CVEs
279 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2007-2108 | MEDIUM | 6.8 | 18.04.2007 | |
| CVE-2007-3285 | MEDIUM | 6.8 | 20.06.2007 | |
| CVE-2007-3504 | HIGH | 9.3 | 30.06.2007 | |
| CVE-2007-3794 | HIGH | 10.0 | 15.07.2007 | |
| CVE-2007-5473 | MEDIUM | 5.0 | 18.10.2007 | |
| CVE-2007-6045 | HIGH | 10.0 | 20.11.2007 | |
| CVE-2007-6046 | HIGH | 7.2 | 20.11.2007 | |
| CVE-2007-6047 | HIGH | 10.0 | 20.11.2007 | |
| CVE-2007-6048 | HIGH | 10.0 | 20.11.2007 | |
| CVE-2007-6050 | HIGH | 7.2 | 20.11.2007 | |
| CVE-2007-6051 | HIGH | 10.0 | 20.11.2007 | |
| CVE-2007-6052 | HIGH | 7.8 | 20.11.2007 | |
| CVE-2007-6053 | HIGH | 9.3 | 20.11.2007 | |
| CVE-2007-6404 | MEDIUM | 5.0 | 17.12.2007 | |
| CVE-2007-6701 | HIGH | 10.0 | 13.02.2008 | |
| CVE-2008-0212 | HIGH | 7.8 | 06.02.2008 | |
| CVE-2008-0296 | HIGH | 10.0 | 16.01.2008 | |
| CVE-2008-0304 | HIGH | 7.5 | 29.02.2008 | |
| CVE-2008-0312 | HIGH | 9.3 | 08.04.2008 | |
| CVE-2008-0454 | HIGH | 9.3 | 25.01.2008 | |
| CVE-2008-0639 | HIGH | 10.0 | 13.02.2008 | |
| CVE-2008-0766 | HIGH | 10.0 | 13.02.2008 | |
| CVE-2008-1299 | MEDIUM | 4.3 | 12.03.2008 | |
| CVE-2008-1302 | MEDIUM | 5.0 | 12.03.2008 | |
| CVE-2008-1363 | HIGH | 7.2 | 20.03.2008 | |
| CVE-2008-1392 | HIGH | 10.0 | 20.03.2008 | |
| CVE-2008-1402 | HIGH | 7.1 | 20.03.2008 | |
| CVE-2008-1998 | HIGH | 8.5 | 28.04.2008 | |
| CVE-2008-2099 | MEDIUM | 6.9 | 02.06.2008 | |
| CVE-2008-2307 | HIGH | 9.3 | 23.06.2008 | |
| CVE-2008-2747 | LOW | 2.1 | 18.06.2008 | |
| CVE-2008-3079 | HIGH | 10.0 | 09.07.2008 | |
| CVE-2008-3851 | MEDIUM | 5.0 | 27.08.2008 | |
| CVE-2008-3897 | LOW | 2.1 | 03.09.2008 | |
| CVE-2008-4420 | HIGH | 9.3 | 13.04.2009 | |
| CVE-2008-4563 | HIGH | 10.0 | 11.03.2009 | |
| CVE-2008-4816 | MEDIUM | 4.3 | 05.11.2008 | |
| CVE-2008-4820 | HIGH | 7.1 | 10.11.2008 | |
| CVE-2008-5326 | MEDIUM | 4.4 | 05.12.2008 | |
| CVE-2008-5412 | HIGH | 10.0 | 10.12.2008 | |
| CVE-2008-6194 | HIGH | 7.8 | 19.02.2009 | |
| CVE-2009-0714 | HIGH | 7.2 | 14.05.2009 | |
| CVE-2009-1394 | HIGH | 9.3 | 26.06.2009 | |
| CVE-2009-1419 | MEDIUM | 4.0 | 08.06.2009 | |
| CVE-2009-3096 | HIGH | 10.0 | 08.09.2009 | |
| CVE-2009-3864 | HIGH | 7.5 | 05.11.2009 | |
| CVE-2009-3951 | HIGH | 7.1 | 10.12.2009 | |
| CVE-2010-2090 | MEDIUM | 5.0 | 27.05.2010 | |
| CVE-2010-2157 | LOW | 2.1 | 07.06.2010 | |
| CVE-2010-3139 | HIGH | 9.3 | 27.08.2010 | |
| CVE-2010-3143 | HIGH | 9.3 | 27.08.2010 | |
| CVE-2010-3888 | HIGH | 7.2 | 08.10.2010 | |
| CVE-2010-3889 | HIGH | 7.2 | 08.10.2010 | |
| CVE-2011-0638 | MEDIUM | 6.9 | 25.01.2011 | |
| CVE-2011-3185 | HIGH | 9.3 | 29.08.2011 | |
| CVE-2011-3516 | HIGH | 7.6 | 19.10.2011 | |
| CVE-2011-5049 | MEDIUM | 4.3 | 04.01.2012 | |
| CVE-2012-2971 | HIGH | 7.5 | 20.10.2012 | |
| CVE-2012-2972 | MEDIUM | 5.0 | 20.10.2012 | |
| CVE-2012-3974 | MEDIUM | 6.9 | 29.08.2012 | |
| CVE-2015-4642 | CRITICAL | 9.8 | 16.05.2016 | |
| CVE-2016-0603 | HIGH | 7.6 | 08.02.2016 | |
| CVE-2016-1037 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1038 | CRITICAL | 10.0 | 11.05.2016 | |
| CVE-2016-1039 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1040 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1041 | CRITICAL | 10.0 | 11.05.2016 | |
| CVE-2016-1042 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1043 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1044 | CRITICAL | 10.0 | 11.05.2016 | |
| CVE-2016-1045 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1046 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1047 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1048 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1049 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1050 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1051 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1052 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1053 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1054 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1055 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1056 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1057 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1058 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1059 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1060 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1061 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1062 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1063 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1064 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1065 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1066 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1067 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1068 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1069 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1070 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1071 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1072 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1073 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1074 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1075 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1076 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1077 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1078 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1079 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1080 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1081 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1082 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1083 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1084 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1085 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1086 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1087 | HIGH | 7.8 | 11.05.2016 | |
| CVE-2016-1088 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1089 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-1090 | HIGH | 7.8 | 11.05.2016 | |
| CVE-2016-1091 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-1092 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1093 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1094 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1095 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1112 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1116 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1117 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1118 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1119 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1120 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1121 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1122 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1123 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1124 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1125 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1126 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1127 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1128 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1129 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1130 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-1156 | MEDIUM | 5.7 | 19.02.2016 | |
| CVE-2016-1976 | MEDIUM | 5.5 | 13.03.2016 | |
| CVE-2016-2077 | CRITICAL | 9.8 | 18.05.2016 | |
| CVE-2016-2078 | MEDIUM | 6.1 | 08.06.2016 | |
| CVE-2016-2556 | HIGH | 7.8 | 12.04.2016 | |
| CVE-2016-2558 | HIGH | 8.4 | 12.04.2016 | |
| CVE-2016-2809 | MEDIUM | 5.5 | 30.04.2016 | |
| CVE-2016-2824 | HIGH | 8.8 | 13.06.2016 | |
| CVE-2016-2826 | HIGH | 7.8 | 13.06.2016 | |
| CVE-2016-4088 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4089 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4090 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4091 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4092 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4093 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4094 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4096 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4097 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4098 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4099 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4100 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4101 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4102 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4103 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4104 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4105 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4106 | HIGH | 7.8 | 11.05.2016 | |
| CVE-2016-4107 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4118 | HIGH | 7.8 | 30.05.2016 | |
| CVE-2016-4119 | CRITICAL | 9.8 | 26.08.2016 | |
| CVE-2016-4158 | HIGH | 7.3 | 16.06.2016 | |
| CVE-2016-4171 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4191 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4192 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4193 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4194 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4195 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4196 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4197 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4198 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4199 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4200 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4201 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4202 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4203 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4204 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4205 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4206 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4207 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4208 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4209 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4210 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4211 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4212 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4213 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4214 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4215 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4250 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4251 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4252 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4254 | CRITICAL | 9.8 | 13.07.2016 | |
| CVE-2016-4255 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4265 | CRITICAL | 9.8 | 26.08.2016 | |
| CVE-2016-4266 | CRITICAL | 9.8 | 26.08.2016 | |
| CVE-2016-4267 | CRITICAL | 9.8 | 26.08.2016 | |
| CVE-2016-4268 | CRITICAL | 9.8 | 26.08.2016 | |
| CVE-2016-4269 | CRITICAL | 9.8 | 26.08.2016 | |
| CVE-2016-4270 | CRITICAL | 9.8 | 26.08.2016 | |
| CVE-2016-6937 | CRITICAL | 9.8 | 17.09.2016 | |
| CVE-2016-6938 | CRITICAL | 9.8 | 17.09.2016 | |
| CVE-2016-6939 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6940 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6941 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6942 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6943 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6944 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6945 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6946 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6947 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6948 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6949 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6950 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6951 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6952 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6953 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6954 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6955 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6956 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6957 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6958 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6959 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6960 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6961 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6962 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6963 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6964 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6965 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6966 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6967 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6968 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6969 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6970 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6971 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6972 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6973 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6974 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6975 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6976 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6977 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6978 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6979 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6988 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6993 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6994 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6995 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6996 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6997 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6998 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-6999 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7000 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7001 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7002 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7003 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7004 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7005 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7006 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7007 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7008 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7009 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7010 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7011 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7012 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7013 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7014 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7015 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7016 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7017 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7018 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7019 | CRITICAL | 9.8 | 13.10.2016 | |
| CVE-2016-7852 | CRITICAL | 9.8 | 21.10.2016 | |
| CVE-2016-7853 | CRITICAL | 9.8 | 21.10.2016 | |
| CVE-2016-7854 | CRITICAL | 9.8 | 21.10.2016 |
Showing 5 out of 279.
Matched certificates
This CPE has no matched certificates.