| CVE-2004-0230: Fixed with 3.2.37 |
| 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-4131: Fixed with 3.2.2 |
| CVE-2011-4916: Fix unknown |
| CVE-2011-4917: Fix unknown |
| CVE-2012-0957: Fixed with 3.2.33 |
| CVE-2012-2119: Fixed with 3.2.24 |
| CVE-2012-2136: Fixed with 3.2.23 |
| CVE-2012-2137: Fixed with 3.2.24 |
| CVE-2012-2313: Fixed with 3.2.19 |
| CVE-2012-2319: Fixed with 3.2.17 |
| CVE-2012-2372: Fixed with 3.2.55 |
| CVE-2012-2375: Fixed with 3.2.15 |
| CVE-2012-2390: Fixed with 3.2.20 |
| CVE-2012-2669: Fixed with 3.2.22 |
| CVE-2012-2745: Fixed with 3.2.15 |
| CVE-2012-3364: Fixed with 3.2.23 |
| CVE-2012-3400: Fixed with 3.2.23 |
| CVE-2012-3412: Fixed with 3.2.30 |
| CVE-2012-3430: Fixed with 3.2.31 |
| CVE-2012-3511: Fixed with 3.2.23 |
| CVE-2012-3520: Fixed with 3.2.30 |
| CVE-2012-4398: Fix not seen in stream |
| CVE-2012-4461: Fixed with 3.2.36 |
| CVE-2012-4508: Fixed with 3.2.33 |
| CVE-2012-4530: Fixed with 3.2.40 |
| CVE-2012-4542: Fix unknown |
| CVE-2012-4565: Fixed with 3.2.34 |
| CVE-2012-5374: Fix not seen in stream |
| CVE-2012-5375: Fix not seen in stream |
| CVE-2012-5517: Fixed with 3.2.41 |
| CVE-2012-6536: Fixed with 3.2.31 |
| CVE-2012-6537: Fixed with 3.2.31 |
| CVE-2012-6538: Fixed with 3.2.31 |
| CVE-2012-6539: Fixed with 3.2.30 |
| CVE-2012-6540: Fixed with 3.2.30 |
| CVE-2012-6541: Fixed with 3.2.30 |
| CVE-2012-6542: Fixed with 3.2.30 |
| CVE-2012-6544: Fixed with 3.2.30 |
| CVE-2012-6545: Fixed with 3.2.30 |
| CVE-2012-6546: Fixed with 3.2.30 |
| CVE-2012-6547: Fixed with 3.2.28 |
| CVE-2012-6548: Fixed with 3.2.42 |
| CVE-2012-6549: Fixed with 3.2.42 |
| CVE-2012-6638: Fixed with 3.2.24 |
| CVE-2012-6647: Fixed with 3.2.27 |
| CVE-2012-6657: Fixed with 3.2.31 |
| CVE-2012-6689: Fixed with 3.2.30 |
| CVE-2012-6701: Fixed with 3.2.19 |
| CVE-2012-6704: Fixed with 3.2.85 |
| CVE-2012-6712: Fix not seen in stream |
| CVE-2013-0160: Fixed with 3.2.45 |
| CVE-2013-0190: Fixed with 3.2.38 |
| CVE-2013-0216: Fixed with 3.2.39 |
| CVE-2013-0217: Fixed with 3.2.39 |
| CVE-2013-0228: Fixed with 3.2.39 |
| CVE-2013-0231: Fixed with 3.2.40 |
| CVE-2013-0268: Fixed with 3.2.38 |
| CVE-2013-0309: Fixed with 3.2.32 |
| CVE-2013-0310: Fixed with 3.2.28 |
| CVE-2013-0311: Fixed with 3.2.40 |
| CVE-2013-0313: Fixed with 3.2.38 |
| CVE-2013-0343: Fixed with 3.2.52 |
| CVE-2013-0349: Fixed with 3.2.38 |
| CVE-2013-0871: Fixed with 3.2.39 |
| CVE-2013-0913: Fixed with 3.2.42 |
| CVE-2013-0914: Fixed with 3.2.41 |
| CVE-2013-1059: Fixed with 3.2.49 |
| CVE-2013-1767: Fixed with 3.2.40 |
| CVE-2013-1772: Fix not seen in stream |
| CVE-2013-1773: Fixed with 3.2.41 |
| CVE-2013-1774: Fixed with 3.2.38 |
| CVE-2013-1792: Fixed with 3.2.41 |
| CVE-2013-1796: Fixed with 3.2.44 |
| CVE-2013-1797: Fixed with 3.2.44 |
| CVE-2013-1798: Fixed with 3.2.44 |
| CVE-2013-1819: Fix not seen in stream |
| CVE-2013-1826: Fixed with 3.2.31 |
| CVE-2013-1827: Fixed with 3.2.29 |
| CVE-2013-1848: Fixed with 3.2.41 |
| CVE-2013-1860: Fixed with 3.2.41 |
| CVE-2013-1928: Fixed with 3.2.33 |
| CVE-2013-1929: Fixed with 3.2.43 |
| CVE-2013-1956: Fix not seen in stream |
| CVE-2013-1979: Fixed with 3.2.44 |
| CVE-2013-2094: Fixed with 3.2.45 |
| CVE-2013-2140: Fix not seen in stream |
| CVE-2013-2141: Fixed with 3.2.44 |
| CVE-2013-2146: Fixed with 3.2.45 |
| CVE-2013-2147: Fixed with 3.2.52 |
| CVE-2013-2148: Fixed with 3.2.50 |
| CVE-2013-2164: Fixed with 3.2.49 |
| CVE-2013-2206: Fix not seen in stream |
| CVE-2013-2232: Fixed with 3.2.50 |
| CVE-2013-2234: Fixed with 3.2.50 |
| CVE-2013-2237: Fixed with 3.2.51 |
| CVE-2013-2546: Fixed with 3.2.41 |
| CVE-2013-2547: Fixed with 3.2.41 |
| CVE-2013-2548: Fixed with 3.2.41 |
| CVE-2013-2596: Fixed with 3.2.45 |
| CVE-2013-2634: Fixed with 3.2.42 |
| CVE-2013-2635: Fix not seen in stream |
| CVE-2013-2850: Fixed with 3.2.47 |
| CVE-2013-2851: Fixed with 3.2.49 |
| CVE-2013-2852: Fixed with 3.2.47 |
| CVE-2013-2888: Fixed with 3.2.52 |
| CVE-2013-2889: Fixed with 3.2.52 |
| CVE-2013-2892: Fixed with 3.2.52 |
| CVE-2013-2893: Fixed with 3.2.52 |
| CVE-2013-2895: Fixed with 3.2.52 |
| CVE-2013-2896: Fixed with 3.2.52 |
| CVE-2013-2899: Fixed with 3.2.52 |
| CVE-2013-2929: Fixed with 3.2.54 |
| CVE-2013-3076: Fixed with 3.2.45 |
| CVE-2013-3222: Fixed with 3.2.45 |
| CVE-2013-3223: Fixed with 3.2.45 |
| CVE-2013-3224: Fixed with 3.2.45 |
| CVE-2013-3225: Fix not seen in stream |
| CVE-2013-3227: Fix not seen in stream |
| CVE-2013-3228: Fix not seen in stream |
| CVE-2013-3229: Fix not seen in stream |
| CVE-2013-3231: Fix not seen in stream |
| CVE-2013-3232: Fixed with 3.2.45 |
| CVE-2013-3234: Fixed with 3.2.45 |
| CVE-2013-3235: Fix not seen in stream |
| CVE-2013-3301: Fixed with 3.2.44 |
| CVE-2013-4129: Fix not seen in stream |
| CVE-2013-4162: Fixed with 3.2.50 |
| CVE-2013-4254: Fix not seen in stream |
| CVE-2013-4299: Fixed with 3.2.53 |
| CVE-2013-4312: Fixed with 3.2.78 |
| CVE-2013-4345: Fixed with 3.2.54 |
| CVE-2013-4348: Fixed with 3.2.54 |
| CVE-2013-4350: Fixed with 3.2.52 |
| CVE-2013-4387: Fixed with 3.2.52 |
| CVE-2013-4470: Fixed with 3.2.53 |
| CVE-2013-4483: Fixed with 3.2.57 |
| CVE-2013-4511: Fixed with 3.2.53 |
| CVE-2013-4512: Fixed with 3.2.53 |
| CVE-2013-4514: Fixed with 3.2.53 |
| CVE-2013-4515: Fixed with 3.2.53 |
| CVE-2013-4579: Fixed with 3.2.55 |
| CVE-2013-4587: Fixed with 3.2.54 |
| CVE-2013-4592: Fixed with 3.2.54 |
| CVE-2013-6282: Fixed with 3.2.54 |
| CVE-2013-6367: Fixed with 3.2.54 |
| CVE-2013-6368: Fixed with 3.2.55 |
| CVE-2013-6378: Fixed with 3.2.54 |
| CVE-2013-6380: Fixed with 3.2.54 |
| CVE-2013-6381: Fixed with 3.2.54 |
| CVE-2013-6382: Fixed with 3.2.54 |
| CVE-2013-6383: Fixed with 3.2.53 |
| CVE-2013-6885: Fixed with 3.2.67 |
| CVE-2013-7027: Fixed with 3.2.53 |
| CVE-2013-7263: Fixed with 3.2.54 |
| CVE-2013-7264: Fixed with 3.2.54 |
| CVE-2013-7265: Fixed with 3.2.54 |
| CVE-2013-7266: Fixed with 3.2.54 |
| CVE-2013-7267: Fixed with 3.2.54 |
| CVE-2013-7268: Fixed with 3.2.54 |
| CVE-2013-7269: Fixed with 3.2.54 |
| CVE-2013-7270: Fixed with 3.2.54 |
| CVE-2013-7271: Fixed with 3.2.54 |
| CVE-2013-7281: Fixed with 3.2.54 |
| CVE-2013-7339: Fixed with 3.2.55 |
| CVE-2013-7348: Fix not seen in stream |
| CVE-2013-7421: Fixed with 3.2.67 |
| CVE-2013-7445: Fix unknown |
| CVE-2013-7446: Fixed with 3.2.75 |
| CVE-2013-7470: Fixed with 3.2.53 |
| CVE-2014-0055: Fixed with 3.2.58 |
| CVE-2014-0069: Fixed with 3.2.57 |
| CVE-2014-0077: Fixed with 3.2.58 |
| CVE-2014-0101: Fixed with 3.2.56 |
| CVE-2014-0131: Fixed with 3.2.61 |
| CVE-2014-0181: Fix not seen in stream |
| CVE-2014-0196: Fixed with 3.2.59 |
| CVE-2014-1438: Fixed with 3.2.55 |
| CVE-2014-1444: Fixed with 3.2.53 |
| CVE-2014-1445: Fixed with 3.2.53 |
| CVE-2014-1446: Fixed with 3.2.55 |
| CVE-2014-1737: Fixed with 3.2.59 |
| CVE-2014-1738: Fixed with 3.2.59 |
| CVE-2014-1739: Fixed with 3.2.60 |
| CVE-2014-1874: Fix not seen in stream |
| CVE-2014-2039: Fixed with 3.2.57 |
| CVE-2014-2309: Fixed with 3.2.58 |
| CVE-2014-2523: Fixed with 3.2.57 |
| CVE-2014-2672: Fixed with 3.2.56 |
| CVE-2014-2678: Fixed with 3.2.58 |
| CVE-2014-2706: Fixed with 3.2.56 |
| CVE-2014-2851: Fixed with 3.2.60 |
| CVE-2014-3122: Fixed with 3.2.58 |
| CVE-2014-3144: Fixed with 3.2.60 |
| CVE-2014-3145: Fixed with 3.2.60 |
| CVE-2014-3153: Fixed with 3.2.60 |
| CVE-2014-3180: Fix not seen in stream |
| CVE-2014-3181: Fixed with 3.2.63 |
| CVE-2014-3182: Fixed with 3.2.63 |
| CVE-2014-3184: Fixed with 3.2.63 |
| CVE-2014-3185: Fixed with 3.2.63 |
| CVE-2014-3186: Fixed with 3.2.63 |
| CVE-2014-3534: Fixed with 3.2.62 |
| CVE-2014-3601: Fixed with 3.2.63 |
| CVE-2014-3610: Fixed with 3.2.64 |
| CVE-2014-3611: Fixed with 3.2.64 |
| CVE-2014-3645: Fixed with 3.2.64 |
| CVE-2014-3646: Fixed with 3.2.64 |
| CVE-2014-3647: Fixed with 3.2.64 |
| CVE-2014-3673: Fixed with 3.2.64 |
| CVE-2014-3687: Fixed with 3.2.64 |
| CVE-2014-3688: Fixed with 3.2.64 |
| CVE-2014-3690: Fixed with 3.2.64 |
| CVE-2014-3917: Fixed with 3.2.61 |
| CVE-2014-4027: Fix not seen in stream |
| CVE-2014-4157: Fixed with 3.2.61 |
| CVE-2014-4171: Fixed with 3.2.62 |
| CVE-2014-4508: Fixed with 3.2.61 |
| CVE-2014-4608: Fixed with 3.2.65 |
| CVE-2014-4652: Fixed with 3.2.61 |
| CVE-2014-4653: Fixed with 3.2.61 |
| CVE-2014-4654: Fixed with 3.2.61 |
| CVE-2014-4655: Fixed with 3.2.61 |
| CVE-2014-4656: Fixed with 3.2.61 |
| CVE-2014-4667: Fixed with 3.2.61 |
| CVE-2014-4699: Fixed with 3.2.61 |
| CVE-2014-4943: Fix not seen in stream |
| CVE-2014-5077: Fixed with 3.2.63 |
| CVE-2014-5471: Fixed with 3.2.63 |
| CVE-2014-5472: Fixed with 3.2.63 |
| CVE-2014-6410: Fixed with 3.2.66 |
| CVE-2014-6416: Fixed with 3.2.64 |
| CVE-2014-6417: Fixed with 3.2.64 |
| CVE-2014-6418: Fixed with 3.2.64 |
| CVE-2014-7207: Fixed with 3.2.64 |
| CVE-2014-7822: Fixed with 3.2.67 |
| CVE-2014-7825: Fixed with 3.2.65 |
| CVE-2014-7826: Fixed with 3.2.65 |
| CVE-2014-7841: Fixed with 3.2.66 |
| CVE-2014-7842: Fixed with 3.2.66 |
| CVE-2014-7970: Fix not seen in stream |
| CVE-2014-7975: Fix not seen in stream |
| CVE-2014-8133: Fixed with 3.2.66 |
| CVE-2014-8134: Fixed with 3.2.66 |
| CVE-2014-8159: Fixed with 3.2.69 |
| CVE-2014-8160: Fixed with 3.2.67 |
| CVE-2014-8171: Fix not seen in stream |
| CVE-2014-8172: Fix not seen in stream |
| CVE-2014-8559: Fixed with 3.2.66 |
| CVE-2014-8709: Fixed with 3.2.56 |
| CVE-2014-8884: Fixed with 3.2.66 |
| CVE-2014-8989: Fix not seen in stream |
| CVE-2014-9090: Fixed with 3.2.65 |
| CVE-2014-9322: Fixed with 3.2.65 |
| CVE-2014-9419: Fixed with 3.2.67 |
| CVE-2014-9420: Fixed with 3.2.67 |
| CVE-2014-9529: Fixed with 3.2.67 |
| CVE-2014-9584: Fixed with 3.2.67 |
| CVE-2014-9585: Fixed with 3.2.67 |
| CVE-2014-9644: Fixed with 3.2.67 |
| CVE-2014-9683: Fixed with 3.2.67 |
| CVE-2014-9710: Fix not seen in stream |
| CVE-2014-9717: Fix not seen in stream |
| CVE-2014-9728: Fixed with 3.2.67 |
| CVE-2014-9729: Fixed with 3.2.67 |
| CVE-2014-9730: Fixed with 3.2.67 |
| CVE-2014-9731: Fixed with 3.2.67 |
| CVE-2014-9803: Fix not seen in stream |
| CVE-2014-9888: Fixed with 3.2.85 |
| CVE-2014-9895: Fixed with 3.2.85 |
| CVE-2014-9914: Fix not seen in stream |
| CVE-2014-9922: Fixed with 3.2.82 |
| CVE-2015-0239: Fixed with 3.2.67 |
| CVE-2015-1350: Fixed with 3.2.84 |
| CVE-2015-1420: Fixed with 3.2.70 |
| CVE-2015-1421: Fixed with 3.2.67 |
| CVE-2015-1593: Fixed with 3.2.69 |
| CVE-2015-1805: Fix not seen in stream |
| CVE-2015-2041: Fixed with 3.2.69 |
| CVE-2015-2042: Fixed with 3.2.69 |
| CVE-2015-2150: Fixed with 3.2.69 |
| CVE-2015-2830: Fixed with 3.2.69 |
| CVE-2015-2877: Fix unknown |
| CVE-2015-2922: Fixed with 3.2.69 |
| CVE-2015-2925: Fixed with 3.2.72 |
| CVE-2015-3212: Fixed with 3.2.70 |
| CVE-2015-3288: Fixed with 3.2.71 |
| CVE-2015-3290: Fix not seen in stream |
| CVE-2015-3331: Fixed with 3.2.69 |
| CVE-2015-3332: Fix not seen in stream |
| CVE-2015-3339: Fix not seen in stream |
| CVE-2015-3636: Fixed with 3.2.69 |
| CVE-2015-4167: Fixed with 3.2.69 |
| CVE-2015-4176: Fix not seen in stream |
| CVE-2015-4177: Fix not seen in stream |
| CVE-2015-4178: Fix not seen in stream |
| CVE-2015-4700: Fixed with 3.2.70 |
| CVE-2015-5156: Fixed with 3.2.72 |
| CVE-2015-5157: Fix not seen in stream |
| CVE-2015-5257: Fixed with 3.2.72 |
| CVE-2015-5307: Fixed with 3.2.73 |
| CVE-2015-5364: Fixed with 3.2.70 |
| CVE-2015-5366: Fixed with 3.2.70 |
| CVE-2015-5697: Fixed with 3.2.72 |
| CVE-2015-5707: Fixed with 3.2.70 |
| CVE-2015-6252: Fixed with 3.2.71 |
| CVE-2015-6526: Fixed with 3.2.70 |
| CVE-2015-6937: Fixed with 3.2.72 |
| CVE-2015-7509: Fixed with 3.2.66 |
| CVE-2015-7513: Fixed with 3.2.76 |
| CVE-2015-7515: Fixed with 3.2.79 |
| CVE-2015-7550: Fixed with 3.2.76 |
| CVE-2015-7566: Fixed with 3.2.78 |
| CVE-2015-7613: Fixed with 3.2.72 |
| CVE-2015-7799: Fixed with 3.2.75 |
| CVE-2015-7872: Fixed with 3.2.73 |
| CVE-2015-8019: Fixed with 3.2.73 |
| CVE-2015-8104: Fixed with 3.2.74 |
| CVE-2015-8215: Fixed with 3.2.72 |
| CVE-2015-8374: Fixed with 3.2.74 |
| CVE-2015-8543: Fixed with 3.2.75 |
| CVE-2015-8550: Fixed with 3.2.76 |
| CVE-2015-8551: Fixed with 3.2.76 |
| CVE-2015-8552: Fixed with 3.2.76 |
| CVE-2015-8553: Fixed with 3.2.76 |
| CVE-2015-8569: Fixed with 3.2.75 |
| CVE-2015-8575: Fixed with 3.2.75 |
| CVE-2015-8709: Fix not seen in stream |
| CVE-2015-8767: Fixed with 3.2.77 |
| CVE-2015-8785: Fixed with 3.2.75 |
| CVE-2015-8812: Fixed with 3.2.78 |
| CVE-2015-8816: Fixed with 3.2.76 |
| CVE-2015-8839: Fix not seen in stream |
| CVE-2015-8950: Fix not seen in stream |
| CVE-2015-8952: Fix not seen in stream |
| CVE-2015-8955: Fix not seen in stream |
| CVE-2015-8962: Fixed with 3.2.85 |
| CVE-2015-8963: Fixed with 3.2.85 |
| CVE-2015-8964: Fixed with 3.2.85 |
| CVE-2015-8966: Fix not seen in stream |
| CVE-2015-8967: Fix not seen in stream |
| CVE-2015-8970: Fixed with 3.2.77 |
| CVE-2015-9004: Fixed with 3.2.95 |
| CVE-2015-9016: Fix not seen in stream |
| CVE-2015-9289: Fixed with 3.2.71 |
| CVE-2016-0723: Fixed with 3.2.78 |
| CVE-2016-0821: Fixed with 3.2.79 |
| CVE-2016-0823: Fixed with 3.2.69 |
| CVE-2016-10044: Fix not seen in stream |
| CVE-2016-10088: Fixed with 3.2.85 |
| CVE-2016-10147: Fix not seen in stream |
| CVE-2016-10200: Fixed with 3.2.88 |
| CVE-2016-10229: Fixed with 3.2.76 |
| CVE-2016-10723: Fix not seen in stream |
| CVE-2016-10741: Fix not seen in stream |
| CVE-2016-1583: Fixed with 3.2.82 |
| CVE-2016-2069: Fixed with 3.2.77 |
| CVE-2016-2143: Fixed with 3.2.79 |
| CVE-2016-2184: Fixed with 3.2.80 |
| CVE-2016-2185: Fixed with 3.2.80 |
| CVE-2016-2186: Fixed with 3.2.80 |
| CVE-2016-2187: Fixed with 3.2.81 |
| CVE-2016-2188: Fixed with 3.2.89 |
| CVE-2016-2384: Fixed with 3.2.78 |
| CVE-2016-2543: Fixed with 3.2.77 |
| CVE-2016-2544: Fixed with 3.2.77 |
| CVE-2016-2545: Fixed with 3.2.77 |
| CVE-2016-2546: Fixed with 3.2.77 |
| CVE-2016-2547: Fixed with 3.2.77 |
| CVE-2016-2548: Fixed with 3.2.77 |
| CVE-2016-2549: Fixed with 3.2.77 |
| CVE-2016-2782: Fixed with 3.2.78 |
| CVE-2016-2847: Fixed with 3.2.78 |
| CVE-2016-3070: Fix not seen in stream |
| CVE-2016-3134: Fixed with 3.2.80 |
| CVE-2016-3136: Fixed with 3.2.80 |
| CVE-2016-3137: Fixed with 3.2.80 |
| CVE-2016-3138: Fixed with 3.2.80 |
| CVE-2016-3139: Fix not seen in stream |
| CVE-2016-3140: Fixed with 3.2.80 |
| CVE-2016-3156: Fixed with 3.2.80 |
| CVE-2016-3157: Fixed with 3.2.80 |
| CVE-2016-3672: Fixed with 3.2.80 |
| CVE-2016-3841: Fixed with 3.2.75 |
| CVE-2016-3857: Fixed with 3.2.84 |
| CVE-2016-3955: Fixed with 3.2.80 |
| CVE-2016-3961: Fixed with 3.2.81 |
| CVE-2016-4470: Fixed with 3.2.82 |
| CVE-2016-4482: Fixed with 3.2.82 |
| CVE-2016-4485: Fixed with 3.2.81 |
| CVE-2016-4486: Fixed with 3.2.81 |
| CVE-2016-4565: Fixed with 3.2.81 |
| CVE-2016-4569: Fixed with 3.2.82 |
| CVE-2016-4578: Fixed with 3.2.82 |
| CVE-2016-4580: Fixed with 3.2.81 |
| CVE-2016-4805: Fixed with 3.2.80 |
| CVE-2016-4913: Fixed with 3.2.81 |
| CVE-2016-4997: Fix not seen in stream |
| CVE-2016-4998: Fix not seen in stream |
| CVE-2016-5195: Fix not seen in stream |
| CVE-2016-5243: Fixed with 3.2.82 |
| CVE-2016-5244: Fixed with 3.2.82 |
| CVE-2016-5829: Fixed with 3.2.82 |
| CVE-2016-6136: Fixed with 3.2.82 |
| CVE-2016-6197: Fix not seen in stream |
| CVE-2016-6198: Fix not seen in stream |
| CVE-2016-6213: Fix not seen in stream |
| CVE-2016-6480: Fixed with 3.2.84 |
| CVE-2016-6786: Fixed with 3.2.85 |
| CVE-2016-6787: Fixed with 3.2.85 |
| CVE-2016-6828: Fixed with 3.2.84 |
| CVE-2016-7042: Fixed with 3.2.84 |
| CVE-2016-7097: Fixed with 3.2.84 |
| CVE-2016-7117: Fixed with 3.2.80 |
| CVE-2016-7425: Fixed with 3.2.84 |
| CVE-2016-7910: Fixed with 3.2.84 |
| CVE-2016-7911: Fixed with 3.2.85 |
| CVE-2016-7915: Fixed with 3.2.85 |
| CVE-2016-7916: Fixed with 3.2.81 |
| CVE-2016-7917: Fix not seen in stream |
| CVE-2016-8405: Fixed with 3.2.85 |
| CVE-2016-8632: Fixed with 3.2.85 |
| CVE-2016-8633: Fixed with 3.2.84 |
| CVE-2016-8645: Fixed with 3.2.85 |
| CVE-2016-8646: Fixed with 3.2.74 |
| CVE-2016-8655: Fixed with 3.2.85 |
| CVE-2016-9120: Fix not seen in stream |
| CVE-2016-9178: Fix not seen in stream |
| CVE-2016-9555: Fixed with 3.2.85 |
| CVE-2016-9588: Fixed with 3.2.86 |
| CVE-2016-9604: Fixed with 3.2.89 |
| CVE-2016-9644: Fix not seen in stream |
| CVE-2016-9685: Fixed with 3.2.80 |
| CVE-2016-9754: Fix not seen in stream |
| CVE-2016-9794: Fixed with 3.2.85 |
| CVE-2017-0605: Fixed with 3.2.89 |
| CVE-2017-0627: Fixed with 3.2.96 |
| CVE-2017-0786: Fix not seen in stream |
| CVE-2017-0861: Fixed with 3.2.100 |
| CVE-2017-1000: Fix not seen in stream |
| CVE-2017-1000111: Fixed with 3.2.92 |
| CVE-2017-1000112: Fix not seen in stream |
| CVE-2017-1000251: Fixed with 3.2.94 |
| CVE-2017-1000253: Fixed with 3.2.70 |
| CVE-2017-1000363: Fixed with 3.2.91 |
| CVE-2017-1000364: Fixed with 3.2.90 |
| CVE-2017-1000365: Fixed with 3.2.91 |
| CVE-2017-1000379: Fixed with 3.2.90 |
| CVE-2017-1000380: Fixed with 3.2.91 |
| CVE-2017-1000405: Fix not seen in stream |
| CVE-2017-1000407: Fixed with 3.2.97 |
| CVE-2017-10661: Fixed with 3.2.92 |
| CVE-2017-10662: Fix not seen in stream |
| CVE-2017-10663: Fix not seen in stream |
| CVE-2017-10810: Fix not seen in stream |
| CVE-2017-10911: Fixed with 3.2.91 |
| CVE-2017-11176: Fixed with 3.2.92 |
| CVE-2017-11472: Fix not seen in stream |
| CVE-2017-11473: Fixed with 3.2.95 |
| CVE-2017-11600: Fixed with 3.2.93 |
| CVE-2017-12134: Fixed with 3.2.93 |
| CVE-2017-12153: Fixed with 3.2.94 |
| CVE-2017-12154: Fixed with 3.2.94 |
| CVE-2017-12168: Fix not seen in stream |
| CVE-2017-12190: Fixed with 3.2.95 |
| CVE-2017-12762: Fix not seen in stream |
| CVE-2017-13080: Fixed with 3.2.95 |
| CVE-2017-13166: Fix not seen in stream |
| CVE-2017-13167: Fixed with 3.2.78 |
| CVE-2017-13168: Fix not seen in stream |
| CVE-2017-13215: Fixed with 3.2.77 |
| CVE-2017-13305: Fix not seen in stream |
| CVE-2017-13693: Fix unknown |
| CVE-2017-13694: Fix unknown |
| CVE-2017-13695: Fix not seen in stream |
| CVE-2017-14051: Fixed with 3.2.96 |
| CVE-2017-14106: Fixed with 3.2.93 |
| CVE-2017-14140: Fixed with 3.2.93 |
| CVE-2017-14156: Fixed with 3.2.94 |
| CVE-2017-14340: Fixed with 3.2.94 |
| CVE-2017-14489: Fixed with 3.2.94 |
| CVE-2017-14991: Fix not seen in stream |
| CVE-2017-15102: Fixed with 3.2.85 |
| CVE-2017-15115: Fixed with 3.2.96 |
| CVE-2017-15116: Fix not seen in stream |
| CVE-2017-15121: Fix not seen in stream |
| CVE-2017-15265: Fixed with 3.2.95 |
| CVE-2017-15274: Fixed with 3.2.93 |
| CVE-2017-15299: Fixed with 3.2.95 |
| CVE-2017-15537: Fix not seen in stream |
| CVE-2017-15649: Fixed with 3.2.95 |
| CVE-2017-15868: Fixed with 3.2.97 |
| CVE-2017-16525: Fixed with 3.2.96 |
| CVE-2017-16526: Fixed with 3.2.97 |
| CVE-2017-16527: Fixed with 3.2.95 |
| CVE-2017-16528: Fix not seen in stream |
| CVE-2017-16529: Fixed with 3.2.95 |
| CVE-2017-16531: Fixed with 3.2.95 |
| CVE-2017-16532: Fixed with 3.2.95 |
| CVE-2017-16533: Fixed with 3.2.95 |
| CVE-2017-16535: Fixed with 3.2.95 |
| CVE-2017-16536: Fixed with 3.2.96 |
| CVE-2017-16537: Fixed with 3.2.96 |
| CVE-2017-16643: Fixed with 3.2.96 |
| CVE-2017-16646: Fix not seen in stream |
| CVE-2017-16648: Fix not seen in stream |
| CVE-2017-16649: Fixed with 3.2.96 |
| CVE-2017-16911: Fixed with 3.2.99 |
| CVE-2017-16912: Fixed with 3.2.99 |
| CVE-2017-16913: Fixed with 3.2.99 |
| CVE-2017-16914: Fixed with 3.2.99 |
| CVE-2017-16939: Fixed with 3.2.97 |
| CVE-2017-16995: Fix not seen in stream |
| CVE-2017-17450: Fix not seen in stream |
| CVE-2017-17558: Fixed with 3.2.97 |
| CVE-2017-17741: Fixed with 3.2.97 |
| CVE-2017-17805: Fixed with 3.2.97 |
| CVE-2017-17806: Fixed with 3.2.97 |
| CVE-2017-17807: Fixed with 3.2.97 |
| CVE-2017-18017: Fixed with 3.2.99 |
| CVE-2017-18079: Fixed with 3.2.94 |
| CVE-2017-18193: Fix not seen in stream |
| CVE-2017-18203: Fixed with 3.2.99 |
| CVE-2017-18204: Fix not seen in stream |
| CVE-2017-18208: Fixed with 3.2.102 |
| CVE-2017-18216: Fixed with 3.2.102 |
| CVE-2017-18241: Fix not seen in stream |
| CVE-2017-18249: Fix not seen in stream |
| CVE-2017-18255: Fix not seen in stream |
| CVE-2017-18270: Fixed with 3.2.97 |
| CVE-2017-18360: Fixed with 3.2.93 |
| CVE-2017-18509: Fix not seen in stream |
| CVE-2017-18551: Fixed with 3.2.100 |
| CVE-2017-18552: Fix not seen in stream |
| CVE-2017-2636: Fixed with 3.2.87 |
| CVE-2017-2647: Fixed with 3.2.91 |
| CVE-2017-2671: Fixed with 3.2.89 |
| CVE-2017-5549: Fixed with 3.2.86 |
| CVE-2017-5551: Fix not seen in stream |
| CVE-2017-5669: Fixed with 3.2.87 |
| CVE-2017-5715: Fix not seen in stream |
| CVE-2017-5753: Fix not seen in stream |
| CVE-2017-5754: Fix not seen in stream |
| CVE-2017-5967: Fix not seen in stream |
| CVE-2017-5970: Fixed with 3.2.88 |
| CVE-2017-5972: Fix not seen in stream |
| CVE-2017-5986: Fixed with 3.2.87 |
| CVE-2017-6001: Fixed with 3.2.85 |
| CVE-2017-6074: Fixed with 3.2.86 |
| CVE-2017-6214: Fixed with 3.2.86 |
| CVE-2017-6346: Fixed with 3.2.87 |
| CVE-2017-6348: Fixed with 3.2.87 |
| CVE-2017-6353: Fixed with 3.2.87 |
| CVE-2017-6951: Fixed with 3.2.91 |
| CVE-2017-7184: Fixed with 3.2.89 |
| CVE-2017-7261: Fixed with 3.2.89 |
| CVE-2017-7273: Fixed with 3.2.87 |
| CVE-2017-7294: Fixed with 3.2.89 |
| CVE-2017-7308: Fixed with 3.2.89 |
| CVE-2017-7472: Fixed with 3.2.89 |
| CVE-2017-7482: Fixed with 3.2.90 |
| CVE-2017-7487: Fixed with 3.2.89 |
| CVE-2017-7518: Fix not seen in stream |
| CVE-2017-7542: Fixed with 3.2.92 |
| CVE-2017-7616: Fixed with 3.2.89 |
| CVE-2017-7618: Fixed with 3.2.89 |
| CVE-2017-7645: Fixed with 3.2.89 |
| CVE-2017-7889: Fixed with 3.2.91 |
| CVE-2017-7895: Fixed with 3.2.89 |
| CVE-2017-8065: Fix not seen in stream |
| CVE-2017-8797: Fix not seen in stream |
| CVE-2017-8824: Fixed with 3.2.97 |
| CVE-2017-8831: Fixed with 3.2.94 |
| CVE-2017-8890: Fixed with 3.2.89 |
| CVE-2017-8924: Fixed with 3.2.89 |
| CVE-2017-8925: Fixed with 3.2.89 |
| CVE-2017-9074: Fixed with 3.2.89 |
| CVE-2017-9075: Fixed with 3.2.89 |
| CVE-2017-9076: Fixed with 3.2.89 |
| CVE-2017-9077: Fixed with 3.2.89 |
| CVE-2017-9242: Fixed with 3.2.89 |
| CVE-2017-9725: Fix not seen in stream |
| CVE-2017-9984: Fix not seen in stream |
| CVE-2017-9985: Fix not seen in stream |
| CVE-2017-9986: Fix not seen in stream |
| CVE-2018-1000004: Fixed with 3.2.99 |
| CVE-2018-1000026: Fix not seen in stream |
| CVE-2018-1000028: Fixed with 3.2.100 |
| CVE-2018-1000199: Fixed with 3.2.102 |
| CVE-2018-1000204: Fix not seen in stream |
| CVE-2018-10021: Fix not seen in stream |
| CVE-2018-10087: Fix not seen in stream |
| CVE-2018-10124: Fix not seen in stream |
| CVE-2018-10322: Fix not seen in stream |
| CVE-2018-10323: Fix not seen in stream |
| CVE-2018-1066: Fix not seen in stream |
| CVE-2018-10675: Fixed with 3.2.95 |
| CVE-2018-1068: Fixed with 3.2.102 |
| CVE-2018-1087: Fix not seen in stream |
| CVE-2018-10876: Fix not seen in stream |
| CVE-2018-10877: Fix not seen in stream |
| CVE-2018-10878: Fix not seen in stream |
| CVE-2018-10879: Fix not seen in stream |
| CVE-2018-10880: Fix not seen in stream |
| CVE-2018-10881: Fix not seen in stream |
| CVE-2018-10882: Fix not seen in stream |
| CVE-2018-10883: Fix not seen in stream |
| CVE-2018-10902: Fix not seen in stream |
| CVE-2018-1092: Fixed with 3.2.102 |
| CVE-2018-1093: Fixed with 3.2.102 |
| CVE-2018-10940: Fixed with 3.2.102 |
| CVE-2018-1120: Fix not seen in stream |
| 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 3.2.102 |
| 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: Fix not seen in stream |
| CVE-2018-12896: Fix not seen in stream |
| CVE-2018-12928: Fix unknown |
| CVE-2018-12929: Fix unknown |
| CVE-2018-12930: Fix unknown |
| CVE-2018-12931: Fix unknown |
| CVE-2018-13053: Fix not seen in stream |
| CVE-2018-13093: Fix not seen in stream |
| CVE-2018-13094: Fix not seen in stream |
| CVE-2018-13095: Fix not seen in stream |
| CVE-2018-13405: Fix not seen in stream |
| CVE-2018-13406: Fix not seen in stream |
| CVE-2018-14609: Fix not seen in stream |
| CVE-2018-14610: Fix not seen in stream |
| CVE-2018-14611: Fix not seen in stream |
| CVE-2018-14612: Fix not seen in stream |
| CVE-2018-14613: Fix not seen in stream |
| CVE-2018-14614: Fix not seen in stream |
| CVE-2018-14616: Fix not seen in stream |
| CVE-2018-14617: Fix not seen in stream |
| CVE-2018-14633: Fix not seen in stream |
| CVE-2018-14634: Fix not seen in stream |
| CVE-2018-14734: Fix not seen in stream |
| CVE-2018-15572: Fix not seen in stream |
| CVE-2018-16276: Fix not seen in stream |
| CVE-2018-16658: Fix not seen in stream |
| CVE-2018-17972: Fix not seen in stream |
| CVE-2018-17977: Fix unknown |
| CVE-2018-18281: Fix not seen in stream |
| CVE-2018-18386: Fixed with 3.2.100 |
| CVE-2018-18690: Fix not seen in stream |
| CVE-2018-18710: Fix not seen in stream |
| CVE-2018-19824: Fix not seen in stream |
| CVE-2018-19985: Fix not seen in stream |
| CVE-2018-20169: Fix not seen in stream |
| CVE-2018-20509: Fix not seen in stream |
| CVE-2018-20510: Fix not seen in stream |
| CVE-2018-20511: Fix not seen in stream |
| CVE-2018-20836: Fix not seen in stream |
| CVE-2018-20854: Fix not seen in stream |
| CVE-2018-20976: Fix not seen in stream |
| CVE-2018-21008: Fix not seen in stream |
| CVE-2018-25020: Fix not seen in stream |
| CVE-2018-3620: Fix not seen in stream |
| CVE-2018-3639: Fix not seen in stream |
| CVE-2018-3646: Fix not seen in stream |
| CVE-2018-3665: Fix not seen in stream |
| CVE-2018-3693: Fix not seen in stream |
| CVE-2018-5332: Fixed with 3.2.99 |
| CVE-2018-5333: Fixed with 3.2.99 |
| CVE-2018-5344: Fix not seen in stream |
| CVE-2018-5750: Fixed with 3.2.100 |
| CVE-2018-5803: Fixed with 3.2.102 |
| CVE-2018-5814: Fix not seen in stream |
| CVE-2018-5848: Fix not seen in stream |
| CVE-2018-5953: Fix not seen in stream |
| CVE-2018-5995: Fix not seen in stream |
| CVE-2018-6412: Fixed with 3.2.102 |
| CVE-2018-6554: Fix not seen in stream |
| CVE-2018-6555: Fix not seen in stream |
| CVE-2018-6927: Fixed with 3.2.100 |
| CVE-2018-7273: Fix not seen in stream |
| CVE-2018-7480: Fix not seen in stream |
| CVE-2018-7492: Fixed with 3.2.100 |
| CVE-2018-7566: Fixed with 3.2.102 |
| CVE-2018-7755: Fix not seen in stream |
| CVE-2018-7757: Fixed with 3.2.102 |
| CVE-2018-7995: Fixed with 3.2.102 |
| CVE-2018-8822: Fixed with 3.2.102 |
| CVE-2018-8897: Fixed with 3.2.102 |
| CVE-2018-9422: Fix not seen in stream |
| CVE-2018-9465: Fix not seen in stream |
| CVE-2018-9516: Fix not seen in stream |
| CVE-2018-9517: Fixed with 3.2.96 |
| CVE-2018-9568: Fix not seen in stream |
| CVE-2019-0136: Fix not seen in stream |
| CVE-2019-0154: Fix not seen in stream |
| CVE-2019-10126: Fix not seen in stream |
| CVE-2019-10142: Fix not seen in stream |
| CVE-2019-10207: Fix not seen in stream |
| CVE-2019-10220: Fix not seen in stream |
| CVE-2019-10638: Fix not seen in stream |
| CVE-2019-10639: Fix not seen in stream |
| CVE-2019-11091: Fix not seen in stream |
| CVE-2019-11135: Fix not seen in stream |
| CVE-2019-11190: Fix not seen in stream |
| CVE-2019-11191: Fix not seen in stream |
| CVE-2019-1125: Fix not seen in stream |
| CVE-2019-11477: Fix not seen in stream |
| CVE-2019-11478: Fix not seen in stream |
| CVE-2019-11479: Fix not seen in stream |
| CVE-2019-11486: Fix not seen in stream |
| CVE-2019-11487: Fix not seen in stream |
| CVE-2019-11599: Fix not seen in stream |
| CVE-2019-11810: Fix not seen in stream |
| CVE-2019-11833: Fix not seen in stream |
| CVE-2019-11884: Fix not seen in stream |
| CVE-2019-12378: Fix not seen in stream |
| CVE-2019-12379: Fix not seen in stream |
| CVE-2019-12381: Fix not seen in stream |
| CVE-2019-12382: Fix not seen in stream |
| CVE-2019-12614: Fix not seen in stream |
| CVE-2019-12615: Fix not seen in stream |
| CVE-2019-12818: Fix not seen in stream |
| CVE-2019-12881: Fix not seen in stream |
| CVE-2019-13272: Fix not seen in stream |
| CVE-2019-13631: Fix not seen in stream |
| CVE-2019-14283: Fix not seen in stream |
| CVE-2019-14284: Fix not seen in stream |
| CVE-2019-14615: Fix not seen in stream |
| CVE-2019-14821: Fix not seen in stream |
| CVE-2019-14835: Fix not seen in stream |
| CVE-2019-14895: Fix not seen in stream |
| CVE-2019-14896: Fix not seen in stream |
| CVE-2019-14897: Fix not seen in stream |
| CVE-2019-14901: Fix not seen in stream |
| CVE-2019-15117: Fix not seen in stream |
| CVE-2019-15118: Fix not seen in stream |
| CVE-2019-15212: Fix not seen in stream |
| CVE-2019-15214: Fix not seen in stream |
| CVE-2019-15216: Fix not seen in stream |
| CVE-2019-15217: Fix not seen in stream |
| CVE-2019-15219: Fix not seen in stream |
| CVE-2019-15221: Fix not seen in stream |
| CVE-2019-15222: Fix not seen in stream |
| CVE-2019-15223: Fix not seen in stream |
| CVE-2019-15239: Fix not seen in stream |
| CVE-2019-15290: Fix unknown |
| CVE-2019-15291: Fix not seen in stream |
| CVE-2019-15292: Fix not seen in stream |
| CVE-2019-15505: Fix not seen in stream |
| CVE-2019-15807: Fix not seen in stream |
| CVE-2019-15902: Fix not seen in stream |
| CVE-2019-15916: Fix not seen in stream |
| CVE-2019-15917: Fix not seen in stream |
| CVE-2019-15926: Fix not seen in stream |
| CVE-2019-15927: Fix not seen in stream |
| CVE-2019-16232: Fix not seen in stream |
| CVE-2019-16233: Fix not seen in stream |
| CVE-2019-16413: Fix not seen in stream |
| CVE-2019-16746: Fix not seen in stream |
| CVE-2019-16921: Fix not seen in stream |
| CVE-2019-17052: Fix not seen in stream |
| CVE-2019-17053: Fix not seen in stream |
| CVE-2019-17054: Fix not seen in stream |
| CVE-2019-17055: Fix not seen in stream |
| CVE-2019-17075: Fix not seen in stream |
| CVE-2019-17133: Fix not seen in stream |
| CVE-2019-17351: Fix not seen in stream |
| CVE-2019-18660: Fix not seen in stream |
| CVE-2019-18675: Fix not seen in stream |
| CVE-2019-18680: Fix not seen in stream |
| CVE-2019-18806: Fix not seen in stream |
| 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-19054: Fix not seen in stream |
| CVE-2019-19062: Fix not seen in stream |
| CVE-2019-19066: Fix not seen in stream |
| CVE-2019-19073: Fix not seen in stream |
| CVE-2019-19074: Fix not seen in stream |
| CVE-2019-19227: Fix not seen in stream |
| CVE-2019-19241: Fix not seen in stream |
| CVE-2019-19319: Fix not seen in stream |
| CVE-2019-19377: Fix not seen in stream |
| CVE-2019-19447: Fix not seen in stream |
| CVE-2019-19448: Fix not seen in stream |
| CVE-2019-19449: Fix not seen in stream |
| CVE-2019-19523: Fix not seen in stream |
| CVE-2019-19524: Fix not seen in stream |
| CVE-2019-19527: Fix not seen in stream |
| CVE-2019-19528: Fix not seen in stream |
| CVE-2019-19531: Fix not seen in stream |
| CVE-2019-19532: Fix not seen in stream |
| CVE-2019-19533: Fix not seen in stream |
| CVE-2019-19537: Fix not seen in stream |
| CVE-2019-19768: Fix not seen in stream |
| CVE-2019-19813: Fix not seen in stream |
| CVE-2019-19814: Fix unknown |
| CVE-2019-19816: Fix not seen in stream |
| CVE-2019-19922: Fix not seen in stream |
| CVE-2019-19927: Fix not seen in stream |
| CVE-2019-19965: Fix not seen in stream |
| CVE-2019-19966: Fix not seen in stream |
| CVE-2019-1999: Fix not seen in stream |
| CVE-2019-20096: Fix not seen in stream |
| CVE-2019-2025: Fix not seen in stream |
| CVE-2019-2054: Fix not seen in stream |
| CVE-2019-20636: Fix not seen in stream |
| CVE-2019-20794: Fix unknown |
| CVE-2019-20806: Fix not seen in stream |
| CVE-2019-20811: Fix not seen in stream |
| CVE-2019-20812: Fix not seen in stream |
| CVE-2019-20908: Fix not seen in stream |
| CVE-2019-2101: Fix not seen in stream |
| CVE-2019-2181: Fix not seen in stream |
| CVE-2019-2213: Fix not seen in stream |
| CVE-2019-2215: Fix not seen in stream |
| CVE-2019-3459: Fix not seen in stream |
| CVE-2019-3460: Fix not seen in stream |
| CVE-2019-3701: Fix not seen in stream |
| CVE-2019-3837: Fix not seen in stream |
| CVE-2019-3846: Fix not seen in stream |
| CVE-2019-3874: Fix not seen in stream |
| CVE-2019-3892: Fix not seen in stream |
| CVE-2019-3901: Fix not seen in stream |
| CVE-2019-5108: Fix not seen in stream |
| CVE-2019-5489: Fix not seen in stream |
| CVE-2019-6133: Fix not seen in stream |
| CVE-2019-7222: Fix not seen in stream |
| CVE-2019-7308: Fix not seen in stream |
| CVE-2019-9213: Fix not seen in stream |
| CVE-2019-9454: Fixed with 3.2.100 |
| CVE-2019-9456: Fixed with 3.2.102 |
| CVE-2019-9457: Fix not seen in stream |
| CVE-2019-9458: Fix not seen in stream |
| CVE-2019-9466: Fix not seen in stream |
| CVE-2019-9503: Fix not seen in stream |
| CVE-2019-9506: Fix not seen in stream |
| CVE-2020-0030: Fix not seen in stream |
| CVE-2020-0066: Fix not seen in stream |
| CVE-2020-0255: Fix not seen in stream |
| CVE-2020-0305: Fix not seen in stream |
| CVE-2020-0347: Fix unknown |
| CVE-2020-0404: Fix not seen in stream |
| CVE-2020-0427: Fix not seen in stream |
| CVE-2020-0429: Fix not seen in stream |
| CVE-2020-0431: Fix not seen in stream |
| CVE-2020-0432: Fix not seen in stream |
| CVE-2020-0433: Fix not seen in stream |
| CVE-2020-0435: Fix not seen in stream |
| CVE-2020-0465: Fix not seen in stream |
| CVE-2020-0466: Fix not seen in stream |
| CVE-2020-0543: Fix not seen in stream |
| CVE-2020-10135: Fix not seen in stream |
| CVE-2020-10690: Fix not seen in stream |
| CVE-2020-10708: Fix unknown |
| CVE-2020-10732: Fix not seen in stream |
| CVE-2020-10742: Fix not seen in stream |
| CVE-2020-10751: Fix not seen in stream |
| CVE-2020-10766: Fix not seen in stream |
| CVE-2020-10767: Fix not seen in stream |
| CVE-2020-10768: Fix not seen in stream |
| CVE-2020-10769: Fix not seen in stream |
| CVE-2020-10773: Fix not seen in stream |
| CVE-2020-10942: Fix not seen in stream |
| CVE-2020-11494: Fix not seen in stream |
| CVE-2020-11565: Fix not seen in stream |
| CVE-2020-11608: Fix not seen in stream |
| CVE-2020-11609: Fix not seen in stream |
| CVE-2020-11668: Fix not seen in stream |
| CVE-2020-11669: Fix not seen in stream |
| 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: Fix not seen in stream |
| CVE-2020-12652: Fix not seen in stream |
| CVE-2020-12653: Fix not seen in stream |
| CVE-2020-12654: Fix not seen in stream |
| CVE-2020-12655: Fix not seen in stream |
| CVE-2020-12656: Fix not seen in stream |
| CVE-2020-12769: Fix not seen in stream |
| CVE-2020-12770: Fix not seen in stream |
| CVE-2020-12826: Fix not seen in stream |
| CVE-2020-12888: Fix not seen in stream |
| CVE-2020-13974: Fix not seen in stream |
| CVE-2020-14304: Fix unknown |
| CVE-2020-14314: Fix not seen in stream |
| CVE-2020-14331: Fix not seen in stream |
| CVE-2020-14353: Fixed with 3.2.97 |
| CVE-2020-14381: Fix not seen in stream |
| CVE-2020-14390: Fix not seen in stream |
| CVE-2020-14416: Fix not seen in stream |
| CVE-2020-15393: Fix not seen in stream |
| CVE-2020-15436: Fix not seen in stream |
| CVE-2020-15437: Fix not seen in stream |
| CVE-2020-15802: Fix unknown |
| CVE-2020-16120: Fix not seen in stream |
| CVE-2020-16166: Fix not seen in stream |
| CVE-2020-1749: Fix not seen in stream |
| CVE-2020-24502: Fix unknown |
| CVE-2020-24503: Fix unknown |
| CVE-2020-24586: Fix not seen in stream |
| CVE-2020-24587: Fix not seen in stream |
| CVE-2020-24588: Fix not seen in stream |
| CVE-2020-25211: Fix not seen in stream |
| CVE-2020-25284: Fix not seen in stream |
| CVE-2020-25285: Fix not seen in stream |
| CVE-2020-25643: Fix not seen in stream |
| CVE-2020-25656: Fix not seen in stream |
| CVE-2020-25668: Fix not seen in stream |
| CVE-2020-25669: Fix not seen in stream |
| CVE-2020-26139: Fix not seen in stream |
| 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: Fix not seen in stream |
| CVE-2020-26541: Fix not seen in stream |
| CVE-2020-26555: Fix not seen in stream |
| CVE-2020-26556: Fix unknown |
| CVE-2020-26557: Fix unknown |
| CVE-2020-26558: Fix not seen in stream |
| CVE-2020-26559: Fix unknown |
| CVE-2020-26560: Fix unknown |
| CVE-2020-27066: Fix not seen in stream |
| CVE-2020-27067: Fixed with 3.2.97 |
| CVE-2020-27068: Fix not seen in stream |
| CVE-2020-2732: Fix not seen in stream |
| CVE-2020-27673: Fix not seen in stream |
| CVE-2020-27675: Fix not seen in stream |
| CVE-2020-27777: Fix not seen in stream |
| CVE-2020-27786: Fix not seen in stream |
| CVE-2020-27815: Fix not seen in stream |
| CVE-2020-27820: Fix not seen in stream |
| CVE-2020-28097: Fix not seen in stream |
| CVE-2020-28915: Fix not seen in stream |
| CVE-2020-28974: Fix not seen in stream |
| CVE-2020-29371: Fix not seen in stream |
| CVE-2020-29374: Fix not seen in stream |
| CVE-2020-29568: Fix not seen in stream |
| CVE-2020-29660: Fix not seen in stream |
| CVE-2020-29661: Fix not seen in stream |
| CVE-2020-35501: Fix unknown |
| CVE-2020-35519: Fix not seen in stream |
| CVE-2020-36158: Fix not seen in stream |
| 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: Fix not seen in stream |
| CVE-2020-36558: Fix not seen in stream |
| CVE-2020-3702: Fix not seen in stream |
| CVE-2020-4788: Fix not seen in stream |
| CVE-2020-8647: Fix not seen in stream |
| CVE-2020-8648: Fix not seen in stream |
| CVE-2020-8649: Fix not seen in stream |
| CVE-2020-8832: Fix not seen in stream |
| CVE-2020-9383: Fix not seen in stream |
| CVE-2021-0129: Fix not seen in stream |
| CVE-2021-0399: Fix unknown |
| CVE-2021-0447: Fixed with 3.2.99 |
| CVE-2021-0448: Fix not seen in stream |
| CVE-2021-0512: Fix not seen in stream |
| CVE-2021-0920: Fix not seen in stream |
| CVE-2021-0929: Fix not seen in stream |
| CVE-2021-0937: Fix not seen in stream |
| CVE-2021-0941: Fix not seen in stream |
| CVE-2021-1048: Fix not seen in stream |
| CVE-2021-20261: Fix not seen in stream |
| CVE-2021-20265: Fixed with 3.2.78 |
| CVE-2021-20292: Fix not seen in stream |
| CVE-2021-20317: Fix not seen in stream |
| CVE-2021-20321: Fix not seen in stream |
| CVE-2021-21781: Fix not seen in stream |
| CVE-2021-22543: Fix not seen in stream |
| CVE-2021-22555: Fix not seen in stream |
| CVE-2021-26401: Fix not seen in stream |
| CVE-2021-26930: Fix not seen in stream |
| CVE-2021-26931: Fix not seen in stream |
| CVE-2021-26932: Fix not seen in stream |
| CVE-2021-27363: Fix not seen in stream |
| CVE-2021-27364: Fix not seen in stream |
| CVE-2021-27365: Fix not seen in stream |
| CVE-2021-28038: Fix not seen in stream |
| CVE-2021-28688: Fix not seen in stream |
| CVE-2021-28711: Fix not seen in stream |
| CVE-2021-28712: Fix not seen in stream |
| CVE-2021-28713: Fix not seen in stream |
| CVE-2021-28972: Fix not seen in stream |
| CVE-2021-29154: Fix not seen in stream |
| CVE-2021-29155: Fix not seen in stream |
| CVE-2021-29265: Fix not seen in stream |
| CVE-2021-29650: Fix not seen in stream |
| CVE-2021-30002: Fix not seen in stream |
| CVE-2021-3178: Fix not seen in stream |
| CVE-2021-31916: Fix not seen in stream |
| CVE-2021-32078: Fix not seen in stream |
| CVE-2021-32399: Fix not seen in stream |
| CVE-2021-33034: Fix not seen in stream |
| CVE-2021-33061: Fix not seen in stream |
| CVE-2021-33655: Fix not seen in stream |
| CVE-2021-33656: Fix not seen in stream |
| CVE-2021-34556: Fix not seen in stream |
| CVE-2021-34693: Fix not seen in stream |
| CVE-2021-3483: Fix not seen in stream |
| CVE-2021-34981: Fix not seen in stream |
| CVE-2021-3506: Fix not seen in stream |
| CVE-2021-3542: Fix unknown |
| CVE-2021-35477: Fix not seen in stream |
| CVE-2021-3564: Fix not seen in stream |
| CVE-2021-3573: Fix not seen in stream |
| CVE-2021-3609: Fix not seen in stream |
| CVE-2021-3612: Fix not seen in stream |
| CVE-2021-3640: Fix not seen in stream |
| CVE-2021-3653: Fix not seen in stream |
| CVE-2021-3655: Fix not seen in stream |
| CVE-2021-3659: Fix not seen in stream |
| CVE-2021-3669: Fix not seen in stream |
| CVE-2021-3679: Fix not seen in stream |
| CVE-2021-3714: Fix unknown |
| CVE-2021-37159: Fix not seen in stream |
| CVE-2021-3752: Fix not seen in stream |
| CVE-2021-3753: Fix not seen in stream |
| CVE-2021-3772: Fix not seen in stream |
| CVE-2021-38160: Fix not seen in stream |
| CVE-2021-38198: Fix not seen in stream |
| CVE-2021-38205: Fix not seen in stream |
| CVE-2021-3847: Fix unknown |
| CVE-2021-3864: Fix unknown |
| CVE-2021-3892: Fix unknown |
| CVE-2021-3896: Fix not seen in stream |
| CVE-2021-39634: Fix not seen in stream |
| CVE-2021-39636: Fix not seen in stream |
| CVE-2021-39648: Fix not seen in stream |
| CVE-2021-39685: Fix not seen in stream |
| CVE-2021-39686: Fix not seen in stream |
| CVE-2021-39698: Fix not seen in stream |
| CVE-2021-39800: Fix unknown |
| CVE-2021-39801: Fix unknown |
| CVE-2021-4023: Fix not seen in stream |
| CVE-2021-4037: Fix not seen in stream |
| CVE-2021-4083: Fix not seen in stream |
| CVE-2021-4149: Fix not seen in stream |
| CVE-2021-4150: Fix not seen in stream |
| CVE-2021-4155: Fix not seen in stream |
| CVE-2021-4159: Fix not seen in stream |
| CVE-2021-42008: Fix not seen in stream |
| CVE-2021-4202: Fix not seen in stream |
| CVE-2021-4203: Fix not seen in stream |
| CVE-2021-4218: Fix not seen in stream |
| CVE-2021-42739: Fix not seen in stream |
| CVE-2021-43389: Fix not seen in stream |
| CVE-2021-43975: Fix not seen in stream |
| CVE-2021-43976: Fix not seen in stream |
| CVE-2021-44879: Fix not seen in stream |
| CVE-2021-45095: Fix not seen in stream |
| CVE-2021-45485: Fix not seen in stream |
| CVE-2021-45868: Fix not seen in stream |
| 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: Fix not seen in stream |
| CVE-2022-0382: Fix not seen in stream |
| CVE-2022-0400: Fix unknown |
| CVE-2022-0480: Fix not seen in stream |
| CVE-2022-0492: Fix not seen in stream |
| CVE-2022-0494: Fix not seen in stream |
| CVE-2022-0850: Fix not seen in stream |
| CVE-2022-1011: Fix not seen in stream |
| CVE-2022-1012: 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: Fix not seen in stream |
| 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-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-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-20132: Fix not seen in stream |
| CVE-2022-20141: Fix not seen in stream |
| 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-20424: Fix not seen in stream |
| CVE-2022-20565: Fix not seen in stream |
| CVE-2022-20566: 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-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-24958: Fix not seen in stream |
| CVE-2022-25265: Fix unknown |
| CVE-2022-25375: 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-2663: Fix not seen in stream |
| CVE-2022-27672: Fix not seen in stream |
| CVE-2022-28356: Fix not seen in stream |
| CVE-2022-28390: Fix not seen in stream |
| CVE-2022-2961: Fix unknown |
| 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-3028: 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-32296: 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-3522: Fix not seen in stream |
| CVE-2022-3523: Fix not seen in stream |
| CVE-2022-3524: Fix not seen in stream |
| CVE-2022-3534: Fix not seen in stream |
| CVE-2022-3545: 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-3595: Fix not seen in stream |
| 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-36280: 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-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-38457: Fix not seen in stream |
| 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-40133: Fix not seen in stream |
| CVE-2022-40768: Fix not seen in stream |
| CVE-2022-4095: 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-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-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-0590: Fix not seen in stream |
| CVE-2023-0597: Fix not seen in stream |
| CVE-2023-0615: Fix unknown |
| CVE-2023-1074: Fix not seen in stream |
| CVE-2023-1077: Fix not seen in stream |
| CVE-2023-1118: Fix not seen in stream |
| CVE-2023-1380: Fix unknown |
| CVE-2023-1513: Fix not seen in stream |
| CVE-2023-20937: Fix unknown |
| 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-26607: Fix not seen in stream |
| CVE-2023-28328: Fix not seen in stream |
| CVE-2023-28772: Fix not seen in stream |
