| CVE-2005-3660: Fix unknown |
| CVE-2007-3719: Fix unknown |
| CVE-2008-2544: Fix unknown |
| CVE-2008-4609: Fix unknown |
| CVE-2010-4563: Fix unknown |
| CVE-2010-5321: Fix unknown |
| CVE-2011-4916: Fix unknown |
| CVE-2011-4917: Fix unknown |
| CVE-2012-4542: Fix unknown |
| CVE-2013-4312: Fixed with 4.4.1 |
| CVE-2013-7445: Fix unknown |
| CVE-2015-1350: Fix not seen in stream |
| CVE-2015-2877: Fix unknown |
| CVE-2015-7566: Fixed with 4.4.2 |
| CVE-2015-8709: Fixed with 4.4.40 |
| CVE-2015-8812: Fixed with 4.4.4 |
| CVE-2015-8839: Fixed with 4.4.9 |
| CVE-2015-8952: Fix not seen in stream |
| CVE-2015-8963: Fixed with 4.4 |
| CVE-2015-8964: Fixed with 4.4.34 |
| CVE-2015-8970: Fixed with 4.4.2 |
| CVE-2016-0617: Fixed with 4.4.3 |
| CVE-2016-0723: Fixed with 4.4.2 |
| CVE-2016-0728: Fixed with 4.4.1 |
| CVE-2016-0758: Fixed with 4.4.21 |
| CVE-2016-10044: Fixed with 4.4.24 |
| CVE-2016-10088: Fixed with 4.4.41 |
| CVE-2016-10147: Fixed with 4.4.39 |
| CVE-2016-10200: Fixed with 4.4.38 |
| CVE-2016-10208: Fixed with 4.4.48 |
| CVE-2016-10229: Fixed with 4.4.21 |
| CVE-2016-10318: Fixed with 4.4.22 |
| CVE-2016-10723: Fix not seen in stream |
| CVE-2016-10741: Fixed with 4.4.80 |
| CVE-2016-10905: Fixed with 4.4.191 |
| CVE-2016-10906: Fixed with 4.4.191 |
| CVE-2016-1237: Fixed with 4.4.16 |
| CVE-2016-1575: Fixed with 4.4.3 |
| CVE-2016-1576: Fixed with 4.4.3 |
| CVE-2016-1583: Fixed with 4.4.14 |
| CVE-2016-2069: Fixed with 4.4.1 |
| CVE-2016-2070: Fixed with 4.4 |
| CVE-2016-2085: Fixed with 4.4.2 |
| CVE-2016-2117: Fixed with 4.4.11 |
| CVE-2016-2143: Fixed with 4.4.6 |
| CVE-2016-2184: Fixed with 4.4.7 |
| CVE-2016-2185: Fixed with 4.4.7 |
| CVE-2016-2186: Fixed with 4.4.7 |
| CVE-2016-2187: Fixed with 4.4.9 |
| CVE-2016-2188: Fixed with 4.4.55 |
| CVE-2016-2383: Fixed with 4.4.4 |
| CVE-2016-2384: Fixed with 4.4.2 |
| CVE-2016-2543: Fixed with 4.4.1 |
| CVE-2016-2544: Fixed with 4.4.1 |
| CVE-2016-2545: Fixed with 4.4.1 |
| CVE-2016-2546: Fixed with 4.4.1 |
| CVE-2016-2547: Fixed with 4.4.1 |
| CVE-2016-2548: Fixed with 4.4.1 |
| CVE-2016-2549: Fixed with 4.4.1 |
| CVE-2016-2782: Fixed with 4.4.2 |
| CVE-2016-2847: Fixed with 4.4.13 |
| CVE-2016-3044: Fixed with 4.4.6 |
| CVE-2016-3134: Fixed with 4.4.14 |
| CVE-2016-3135: Fixed with 4.4.21 |
| CVE-2016-3136: Fixed with 4.4.7 |
| CVE-2016-3137: Fixed with 4.4.7 |
| CVE-2016-3138: Fixed with 4.4.7 |
| CVE-2016-3140: Fixed with 4.4.7 |
| CVE-2016-3156: Fixed with 4.4.8 |
| CVE-2016-3157: Fixed with 4.4.7 |
| CVE-2016-3672: Fixed with 4.4.18 |
| CVE-2016-3689: Fixed with 4.4.7 |
| CVE-2016-3713: Fixed with 4.4.12 |
| CVE-2016-3857: Fixed with 4.4.18 |
| CVE-2016-3951: Fixed with 4.4.18 |
| CVE-2016-3955: Fixed with 4.4.9 |
| CVE-2016-3961: Fixed with 4.4.9 |
| CVE-2016-4470: Fixed with 4.4.16 |
| CVE-2016-4482: Fixed with 4.4.19 |
| CVE-2016-4485: Fixed with 4.4.11 |
| CVE-2016-4486: Fixed with 4.4.11 |
| CVE-2016-4557: Fixed with 4.4.11 |
| CVE-2016-4558: Fixed with 4.4.11 |
| CVE-2016-4565: Fixed with 4.4.9 |
| CVE-2016-4568: Fixed with 4.4.9 |
| CVE-2016-4569: Fixed with 4.4.17 |
| CVE-2016-4578: Fixed with 4.4.17 |
| CVE-2016-4580: Fixed with 4.4.11 |
| CVE-2016-4581: Fixed with 4.4.10 |
| CVE-2016-4794: Fixed with 4.4.16 |
| CVE-2016-4805: Fixed with 4.4.8 |
| CVE-2016-4913: Fixed with 4.4.11 |
| CVE-2016-4951: Fixed with 4.4.14 |
| CVE-2016-4997: Fixed with 4.4.14 |
| CVE-2016-4998: Fixed with 4.4.14 |
| CVE-2016-5195: Fixed with 4.4.26 |
| CVE-2016-5243: Fixed with 4.4.21 |
| CVE-2016-5244: Fixed with 4.4.21 |
| CVE-2016-5400: Fixed with 4.4.17 |
| CVE-2016-5412: Fixed with 4.4.19 |
| CVE-2016-5696: Fixed with 4.4.18 |
| CVE-2016-5728: Fix not seen in stream |
| CVE-2016-5828: Fixed with 4.4.16 |
| CVE-2016-5829: Fixed with 4.4.16 |
| CVE-2016-6130: Fixed with 4.4.21 |
| CVE-2016-6136: Fixed with 4.4.19 |
| CVE-2016-6156: Fixed with 4.4.17 |
| CVE-2016-6197: Fixed with 4.4.16 |
| CVE-2016-6198: Fixed with 4.4.11 |
| CVE-2016-6213: Fixed with 4.4.65 |
| CVE-2016-6327: Fixed with 4.4.7 |
| CVE-2016-6480: Fixed with 4.4.20 |
| CVE-2016-6828: Fixed with 4.4.23 |
| CVE-2016-7039: Fixed with 4.4.32 |
| CVE-2016-7042: Fixed with 4.4.31 |
| CVE-2016-7097: Fixed with 4.4.29 |
| CVE-2016-7117: Fixed with 4.4.8 |
| CVE-2016-7425: Fixed with 4.4.27 |
| CVE-2016-7910: Fixed with 4.4.18 |
| CVE-2016-7911: Fixed with 4.4.17 |
| CVE-2016-7912: Fixed with 4.4.9 |
| CVE-2016-7913: Fixed with 4.4.65 |
| CVE-2016-7914: Fixed with 4.4.9 |
| CVE-2016-7915: Fixed with 4.4.21 |
| CVE-2016-7916: Fixed with 4.4.10 |
| CVE-2016-7917: Fixed with 4.4.65 |
| CVE-2016-8399: Fixed with 4.4.38 |
| CVE-2016-8405: Fixed with 4.4.46 |
| CVE-2016-8630: Fixed with 4.4.31 |
| CVE-2016-8632: Fixed with 4.4.65 |
| CVE-2016-8633: Fixed with 4.4.31 |
| CVE-2016-8645: Fixed with 4.4.34 |
| CVE-2016-8650: Fixed with 4.4.36 |
| CVE-2016-8655: Fixed with 4.4.38 |
| CVE-2016-8658: Fixed with 4.4.29 |
| CVE-2016-8660: Fix unknown |
| CVE-2016-8666: Fixed with 4.4.29 |
| CVE-2016-9083: Fixed with 4.4.65 |
| CVE-2016-9084: Fixed with 4.4.65 |
| CVE-2016-9120: Fixed with 4.4.65 |
| CVE-2016-9178: Fixed with 4.4.22 |
| CVE-2016-9191: Fixed with 4.4.44 |
| CVE-2016-9555: Fixed with 4.4.32 |
| CVE-2016-9588: Fixed with 4.4.41 |
| CVE-2016-9604: Fixed with 4.4.64 |
| CVE-2016-9644: Fixed with 4.4.29 |
| CVE-2016-9685: Fixed with 4.4.7 |
| CVE-2016-9754: Fixed with 4.4.12 |
| CVE-2016-9756: Fixed with 4.4.36 |
| CVE-2016-9793: Fixed with 4.4.38 |
| CVE-2016-9794: Fixed with 4.4.37 |
| CVE-2016-9806: Fixed with 4.4.14 |
| CVE-2017-0605: Fixed with 4.4.269 |
| CVE-2017-0627: Fixed with 4.4.89 |
| CVE-2017-0750: Fixed with 4.4.66 |
| CVE-2017-0786: Fixed with 4.4.93 |
| CVE-2017-0861: Fixed with 4.4.106 |
| CVE-2017-1000: Fixed with 4.4.82 |
| CVE-2017-1000111: Fixed with 4.4.82 |
| CVE-2017-1000112: Fixed with 4.4.82 |
| CVE-2017-1000251: Fixed with 4.4.88 |
| CVE-2017-1000252: Fixed with 4.4.90 |
| CVE-2017-1000363: Fixed with 4.4.70 |
| CVE-2017-1000364: Fixed with 4.4.74 |
| CVE-2017-1000365: Fixed with 4.4.75 |
| CVE-2017-1000370: Fixed with 4.4.78 |
| CVE-2017-1000371: Fixed with 4.4.78 |
| CVE-2017-1000379: Fixed with 4.4.74 |
| CVE-2017-1000380: Fixed with 4.4.72 |
| CVE-2017-1000405: Fix not seen in stream |
| CVE-2017-1000407: Fixed with 4.4.106 |
| CVE-2017-1000410: Fixed with 4.4.112 |
| CVE-2017-10661: Fixed with 4.4.67 |
| CVE-2017-10662: Fixed with 4.4.68 |
| CVE-2017-10663: Fixed with 4.4.81 |
| CVE-2017-10810: Fixed with 4.4.77 |
| CVE-2017-10911: Fixed with 4.4.100 |
| CVE-2017-11089: Fixed with 4.4.78 |
| CVE-2017-11176: Fixed with 4.4.77 |
| CVE-2017-11472: Fixed with 4.4.114 |
| CVE-2017-11473: Fixed with 4.4.79 |
| CVE-2017-11600: Fixed with 4.4.87 |
| CVE-2017-12134: Fixed with 4.4.84 |
| CVE-2017-12146: Fixed with 4.4.77 |
| CVE-2017-12153: Fixed with 4.4.90 |
| CVE-2017-12154: Fixed with 4.4.90 |
| CVE-2017-12168: Fix not seen in stream |
| CVE-2017-12190: Fixed with 4.4.93 |
| CVE-2017-12192: Fixed with 4.4.90 |
| CVE-2017-12193: Fixed with 4.4.96 |
| CVE-2017-12762: Fixed with 4.4.80 |
| CVE-2017-13080: Fixed with 4.4.99 |
| CVE-2017-13166: Fix not seen in stream |
| CVE-2017-13167: Fixed with 4.4.2 |
| CVE-2017-13168: Fixed with 4.4.140 |
| CVE-2017-13215: Fixed with 4.4.2 |
| CVE-2017-13216: Fixed with 4.4.112 |
| CVE-2017-13305: Fixed with 4.4.116 |
| CVE-2017-13693: Fix unknown |
| CVE-2017-13694: Fix unknown |
| CVE-2017-13695: Fixed with 4.4.134 |
| CVE-2017-14051: Fixed with 4.4.89 |
| CVE-2017-14106: Fixed with 4.4.89 |
| CVE-2017-14140: Fixed with 4.4.84 |
| CVE-2017-14156: Fixed with 4.4.90 |
| CVE-2017-14340: Fixed with 4.4.88 |
| CVE-2017-14489: Fixed with 4.4.90 |
| CVE-2017-14991: Fixed with 4.4.89 |
| CVE-2017-15102: Fixed with 4.4.24 |
| CVE-2017-15115: Fixed with 4.4.100 |
| CVE-2017-15129: Fixed with 4.4.109 |
| CVE-2017-15265: Fixed with 4.4.93 |
| CVE-2017-15274: Fixed with 4.4.72 |
| CVE-2017-15299: Fixed with 4.4.95 |
| CVE-2017-15537: Fixed with 4.4.90 |
| CVE-2017-15649: Fixed with 4.4.94 |
| CVE-2017-15951: Fixed with 4.4.95 |
| CVE-2017-16525: Fixed with 4.4.93 |
| CVE-2017-16526: Fixed with 4.4.92 |
| CVE-2017-16527: Fixed with 4.4.93 |
| CVE-2017-16528: Fixed with 4.4.99 |
| CVE-2017-16529: Fixed with 4.4.92 |
| CVE-2017-16530: Fixed with 4.4.92 |
| CVE-2017-16531: Fixed with 4.4.92 |
| CVE-2017-16532: Fixed with 4.4.99 |
| CVE-2017-16533: Fixed with 4.4.93 |
| CVE-2017-16534: Fixed with 4.4.92 |
| CVE-2017-16535: Fixed with 4.4.95 |
| CVE-2017-16536: Fixed with 4.4.103 |
| CVE-2017-16537: Fixed with 4.4.100 |
| CVE-2017-16538: Fixed with 4.4.116 |
| CVE-2017-16643: Fixed with 4.4.96 |
| CVE-2017-16645: Fixed with 4.4.99 |
| CVE-2017-16646: Fixed with 4.4.100 |
| CVE-2017-16648: Fix not seen in stream |
| CVE-2017-16649: Fixed with 4.4.100 |
| CVE-2017-16650: Fixed with 4.4.100 |
| CVE-2017-16911: Fixed with 4.4.114 |
| CVE-2017-16912: Fixed with 4.4.114 |
| CVE-2017-16913: Fixed with 4.4.114 |
| CVE-2017-16914: Fixed with 4.4.107 |
| CVE-2017-16939: Fixed with 4.4.104 |
| CVE-2017-16994: Fixed with 4.4.101 |
| CVE-2017-16995: Fixed with 4.4.123 |
| CVE-2017-17448: Fixed with 4.4.114 |
| CVE-2017-17449: Fixed with 4.4.109 |
| CVE-2017-17450: Fixed with 4.4.114 |
| CVE-2017-17558: Fixed with 4.4.107 |
| CVE-2017-17712: Fixed with 4.4.109 |
| CVE-2017-17741: Fixed with 4.4.112 |
| CVE-2017-17805: Fixed with 4.4.107 |
| CVE-2017-17806: Fixed with 4.4.107 |
| CVE-2017-17807: Fixed with 4.4.107 |
| CVE-2017-17862: Fixed with 4.4.115 |
| CVE-2017-17975: Fixed with 4.4.127 |
| CVE-2017-18017: Fixed with 4.4.76 |
| CVE-2017-18075: Fixed with 4.4.111 |
| CVE-2017-18079: Fixed with 4.4.79 |
| CVE-2017-18174: Fix not seen in stream |
| CVE-2017-18193: Fixed with 4.4.120 |
| CVE-2017-18203: Fixed with 4.4.103 |
| CVE-2017-18204: Fixed with 4.4.101 |
| CVE-2017-18208: Fixed with 4.4.104 |
| CVE-2017-18216: Fixed with 4.4.143 |
| CVE-2017-18221: Fixed with 4.4.71 |
| CVE-2017-18222: Fixed with 4.4.124 |
| CVE-2017-18232: Fix not seen in stream |
| CVE-2017-18241: Fixed with 4.4.169 |
| CVE-2017-18249: Fixed with 4.4.172 |
| CVE-2017-18255: Fixed with 4.4.132 |
| CVE-2017-18257: Fixed with 4.4.132 |
| CVE-2017-18261: Fix not seen in stream |
| CVE-2017-18270: Fixed with 4.4.90 |
| CVE-2017-18344: Fixed with 4.4.116 |
| CVE-2017-18360: Fixed with 4.4.70 |
| CVE-2017-18509: Fixed with 4.4.187 |
| CVE-2017-18551: Fixed with 4.4.179 |
| CVE-2017-18552: Fix not seen in stream |
| CVE-2017-18595: Fixed with 4.4.109 |
| CVE-2017-2583: Fixed with 4.4.44 |
| CVE-2017-2584: Fixed with 4.4.44 |
| CVE-2017-2596: Fixed with 4.4.63 |
| CVE-2017-2618: Fixed with 4.4.49 |
| CVE-2017-2636: Fixed with 4.4.54 |
| CVE-2017-2671: Fixed with 4.4.65 |
| CVE-2017-5547: Fixed with 4.4.45 |
| CVE-2017-5549: Fixed with 4.4.44 |
| CVE-2017-5551: Fixed with 4.4.45 |
| CVE-2017-5669: Fixed with 4.4.53 |
| CVE-2017-5715: Fix not seen in stream |
| CVE-2017-5753: Fixed with 4.4.112 |
| CVE-2017-5754: Fixed with 4.4.144 |
| CVE-2017-5897: Fixed with 4.4.50 |
| CVE-2017-5967: Fix not seen in stream |
| CVE-2017-5970: Fixed with 4.4.50 |
| CVE-2017-5986: Fixed with 4.4.50 |
| CVE-2017-6001: Fixed with 4.4.65 |
| CVE-2017-6074: Fixed with 4.4.52 |
| CVE-2017-6214: Fixed with 4.4.50 |
| CVE-2017-6345: Fixed with 4.4.52 |
| CVE-2017-6346: Fixed with 4.4.52 |
| CVE-2017-6347: Fixed with 4.4.52 |
| CVE-2017-6348: Fixed with 4.4.52 |
| CVE-2017-6353: Fixed with 4.4.63 |
| CVE-2017-7184: Fixed with 4.4.59 |
| CVE-2017-7187: Fixed with 4.4.60 |
| CVE-2017-7261: Fixed with 4.4.61 |
| CVE-2017-7273: Fixed with 4.4.43 |
| CVE-2017-7294: Fixed with 4.4.61 |
| CVE-2017-7308: Fixed with 4.4.62 |
| CVE-2017-7346: Fixed with 4.4.72 |
| CVE-2017-7374: Fixed with 4.4.59 |
| CVE-2017-7472: Fixed with 4.4.64 |
| CVE-2017-7482: Fixed with 4.4.75 |
| CVE-2017-7487: Fixed with 4.4.70 |
| CVE-2017-7495: Fixed with 4.4.18 |
| CVE-2017-7518: Fixed with 4.4.100 |
| CVE-2017-7533: Fixed with 4.4.80 |
| CVE-2017-7541: Fixed with 4.4.78 |
| CVE-2017-7542: Fixed with 4.4.81 |
| CVE-2017-7616: Fixed with 4.4.61 |
| CVE-2017-7618: Fixed with 4.4.63 |
| CVE-2017-7645: Fixed with 4.4.66 |
| CVE-2017-7889: Fixed with 4.4.63 |
| CVE-2017-7895: Fixed with 4.4.67 |
| CVE-2017-8064: Fixed with 4.4.63 |
| CVE-2017-8065: Fix not seen in stream |
| CVE-2017-8797: Fix not seen in stream |
| CVE-2017-8824: Fixed with 4.4.116 |
| CVE-2017-8831: Fixed with 4.4.81 |
| CVE-2017-8890: Fixed with 4.4.71 |
| CVE-2017-8924: Fixed with 4.4.55 |
| CVE-2017-8925: Fixed with 4.4.55 |
| CVE-2017-9074: Fixed with 4.4.71 |
| CVE-2017-9075: Fixed with 4.4.71 |
| CVE-2017-9076: Fixed with 4.4.71 |
| CVE-2017-9077: Fixed with 4.4.71 |
| CVE-2017-9150: Fixed with 4.4.100 |
| CVE-2017-9242: Fixed with 4.4.71 |
| CVE-2017-9605: Fixed with 4.4.72 |
| CVE-2017-9984: Fixed with 4.4.88 |
| CVE-2017-9985: Fixed with 4.4.88 |
| CVE-2017-9986: Fix not seen in stream |
| CVE-2018-1000004: Fixed with 4.4.115 |
| CVE-2018-1000026: Fixed with 4.4.181 |
| CVE-2018-1000028: Fixed with 4.4.114 |
| CVE-2018-1000199: Fixed with 4.4.127 |
| CVE-2018-1000204: Fixed with 4.4.133 |
| CVE-2018-10021: Fixed with 4.4.133 |
| CVE-2018-10087: Fixed with 4.4.133 |
| CVE-2018-10124: Fixed with 4.4.134 |
| CVE-2018-10322: Fix not seen in stream |
| CVE-2018-10323: Fixed with 4.4.232 |
| CVE-2018-1065: Fixed with 4.4.122 |
| CVE-2018-1066: Fixed with 4.4.124 |
| CVE-2018-10675: Fixed with 4.4.84 |
| CVE-2018-1068: Fixed with 4.4.122 |
| CVE-2018-1087: Fixed with 4.4.125 |
| CVE-2018-10876: Fixed with 4.4.140 |
| CVE-2018-10877: Fixed with 4.4.140 |
| CVE-2018-10878: Fixed with 4.4.140 |
| CVE-2018-10879: Fixed with 4.4.140 |
| CVE-2018-10880: Fixed with 4.4.160 |
| CVE-2018-10881: Fixed with 4.4.140 |
| CVE-2018-10882: Fixed with 4.4.140 |
| CVE-2018-10883: Fixed with 4.4.140 |
| CVE-2018-10902: Fixed with 4.4.144 |
| CVE-2018-1092: Fixed with 4.4.129 |
| CVE-2018-1093: Fixed with 4.4.131 |
| CVE-2018-10938: Fixed with 4.4.154 |
| CVE-2018-10940: Fixed with 4.4.130 |
| CVE-2018-1120: Fixed with 4.4.168 |
| CVE-2018-1121: Fix unknown |
| CVE-2018-1128: Fix not seen in stream |
| CVE-2018-1129: Fix not seen in stream |
| CVE-2018-1130: Fixed with 4.4.126 |
| CVE-2018-12126: Fix not seen in stream |
| CVE-2018-12127: Fix not seen in stream |
| CVE-2018-12130: Fix not seen in stream |
| CVE-2018-12207: Fix not seen in stream |
| CVE-2018-12233: Fixed with 4.4.147 |
| CVE-2018-12896: Fixed with 4.4.168 |
| CVE-2018-12928: Fix unknown |
| CVE-2018-12929: Fix unknown |
| CVE-2018-12930: Fix unknown |
| CVE-2018-12931: Fix unknown |
| CVE-2018-13053: Fixed with 4.4.160 |
| CVE-2018-13093: Fixed with 4.4.245 |
| CVE-2018-13094: Fixed with 4.4.233 |
| CVE-2018-13095: Fix not seen in stream |
| CVE-2018-13096: Fixed with 4.4.172 |
| CVE-2018-13097: Fixed with 4.4.172 |
| CVE-2018-13098: Fix not seen in stream |
| CVE-2018-13099: Fixed with 4.4.172 |
| CVE-2018-13100: Fixed with 4.4.172 |
| CVE-2018-13405: Fixed with 4.4.141 |
| CVE-2018-13406: Fixed with 4.4.139 |
| CVE-2018-14609: Fixed with 4.4.156 |
| CVE-2018-14610: Fixed with 4.4.171 |
| CVE-2018-14611: Fixed with 4.4.171 |
| CVE-2018-14612: Fixed with 4.4.171 |
| CVE-2018-14613: Fixed with 4.4.171 |
| CVE-2018-14614: Fixed with 4.4.172 |
| CVE-2018-14616: Fixed with 4.4.172 |
| CVE-2018-14617: Fixed with 4.4.156 |
| CVE-2018-14633: Fixed with 4.4.159 |
| CVE-2018-14634: Fixed with 4.4.78 |
| CVE-2018-14734: Fixed with 4.4.146 |
| CVE-2018-15572: Fixed with 4.4.148 |
| CVE-2018-16276: Fixed with 4.4.141 |
| CVE-2018-16597: Fixed with 4.4.185 |
| CVE-2018-16658: Fixed with 4.4.154 |
| CVE-2018-16862: Fixed with 4.4.167 |
| CVE-2018-16884: Fixed with 4.4.171 |
| CVE-2018-17182: Fixed with 4.4.157 |
| CVE-2018-17972: Fixed with 4.4.160 |
| CVE-2018-17977: Fix unknown |
| CVE-2018-18021: Fixed with 4.4.160 |
| CVE-2018-18281: Fixed with 4.4.163 |
| CVE-2018-18386: Fixed with 4.4.109 |
| CVE-2018-18559: Fixed with 4.4.106 |
| CVE-2018-18690: Fixed with 4.4.172 |
| CVE-2018-18710: Fixed with 4.4.164 |
| CVE-2018-19824: Fixed with 4.4.167 |
| CVE-2018-19985: Fixed with 4.4.170 |
| CVE-2018-20169: Fixed with 4.4.167 |
| CVE-2018-20509: Fix not seen in stream |
| CVE-2018-20510: Fixed with 4.4.181 |
| CVE-2018-20511: Fixed with 4.4.159 |
| CVE-2018-20836: Fixed with 4.4.180 |
| CVE-2018-20854: Fix not seen in stream |
| CVE-2018-20855: Fix not seen in stream |
| CVE-2018-20856: Fixed with 4.4.189 |
| CVE-2018-20961: Fixed with 4.4.190 |
| CVE-2018-20976: Fixed with 4.4.197 |
| CVE-2018-21008: Fixed with 4.4.211 |
| CVE-2018-25020: Fix not seen in stream |
| CVE-2018-3620: Fix not seen in stream |
| CVE-2018-3639: Fixed with 4.4.144 |
| CVE-2018-3646: Fix not seen in stream |
| CVE-2018-3693: Fixed with 4.4.152 |
| CVE-2018-5332: Fixed with 4.4.112 |
| CVE-2018-5333: Fixed with 4.4.112 |
| CVE-2018-5344: Fixed with 4.4.115 |
| CVE-2018-5391: Fixed with 4.4.174 |
| CVE-2018-5750: Fixed with 4.4.116 |
| CVE-2018-5803: Fixed with 4.4.121 |
| CVE-2018-5814: Fixed with 4.4.133 |
| CVE-2018-5848: Fixed with 4.4.168 |
| CVE-2018-5873: Fixed with 4.4.116 |
| CVE-2018-5953: Fixed with 4.4.168 |
| CVE-2018-5995: Fix not seen in stream |
| CVE-2018-6412: Fixed with 4.4.134 |
| CVE-2018-6554: Fixed with 4.4.156 |
| CVE-2018-6555: Fixed with 4.4.156 |
| CVE-2018-6927: Fixed with 4.4.113 |
| CVE-2018-7191: Fixed with 4.4.99 |
| CVE-2018-7273: Fix not seen in stream |
| CVE-2018-7480: Fixed with 4.4.123 |
| CVE-2018-7492: Fixed with 4.4.106 |
| CVE-2018-7566: Fixed with 4.4.117 |
| CVE-2018-7754: Fix not seen in stream |
| CVE-2018-7755: Fixed with 4.4.160 |
| CVE-2018-7757: Fixed with 4.4.128 |
| CVE-2018-7995: Fixed with 4.4.122 |
| CVE-2018-8043: Fixed with 4.4.233 |
| CVE-2018-8781: Fixed with 4.4.125 |
| CVE-2018-8822: Fixed with 4.4.125 |
| CVE-2018-8897: Fixed with 4.4.125 |
| CVE-2018-9363: Fixed with 4.4.149 |
| CVE-2018-9385: Fixed with 4.4.131 |
| CVE-2018-9415: Fixed with 4.4.131 |
| CVE-2018-9422: Fixed with 4.4.128 |
| CVE-2018-9465: Fix not seen in stream |
| CVE-2018-9516: Fixed with 4.4.140 |
| CVE-2018-9517: Fixed with 4.4.225 |
| CVE-2018-9518: Fixed with 4.4.134 |
| CVE-2018-9568: Fixed with 4.4.94 |
| CVE-2019-0136: Fixed with 4.4.185 |
| CVE-2019-0148: Fixed with 4.4.244 |
| CVE-2019-0154: Fixed with 4.4.201 |
| CVE-2019-0155: Fixed with 4.4.201 |
| CVE-2019-10126: Fixed with 4.4.186 |
| CVE-2019-10142: Fixed with 4.4.180 |
| CVE-2019-10207: Fixed with 4.4.187 |
| CVE-2019-10220: Fix not seen in stream |
| CVE-2019-10638: Fixed with 4.4.191 |
| CVE-2019-10639: Fixed with 4.4.179 |
| CVE-2019-11091: Fix not seen in stream |
| CVE-2019-11135: Fixed with 4.4.202 |
| CVE-2019-11190: Fixed with 4.4.179 |
| CVE-2019-11191: Fix not seen in stream |
| CVE-2019-1125: Fixed with 4.4.189 |
| CVE-2019-11477: Fixed with 4.4.182 |
| CVE-2019-11478: Fixed with 4.4.182 |
| CVE-2019-11479: Fixed with 4.4.182 |
| CVE-2019-11486: Fixed with 4.4.179 |
| CVE-2019-11487: Fixed with 4.4.216 |
| CVE-2019-11599: Fixed with 4.4.183 |
| CVE-2019-11810: Fixed with 4.4.179 |
| CVE-2019-11815: Fixed with 4.4.179 |
| CVE-2019-11833: Fixed with 4.4.181 |
| CVE-2019-11884: Fixed with 4.4.180 |
| CVE-2019-12378: Fix not seen in stream |
| CVE-2019-12379: Fix not seen in stream |
| CVE-2019-12380: Fix not seen in stream |
| CVE-2019-12381: Fix not seen in stream |
| CVE-2019-12382: Fix not seen in stream |
| CVE-2019-12456: Fix unknown |
| CVE-2019-12614: Fixed with 4.4.206 |
| CVE-2019-12615: Fix not seen in stream |
| CVE-2019-12818: Fixed with 4.4.177 |
| CVE-2019-12819: Fixed with 4.4.177 |
| CVE-2019-12881: Fixed with 4.4.155 |
| CVE-2019-13272: Fixed with 4.4.185 |
| CVE-2019-13631: Fixed with 4.4.187 |
| CVE-2019-13648: Fixed with 4.4.187 |
| CVE-2019-14283: Fixed with 4.4.187 |
| CVE-2019-14284: Fixed with 4.4.187 |
| CVE-2019-14615: Fixed with 4.4.210 |
| CVE-2019-14814: Fixed with 4.4.194 |
| CVE-2019-14816: Fixed with 4.4.194 |
| CVE-2019-14821: Fixed with 4.4.194 |
| CVE-2019-14835: Fixed with 4.4.193 |
| CVE-2019-14895: Fixed with 4.4.210 |
| CVE-2019-14896: Fixed with 4.4.212 |
| CVE-2019-14897: Fixed with 4.4.212 |
| CVE-2019-14901: Fixed with 4.4.217 |
| CVE-2019-15098: Fixed with 4.4.199 |
| CVE-2019-15117: Fixed with 4.4.191 |
| CVE-2019-15118: Fixed with 4.4.191 |
| CVE-2019-15211: Fixed with 4.4.187 |
| CVE-2019-15212: Fixed with 4.4.181 |
| CVE-2019-15214: Fixed with 4.4.179 |
| CVE-2019-15215: Fixed with 4.4.187 |
| CVE-2019-15216: Fixed with 4.4.180 |
| CVE-2019-15217: Fixed with 4.4.211 |
| CVE-2019-15218: Fixed with 4.4.181 |
| CVE-2019-15219: Fixed with 4.4.181 |
| CVE-2019-15220: Fixed with 4.4.211 |
| CVE-2019-15221: Fixed with 4.4.211 |
| CVE-2019-15222: Fix not seen in stream |
| CVE-2019-15223: Fix not seen in stream |
| CVE-2019-15239: Fixed with 4.4.187 |
| CVE-2019-15290: Fix unknown |
| CVE-2019-15291: Fixed with 4.4.204 |
| CVE-2019-15292: Fixed with 4.4.179 |
| CVE-2019-15505: Fixed with 4.4.194 |
| CVE-2019-15666: Fixed with 4.4.181 |
| CVE-2019-15807: Fixed with 4.4.183 |
| CVE-2019-15902: Fixed with 4.4.191 |
| CVE-2019-15916: Fixed with 4.4.177 |
| CVE-2019-15917: Fixed with 4.4.203 |
| CVE-2019-15926: Fixed with 4.4.187 |
| CVE-2019-15927: Fixed with 4.4.170 |
| CVE-2019-16230: Fix not seen in stream |
| CVE-2019-16231: Fix not seen in stream |
| CVE-2019-16232: Fixed with 4.4.262 |
| CVE-2019-16233: Fixed with 4.4.215 |
| CVE-2019-16234: Fixed with 4.4.216 |
| CVE-2019-16413: Fixed with 4.4.177 |
| CVE-2019-16746: Fixed with 4.4.197 |
| CVE-2019-16921: Fix not seen in stream |
| CVE-2019-16995: Fixed with 4.4.177 |
| CVE-2019-17052: Fixed with 4.4.195 |
| CVE-2019-17053: Fixed with 4.4.195 |
| CVE-2019-17054: Fixed with 4.4.195 |
| CVE-2019-17055: Fixed with 4.4.195 |
| CVE-2019-17056: Fixed with 4.4.195 |
| CVE-2019-17075: Fixed with 4.4.198 |
| CVE-2019-17133: Fixed with 4.4.198 |
| CVE-2019-17351: Fixed with 4.4.211 |
| CVE-2019-17666: Fixed with 4.4.199 |
| CVE-2019-18282: Fixed with 4.4.200 |
| CVE-2019-18660: Fixed with 4.4.204 |
| CVE-2019-18675: Fixed with 4.4.137 |
| CVE-2019-18680: Fixed with 4.4.195 |
| CVE-2019-18683: Fixed with 4.4.204 |
| CVE-2019-18806: Fixed with 4.4.196 |
| CVE-2019-18885: Fix not seen in stream |
| CVE-2019-19036: Fix not seen in stream |
| CVE-2019-19039: Fix not seen in stream |
| CVE-2019-19049: Fixed with 4.4.200 |
| CVE-2019-19052: Fixed with 4.4.201 |
| CVE-2019-19054: Fixed with 4.4.233 |
| CVE-2019-19056: Fixed with 4.4.210 |
| CVE-2019-19057: Fixed with 4.4.208 |
| CVE-2019-19060: Fixed with 4.4.262 |
| CVE-2019-19061: Fixed with 4.4.262 |
| CVE-2019-19062: Fixed with 4.4.207 |
| CVE-2019-19063: Fixed with 4.4.208 |
| CVE-2019-19066: Fixed with 4.4.210 |
| CVE-2019-19068: Fixed with 4.4.210 |
| CVE-2019-19073: Fixed with 4.4.233 |
| CVE-2019-19074: Fixed with 4.4.233 |
| CVE-2019-19227: Fixed with 4.4.207 |
| CVE-2019-19241: Fix not seen in stream |
| CVE-2019-19319: Fixed with 4.4.221 |
| CVE-2019-19332: Fixed with 4.4.207 |
| CVE-2019-19377: Fix not seen in stream |
| CVE-2019-19378: Fix unknown |
| CVE-2019-19447: Fixed with 4.4.208 |
| CVE-2019-19448: Fixed with 4.4.233 |
| CVE-2019-19449: Fix not seen in stream |
| CVE-2019-19523: Fixed with 4.4.197 |
| CVE-2019-19524: Fixed with 4.4.203 |
| CVE-2019-19525: Fixed with 4.4.197 |
| CVE-2019-19527: Fixed with 4.4.190 |
| CVE-2019-19528: Fixed with 4.4.197 |
| CVE-2019-19530: Fixed with 4.4.190 |
| CVE-2019-19531: Fixed with 4.4.190 |
| CVE-2019-19532: Fixed with 4.4.199 |
| CVE-2019-19533: Fixed with 4.4.195 |
| CVE-2019-19534: Fixed with 4.4.201 |
| CVE-2019-19535: Fixed with 4.4.190 |
| CVE-2019-19536: Fixed with 4.4.190 |
| CVE-2019-19537: Fixed with 4.4.190 |
| CVE-2019-19768: Fixed with 4.4.224 |
| CVE-2019-19813: Fixed with 4.4.247 |
| CVE-2019-19814: Fix unknown |
| CVE-2019-19815: Fix not seen in stream |
| CVE-2019-19816: Fixed with 4.4.247 |
| CVE-2019-19922: Fix not seen in stream |
| CVE-2019-19927: Fix not seen in stream |
| CVE-2019-19965: Fixed with 4.4.209 |
| CVE-2019-19966: Fixed with 4.4.181 |
| CVE-2019-1999: Fix not seen in stream |
| CVE-2019-20054: Fixed with 4.4.178 |
| CVE-2019-20096: Fixed with 4.4.211 |
| CVE-2019-2024: Fixed with 4.4.167 |
| CVE-2019-2025: Fix not seen in stream |
| CVE-2019-2054: Fix not seen in stream |
| CVE-2019-20636: Fixed with 4.4.210 |
| CVE-2019-20794: Fix unknown |
| CVE-2019-20806: Fix not seen in stream |
| CVE-2019-20810: Fixed with 4.4.228 |
| CVE-2019-20811: Fix not seen in stream |
| CVE-2019-20812: Fixed with 4.4.208 |
| CVE-2019-20908: Fix not seen in stream |
| CVE-2019-20934: Fixed with 4.4.187 |
| CVE-2019-2101: Fixed with 4.4.177 |
| CVE-2019-2181: Fix not seen in stream |
| CVE-2019-2213: Fix not seen in stream |
| CVE-2019-2215: Fixed with 4.4.196 |
| CVE-2019-3459: Fixed with 4.4.178 |
| CVE-2019-3460: Fixed with 4.4.178 |
| CVE-2019-3701: Fixed with 4.4.172 |
| CVE-2019-3846: Fixed with 4.4.186 |
| CVE-2019-3874: Fix not seen in stream |
| CVE-2019-3882: Fixed with 4.4.180 |
| CVE-2019-3892: Fixed with 4.4.183 |
| CVE-2019-3900: Fixed with 4.4.191 |
| CVE-2019-3901: Fixed with 4.4.12 |
| CVE-2019-5108: Fixed with 4.4.211 |
| CVE-2019-5489: Fix not seen in stream |
| CVE-2019-6133: Fixed with 4.4.170 |
| CVE-2019-6974: Fixed with 4.4.176 |
| CVE-2019-7221: Fixed with 4.4.175 |
| CVE-2019-7222: Fixed with 4.4.175 |
| CVE-2019-7308: Fix not seen in stream |
| CVE-2019-9213: Fixed with 4.4.177 |
| CVE-2019-9445: Fixed with 4.4.233 |
| CVE-2019-9453: Fix not seen in stream |
| CVE-2019-9454: Fixed with 4.4.179 |
| CVE-2019-9455: Fixed with 4.4.177 |
| CVE-2019-9456: Fixed with 4.4.122 |
| CVE-2019-9457: Fixed with 4.4.78 |
| CVE-2019-9458: Fixed with 4.4.160 |
| CVE-2019-9466: Fixed with 4.4.181 |
| CVE-2019-9503: Fixed with 4.4.181 |
| CVE-2019-9506: Fixed with 4.4.185 |
| CVE-2020-0009: Fixed with 4.4.215 |
| CVE-2020-0030: Fixed with 4.4.196 |
| CVE-2020-0067: Fix not seen in stream |
| CVE-2020-0255: Fixed with 4.4.222 |
| CVE-2020-0305: Fixed with 4.4.210 |
| CVE-2020-0347: Fix unknown |
| CVE-2020-0404: Fixed with 4.4.214 |
| CVE-2020-0427: Fixed with 4.4.244 |
| CVE-2020-0429: Fixed with 4.4.219 |
| CVE-2020-0431: Fixed with 4.4.210 |
| CVE-2020-0432: Fixed with 4.4.213 |
| CVE-2020-0433: Fixed with 4.4.224 |
| CVE-2020-0435: Fix not seen in stream |
| CVE-2020-0444: Fixed with 4.4.216 |
| CVE-2020-0465: Fixed with 4.4.236 |
| CVE-2020-0466: Fixed with 4.4.234 |
| CVE-2020-0543: Fixed with 4.4.227 |
| CVE-2020-10135: Fixed with 4.4.240 |
| CVE-2020-10690: Fixed with 4.4.224 |
| CVE-2020-10708: Fix unknown |
| CVE-2020-10711: Fixed with 4.4.224 |
| CVE-2020-10720: Fixed with 4.4.181 |
| CVE-2020-10732: Fixed with 4.4.226 |
| CVE-2020-10751: Fixed with 4.4.222 |
| CVE-2020-10766: Fixed with 4.4.228 |
| CVE-2020-10767: Fixed with 4.4.228 |
| CVE-2020-10768: Fixed with 4.4.228 |
| CVE-2020-10769: Fixed with 4.4.172 |
| CVE-2020-10773: Fixed with 4.4.199 |
| CVE-2020-10942: Fixed with 4.4.218 |
| CVE-2020-11494: Fixed with 4.4.219 |
| CVE-2020-11565: Fixed with 4.4.219 |
| CVE-2020-11608: Fixed with 4.4.218 |
| CVE-2020-11609: Fixed with 4.4.218 |
| CVE-2020-11668: Fixed with 4.4.218 |
| CVE-2020-11669: Fix not seen in stream |
| CVE-2020-11725: Fix unknown |
| CVE-2020-12114: Fixed with 4.4.221 |
| CVE-2020-12352: Fixed with 4.4.240 |
| CVE-2020-12362: Fix not seen in stream |
| CVE-2020-12363: Fix not seen in stream |
| CVE-2020-12364: Fix not seen in stream |
| CVE-2020-12464: Fixed with 4.4.221 |
| CVE-2020-12652: Fixed with 4.4.211 |
| CVE-2020-12653: Fixed with 4.4.214 |
| CVE-2020-12654: Fixed with 4.4.214 |
| CVE-2020-12655: Fix not seen in stream |
| CVE-2020-12656: Fix not seen in stream |
| CVE-2020-12769: Fixed with 4.4.224 |
| CVE-2020-12770: Fixed with 4.4.224 |
| CVE-2020-12771: Fixed with 4.4.229 |
| CVE-2020-12826: Fixed with 4.4.220 |
| CVE-2020-12888: Fix not seen in stream |
| CVE-2020-13143: Fixed with 4.4.224 |
| CVE-2020-13974: Fixed with 4.4.227 |
| CVE-2020-14304: Fix unknown |
| CVE-2020-14305: Fix not seen in stream |
| CVE-2020-14314: Fixed with 4.4.234 |
| CVE-2020-14331: Fixed with 4.4.233 |
| CVE-2020-14351: Fixed with 4.4.244 |
| CVE-2020-14353: Fixed with 4.4.90 |
| CVE-2020-14381: Fixed with 4.4.218 |
| CVE-2020-14390: Fixed with 4.4.237 |
| CVE-2020-14416: Fixed with 4.4.212 |
| CVE-2020-15393: Fixed with 4.4.230 |
| CVE-2020-15436: Fixed with 4.4.229 |
| CVE-2020-15437: Fixed with 4.4.232 |
| CVE-2020-15802: Fix unknown |
| CVE-2020-16120: Fix not seen in stream |
| CVE-2020-16166: Fixed with 4.4.233 |
| CVE-2020-1749: Fixed with 4.4.224 |
| CVE-2020-24502: Fix unknown |
| CVE-2020-24503: Fix unknown |
| CVE-2020-24586: Fixed with 4.4.271 |
| CVE-2020-24587: Fixed with 4.4.271 |
| CVE-2020-24588: Fixed with 4.4.271 |
| CVE-2020-25211: Fixed with 4.4.239 |
| CVE-2020-25212: Fixed with 4.4.233 |
| CVE-2020-25284: Fixed with 4.4.237 |
| CVE-2020-25285: Fixed with 4.4.236 |
| CVE-2020-25643: Fixed with 4.4.238 |
| CVE-2020-25645: Fixed with 4.4.244 |
| CVE-2020-25656: Fixed with 4.4.242 |
| CVE-2020-25668: Fixed with 4.4.242 |
| CVE-2020-25669: Fixed with 4.4.245 |
| CVE-2020-25670: Fixed with 4.4.267 |
| CVE-2020-25671: Fixed with 4.4.267 |
| CVE-2020-25672: Fixed with 4.4.267 |
| CVE-2020-25673: Fixed with 4.4.267 |
| CVE-2020-25705: Fixed with 4.4.241 |
| CVE-2020-26088: Fixed with 4.4.233 |
| CVE-2020-26139: Fixed with 4.4.271 |
| CVE-2020-26140: Fix unknown |
| CVE-2020-26141: Fix not seen in stream |
| CVE-2020-26142: Fix unknown |
| CVE-2020-26143: Fix unknown |
| CVE-2020-26145: Fix not seen in stream |
| CVE-2020-26147: Fixed with 4.4.271 |
| CVE-2020-26541: Fix not seen in stream |
| CVE-2020-26555: Fixed with 4.4.270 |
| CVE-2020-26556: Fix unknown |
| CVE-2020-26557: Fix unknown |
| CVE-2020-26558: Fixed with 4.4.270 |
| CVE-2020-26559: Fix unknown |
| CVE-2020-26560: Fix unknown |
| CVE-2020-27066: Fixed with 4.4.218 |
| CVE-2020-27067: Fixed with 4.4.225 |
| CVE-2020-27068: Fixed with 4.4.216 |
| CVE-2020-2732: Fixed with 4.4.215 |
| CVE-2020-27673: Fixed with 4.4.244 |
| CVE-2020-27675: Fixed with 4.4.244 |
| CVE-2020-27777: Fix not seen in stream |
| CVE-2020-27784: Fixed with 4.4.241 |
| CVE-2020-27786: Fixed with 4.4.224 |
| CVE-2020-27815: Fixed with 4.4.249 |
| CVE-2020-27820: Fix not seen in stream |
| CVE-2020-27825: Fixed with 4.4.254 |
| CVE-2020-28097: Fixed with 4.4.237 |
| CVE-2020-28374: Fixed with 4.4.252 |
| CVE-2020-28915: Fixed with 4.4.239 |
| CVE-2020-28974: Fixed with 4.4.242 |
| CVE-2020-29370: Fixed with 4.4.217 |
| CVE-2020-29371: Fixed with 4.4.234 |
| CVE-2020-29374: Fixed with 4.4.289 |
| CVE-2020-29568: Fixed with 4.4.249 |
| CVE-2020-29660: Fixed with 4.4.248 |
| CVE-2020-29661: Fixed with 4.4.248 |
| CVE-2020-35501: Fix unknown |
| CVE-2020-35508: Fixed with 4.4.242 |
| CVE-2020-35519: Fixed with 4.4.248 |
| CVE-2020-36158: Fixed with 4.4.250 |
| CVE-2020-36310: Fix not seen in stream |
| CVE-2020-36313: Fix not seen in stream |
| CVE-2020-36322: Fix not seen in stream |
| CVE-2020-36385: Fix not seen in stream |
| CVE-2020-36386: Fixed with 4.4.233 |
| CVE-2020-36516: Fixed with 4.4.302 |
| CVE-2020-36557: Fixed with 4.4.218 |
| CVE-2020-36558: Fixed with 4.4.215 |
| CVE-2020-36691: Fix not seen in stream |
| CVE-2020-3702: Fixed with 4.4.284 |
| CVE-2020-4788: Fixed with 4.4.245 |
| CVE-2020-8647: Fixed with 4.4.216 |
| CVE-2020-8648: Fixed with 4.4.216 |
| CVE-2020-8649: Fixed with 4.4.216 |
| CVE-2020-8694: Fixed with 4.4.243 |
| CVE-2020-8832: Fix not seen in stream |
| CVE-2020-9383: Fixed with 4.4.215 |
| CVE-2021-0129: Fixed with 4.4.270 |
| CVE-2021-0399: Fix unknown |
| CVE-2021-0447: Fixed with 4.4.225 |
| CVE-2021-0448: Fixed with 4.4.239 |
| CVE-2021-0512: Fixed with 4.4.259 |
| CVE-2021-0605: Fixed with 4.4.238 |
| CVE-2021-0920: Fixed with 4.4.278 |
| CVE-2021-0929: Fix not seen in stream |
| CVE-2021-0937: Fixed with 4.4.267 |
| CVE-2021-0941: Fix not seen in stream |
| CVE-2021-1048: Fixed with 4.4.236 |
| CVE-2021-20261: Fixed with 4.4.262 |
| CVE-2021-20265: Fixed with 4.4.4 |
| CVE-2021-20292: Fix not seen in stream |
| CVE-2021-20317: Fix not seen in stream |
| CVE-2021-20320: Fixed with 4.4.285 |
| CVE-2021-20321: Fixed with 4.4.290 |
| CVE-2021-21781: Fixed with 4.4.278 |
| CVE-2021-22543: Fix not seen in stream |
| CVE-2021-22555: Fixed with 4.4.267 |
| CVE-2021-26401: Fix not seen in stream |
| CVE-2021-26930: Fixed with 4.4.258 |
| CVE-2021-26931: Fixed with 4.4.258 |
| CVE-2021-26932: Fixed with 4.4.258 |
| CVE-2021-27363: Fixed with 4.4.260 |
| CVE-2021-27364: Fixed with 4.4.260 |
| CVE-2021-27365: Fixed with 4.4.260 |
| CVE-2021-28038: Fixed with 4.4.260 |
| CVE-2021-28660: Fixed with 4.4.262 |
| CVE-2021-28688: Fixed with 4.4.264 |
| CVE-2021-28711: Fixed with 4.4.296 |
| CVE-2021-28712: Fixed with 4.4.296 |
| CVE-2021-28713: Fixed with 4.4.296 |
| CVE-2021-28714: Fix not seen in stream |
| CVE-2021-28715: Fixed with 4.4.296 |
| CVE-2021-28964: Fixed with 4.4.263 |
| CVE-2021-28972: Fixed with 4.4.263 |
| CVE-2021-29154: Fixed with 4.4.266 |
| CVE-2021-29155: Fix not seen in stream |
| CVE-2021-29265: Fixed with 4.4.262 |
| CVE-2021-29650: Fixed with 4.4.271 |
| CVE-2021-30002: Fixed with 4.4.260 |
| CVE-2021-3178: Fixed with 4.4.253 |
| CVE-2021-31916: Fixed with 4.4.269 |
| CVE-2021-32078: Fix not seen in stream |
| CVE-2021-32399: Fixed with 4.4.271 |
| CVE-2021-33034: Fixed with 4.4.269 |
| CVE-2021-33061: Fix not seen in stream |
| CVE-2021-33098: Fix not seen in stream |
| CVE-2021-33655: Fix not seen in stream |
| CVE-2021-33656: Fix not seen in stream |
| CVE-2021-33909: Fixed with 4.4.276 |
| CVE-2021-34556: Fix not seen in stream |
| CVE-2021-34693: Fixed with 4.4.274 |
| CVE-2021-3483: Fixed with 4.4.265 |
| CVE-2021-34981: Fixed with 4.4.271 |
| CVE-2021-3506: Fix not seen in stream |
| CVE-2021-3542: Fix unknown |
| CVE-2021-35477: Fix not seen in stream |
| CVE-2021-3564: Fixed with 4.4.272 |
| CVE-2021-3573: Fixed with 4.4.272 |
| CVE-2021-3587: Fixed with 4.4.272 |
| CVE-2021-3609: Fixed with 4.4.276 |
| CVE-2021-3612: Fixed with 4.4.259 |
| CVE-2021-3640: Fixed with 4.4.293 |
| CVE-2021-3653: Fixed with 4.4.282 |
| CVE-2021-3655: Fixed with 4.4.285 |
| CVE-2021-3659: Fixed with 4.4.267 |
| CVE-2021-3669: Fix not seen in stream |
| CVE-2021-3679: Fixed with 4.4.277 |
| CVE-2021-3714: Fix unknown |
| CVE-2021-3715: Fixed with 4.4.218 |
| CVE-2021-37159: Fixed with 4.4.292 |
| CVE-2021-3732: Fixed with 4.4.281 |
| CVE-2021-3752: Fixed with 4.4.293 |
| CVE-2021-3753: Fixed with 4.4.283 |
| CVE-2021-37576: Fixed with 4.4.277 |
| CVE-2021-3760: Fixed with 4.4.290 |
| CVE-2021-3772: Fixed with 4.4.291 |
| CVE-2021-38160: Fixed with 4.4.276 |
| CVE-2021-38198: Fix not seen in stream |
| CVE-2021-38204: Fixed with 4.4.277 |
| CVE-2021-38205: Fixed with 4.4.281 |
| CVE-2021-38208: Fixed with 4.4.272 |
| CVE-2021-38300: Fix not seen in stream |
| CVE-2021-3847: Fix unknown |
| CVE-2021-3864: Fix unknown |
| CVE-2021-3892: Fix unknown |
| CVE-2021-3896: Fixed with 4.4.290 |
| CVE-2021-39633: Fix not seen in stream |
| CVE-2021-39634: Fixed with 4.4.239 |
| CVE-2021-39636: Fix not seen in stream |
| CVE-2021-39648: Fix not seen in stream |
| CVE-2021-39657: Fixed with 4.4.254 |
| CVE-2021-39685: Fixed with 4.4.295 |
| CVE-2021-39686: Fixed with 4.4.293 |
| CVE-2021-39698: Fixed with 4.4.295 |
| CVE-2021-39714: Fix not seen in stream |
| CVE-2021-39800: Fix unknown |
| CVE-2021-39801: Fix unknown |
| CVE-2021-4002: Fixed with 4.4.294 |
| CVE-2021-4023: Fix not seen in stream |
| CVE-2021-4037: Fix not seen in stream |
| CVE-2021-40490: Fixed with 4.4.284 |
| CVE-2021-4083: Fixed with 4.4.294 |
| CVE-2021-4149: Fix not seen in stream |
| CVE-2021-4150: Fix not seen in stream |
| CVE-2021-4155: Fixed with 4.4.299 |
| CVE-2021-4157: Fixed with 4.4.269 |
| CVE-2021-4159: Fix not seen in stream |
| CVE-2021-4197: Fix not seen in stream |
| CVE-2021-42008: Fixed with 4.4.282 |
| CVE-2021-4202: Fixed with 4.4.293 |
| CVE-2021-4203: Fixed with 4.4.288 |
| CVE-2021-4218: Fix not seen in stream |
| CVE-2021-42739: Fix not seen in stream |
| CVE-2021-43389: Fixed with 4.4.290 |
| CVE-2021-43975: Fix not seen in stream |
| CVE-2021-43976: Fixed with 4.4.300 |
| CVE-2021-44879: Fix not seen in stream |
| CVE-2021-45095: Fixed with 4.4.299 |
| CVE-2021-45469: Fix not seen in stream |
| CVE-2021-45485: Fixed with 4.4.276 |
| CVE-2021-45486: Fixed with 4.4.274 |
| CVE-2021-45868: Fixed with 4.4.293 |
| CVE-2022-0001: Fix not seen in stream |
| CVE-2022-0002: Fix not seen in stream |
| CVE-2022-0168: Fix not seen in stream |
| CVE-2022-0330: Fixed with 4.4.301 |
| CVE-2022-0382: Fix not seen in stream |
| CVE-2022-0400: Fix unknown |
| CVE-2022-0480: Fix not seen in stream |
| CVE-2022-0487: Fix not seen in stream |
| CVE-2022-0492: Fix not seen in stream |
| CVE-2022-0494: Fix not seen in stream |
| CVE-2022-0617: Fixed with 4.4.302 |
| CVE-2022-0850: Fixed with 4.4.276 |
| CVE-2022-1011: Fix not seen in stream |
| CVE-2022-1012: Fix not seen in stream |
| CVE-2022-1016: Fix not seen in stream |
| CVE-2022-1048: Fix not seen in stream |
| CVE-2022-1116: Fix unknown |
| CVE-2022-1184: Fix not seen in stream |
| CVE-2022-1195: Fixed with 4.4.297 |
| CVE-2022-1198: Fix not seen in stream |
| CVE-2022-1199: Fix not seen in stream |
| CVE-2022-1204: Fix not seen in stream |
| CVE-2022-1247: Fix unknown |
| CVE-2022-1263: Fix not seen in stream |
| CVE-2022-1280: Fix not seen in stream |
| CVE-2022-1353: Fix not seen in stream |
| CVE-2022-1419: Fix not seen in stream |
| CVE-2022-1462: Fix not seen in stream |
| CVE-2022-1508: Fix not seen in stream |
| CVE-2022-1652: Fix not seen in stream |
| CVE-2022-1679: Fix not seen in stream |
| CVE-2022-1729: Fix not seen in stream |
| CVE-2022-1734: Fix not seen in stream |
| CVE-2022-1786: Fix not seen in stream |
| CVE-2022-1836: Fix not seen in stream |
| CVE-2022-1966: Fix not seen in stream |
| CVE-2022-1974: Fix not seen in stream |
| CVE-2022-1975: Fix not seen in stream |
| CVE-2022-20132: Fixed with 4.4.295 |
| CVE-2022-20141: Fixed with 4.4.284 |
| CVE-2022-20148: Fix not seen in stream |
| CVE-2022-20158: Fix not seen in stream |
| CVE-2022-20166: Fix not seen in stream |
| CVE-2022-20368: Fix not seen in stream |
| CVE-2022-20369: Fix not seen in stream |
| CVE-2022-20422: Fix not seen in stream |
| CVE-2022-20424: Fix not seen in stream |
| CVE-2022-20565: Fixed with 4.4.236 |
| CVE-2022-20566: Fix not seen in stream |
| CVE-2022-20572: Fix not seen in stream |
| CVE-2022-21123: Fix not seen in stream |
| CVE-2022-21125: Fix not seen in stream |
| CVE-2022-21166: Fix not seen in stream |
| CVE-2022-21385: Fix not seen in stream |
| CVE-2022-21499: Fix not seen in stream |
| CVE-2022-2153: Fix not seen in stream |
| CVE-2022-2209: Fix unknown |
| CVE-2022-23036: Fix not seen in stream |
| CVE-2022-23037: Fix not seen in stream |
| CVE-2022-23038: Fix not seen in stream |
| CVE-2022-23039: Fix not seen in stream |
| CVE-2022-23040: Fix not seen in stream |
| CVE-2022-23042: Fix not seen in stream |
| CVE-2022-2318: Fix not seen in stream |
| CVE-2022-23222: Fix not seen in stream |
| CVE-2022-2327: Fix not seen in stream |
| CVE-2022-2380: Fix not seen in stream |
| CVE-2022-23816: Fix not seen in stream |
| CVE-2022-23825: Fix unknown |
| CVE-2022-23960: Fix not seen in stream |
| CVE-2022-24448: Fix not seen in stream |
| CVE-2022-24958: Fix not seen in stream |
| CVE-2022-2503: Fix not seen in stream |
| CVE-2022-25258: Fix not seen in stream |
| CVE-2022-25265: Fix unknown |
| CVE-2022-25375: Fix not seen in stream |
| CVE-2022-2586: Fix not seen in stream |
| CVE-2022-2588: Fix not seen in stream |
| CVE-2022-26365: Fix not seen in stream |
| CVE-2022-26373: Fix not seen in stream |
| CVE-2022-26490: Fix not seen in stream |
| CVE-2022-2663: Fix not seen in stream |
| CVE-2022-26966: Fix not seen in stream |
| CVE-2022-27223: Fix not seen in stream |
| CVE-2022-27672: Fix not seen in stream |
| CVE-2022-28356: Fix not seen in stream |
| CVE-2022-28388: Fix not seen in stream |
| CVE-2022-28390: Fix not seen in stream |
| CVE-2022-2961: Fix unknown |
| CVE-2022-2964: Fix not seen in stream |
| CVE-2022-2978: Fix not seen in stream |
| CVE-2022-29900: Fix not seen in stream |
| CVE-2022-29901: Fix not seen in stream |
| CVE-2022-2991: Fix not seen in stream |
| CVE-2022-3028: Fix not seen in stream |
| CVE-2022-30594: Fix not seen in stream |
| CVE-2022-3061: Fix not seen in stream |
| CVE-2022-3111: Fix not seen in stream |
| CVE-2022-3169: Fix not seen in stream |
| CVE-2022-3202: Fix not seen in stream |
| CVE-2022-32250: Fix not seen in stream |
| CVE-2022-32296: Fix not seen in stream |
| CVE-2022-3239: Fix not seen in stream |
| CVE-2022-32981: Fix not seen in stream |
| CVE-2022-3303: Fix not seen in stream |
| CVE-2022-3344: Fix not seen in stream |
| CVE-2022-33740: Fix not seen in stream |
| CVE-2022-33741: Fix not seen in stream |
| CVE-2022-33742: Fix not seen in stream |
| CVE-2022-33744: Fix not seen in stream |
| CVE-2022-33981: Fix not seen in stream |
| CVE-2022-3424: Fix not seen in stream |
| CVE-2022-34918: Fix not seen in stream |
| CVE-2022-3522: Fix not seen in stream |
| CVE-2022-3523: Fix not seen in stream |
| CVE-2022-3524: Fix not seen in stream |
| CVE-2022-3533: Fix unknown |
| CVE-2022-3534: Fix not seen in stream |
| CVE-2022-3542: Fix not seen in stream |
| CVE-2022-3545: Fix not seen in stream |
| CVE-2022-3564: Fix not seen in stream |
| CVE-2022-3565: Fix not seen in stream |
| CVE-2022-3566: Fix not seen in stream |
| CVE-2022-3567: Fix not seen in stream |
| CVE-2022-3586: Fix not seen in stream |
| CVE-2022-3594: Fix not seen in stream |
| CVE-2022-3595: Fix not seen in stream |
| CVE-2022-3606: Fix unknown |
| CVE-2022-36123: Fix not seen in stream |
| CVE-2022-3621: Fix not seen in stream |
| CVE-2022-3624: Fix not seen in stream |
| CVE-2022-3628: Fix not seen in stream |
| CVE-2022-36280: Fix not seen in stream |
| CVE-2022-3629: Fix not seen in stream |
| CVE-2022-3635: Fix not seen in stream |
| CVE-2022-3636: Fix not seen in stream |
| CVE-2022-36402: Fix unknown |
| CVE-2022-3642: Fix unknown |
| CVE-2022-3643: Fix not seen in stream |
| CVE-2022-3646: Fix not seen in stream |
| CVE-2022-3649: Fix not seen in stream |
| CVE-2022-36879: Fix not seen in stream |
| CVE-2022-36946: Fix not seen in stream |
| CVE-2022-38096: Fix unknown |
| CVE-2022-3903: Fix not seen in stream |
| CVE-2022-39188: Fix not seen in stream |
| CVE-2022-39842: Fix not seen in stream |
| CVE-2022-40768: Fix not seen in stream |
| CVE-2022-4095: Fix not seen in stream |
| CVE-2022-40982: Fix not seen in stream |
| CVE-2022-41218: Fix not seen in stream |
| CVE-2022-41222: Fix not seen in stream |
| CVE-2022-4129: Fix not seen in stream |
| CVE-2022-41848: Fix unknown |
| CVE-2022-41849: Fix not seen in stream |
| CVE-2022-41850: Fix not seen in stream |
| CVE-2022-41858: Fix not seen in stream |
| CVE-2022-42703: Fix not seen in stream |
| CVE-2022-42895: Fix not seen in stream |
| CVE-2022-42896: Fix not seen in stream |
| CVE-2022-43750: Fix not seen in stream |
| CVE-2022-44032: Fix unknown |
| CVE-2022-44033: Fix unknown |
| CVE-2022-4543: Fix unknown |
| CVE-2022-45884: Fix unknown |
| CVE-2022-45885: Fix unknown |
| CVE-2022-45886: Fix unknown |
| CVE-2022-45887: Fix unknown |
| CVE-2022-45919: Fix unknown |
| CVE-2022-45934: Fix not seen in stream |
| CVE-2022-4662: Fix not seen in stream |
| CVE-2022-4744: Fix not seen in stream |
| CVE-2022-47520: Fix not seen in stream |
| CVE-2022-47929: Fix not seen in stream |
| CVE-2023-0030: Fix not seen in stream |
| CVE-2023-0047: Fix not seen in stream |
| CVE-2023-0160: Fix unknown |
| CVE-2023-0266: Fix not seen in stream |
| CVE-2023-0386: Fix not seen in stream |
| CVE-2023-0394: Fix not seen in stream |
| CVE-2023-0458: Fix not seen in stream |
| CVE-2023-0459: Fix not seen in stream |
| CVE-2023-0590: Fix not seen in stream |
| CVE-2023-0597: Fix not seen in stream |
| CVE-2023-0615: Fix not seen in stream |
| CVE-2023-1073: Fix not seen in stream |
| CVE-2023-1074: Fix not seen in stream |
| CVE-2023-1077: Fix not seen in stream |
| CVE-2023-1095: Fix not seen in stream |
| CVE-2023-1118: Fix not seen in stream |
| CVE-2023-1206: Fix not seen in stream |
| CVE-2023-1249: Fix not seen in stream |
| CVE-2023-1380: Fix not seen in stream |
| CVE-2023-1382: Fix not seen in stream |
| CVE-2023-1390: Fix not seen in stream |
| CVE-2023-1513: Fix not seen in stream |
| CVE-2023-1611: Fix not seen in stream |
| CVE-2023-1670: Fix not seen in stream |
| CVE-2023-1829: Fix not seen in stream |
| CVE-2023-1838: Fix not seen in stream |
| CVE-2023-1989: Fix not seen in stream |
| CVE-2023-1990: Fix not seen in stream |
| CVE-2023-2007: Fix not seen in stream |
| CVE-2023-20569: Fix not seen in stream |
| CVE-2023-20588: Fix not seen in stream |
| CVE-2023-20593: Fix not seen in stream |
| CVE-2023-20941: Fix unknown |
| CVE-2023-2124: Fix not seen in stream |
| CVE-2023-21264: Fix not seen in stream |
| CVE-2023-2162: Fix not seen in stream |
| CVE-2023-2176: Fix not seen in stream |
| CVE-2023-2194: Fix not seen in stream |
| CVE-2023-2248: Fix not seen in stream |
| CVE-2023-2269: Fix not seen in stream |
| CVE-2023-22995: Fix not seen in stream |
| CVE-2023-23039: Fix unknown |
| CVE-2023-23454: Fix not seen in stream |
| CVE-2023-23455: Fix not seen in stream |
| CVE-2023-23559: Fix not seen in stream |
| CVE-2023-2430: Fix not seen in stream |
| CVE-2023-2513: Fix not seen in stream |
| CVE-2023-26545: Fix not seen in stream |
| CVE-2023-26607: Fix not seen in stream |
| CVE-2023-28328: Fix not seen in stream |
| CVE-2023-28772: Fixed with 4.4.276 |
| CVE-2023-2985: Fix not seen in stream |
| CVE-2023-3006: Fix not seen in stream |
| CVE-2023-3022: Fix not seen in stream |
| CVE-2023-30456: Fix not seen in stream |
| CVE-2023-30772: Fix not seen in stream |
| CVE-2023-3090: Fix not seen in stream |
| CVE-2023-3106: Fixed with 4.4.223 |
| CVE-2023-31081: Fix unknown |
| CVE-2023-31082: Fix unknown |
| CVE-2023-31083: Fix unknown |
| CVE-2023-31084: Fix not seen in stream |
| CVE-2023-31085: Fix unknown |
| CVE-2023-3111: Fix not seen in stream |
| CVE-2023-3117: Fix not seen in stream |
| CVE-2023-3141: Fix not seen in stream |
| CVE-2023-31436: Fix not seen in stream |
| CVE-2023-3159: Fix not seen in stream |
| CVE-2023-3161: Fix not seen in stream |
| CVE-2023-3212: Fix not seen in stream |
| CVE-2023-32233: Fix not seen in stream |
| CVE-2023-32269: Fix not seen in stream |
| CVE-2023-3268: Fix not seen in stream |
| CVE-2023-33288: Fix not seen in stream |
| CVE-2023-3338: Fix not seen in stream |
| CVE-2023-3390: Fix not seen in stream |
| CVE-2023-3397: Fix unknown |
| CVE-2023-34255: Fix not seen in stream |
| CVE-2023-34256: Fix not seen in stream |
| CVE-2023-34319: Fix not seen in stream |
| CVE-2023-35001: Fix not seen in stream |
| CVE-2023-3567: Fix not seen in stream |
| CVE-2023-35824: Fix not seen in stream |
| CVE-2023-35827: Fix unknown |
| CVE-2023-3611: Fix not seen in stream |
| CVE-2023-3640: Fix unknown |
| CVE-2023-37453: Fix unknown |
| CVE-2023-37454: Fix unknown |
| CVE-2023-3772: Fix unknown |
| CVE-2023-3773: Fix unknown |
| CVE-2023-3776: Fix not seen in stream |
| CVE-2023-3863: Fix not seen in stream |
| CVE-2023-4010: Fix unknown |
| CVE-2023-4128: Fix not seen in stream |
| CVE-2023-4132: Fix not seen in stream |
| CVE-2023-4133: Fix not seen in stream |
| CVE-2023-4134: Fix not seen in stream |
| CVE-2023-4155: Fix not seen in stream |
| CVE-2023-4194: Fix not seen in stream |
| CVE-2023-4273: Fix not seen in stream |
