diff --git a/templates-checksum.txt b/templates-checksum.txt index a941443048..c9dfaae2d0 100644 --- a/templates-checksum.txt +++ b/templates-checksum.txt @@ -654,707 +654,707 @@ http/credential-stuffing/self-hosted/gitlab-login-check-self-hosted.yaml:a74d469 http/credential-stuffing/self-hosted/grafana-login-check.yaml:8f5793e273b313b8fdc6ef9a28efef7786fe4802 http/credential-stuffing/self-hosted/jira-login-check.yaml:cccab91229b3c826d50f35b9d6b3a52755417602 http/cves/2000/CVE-2000-0114.yaml:d782d17292821e74335f4f75b936464cf598a3ea -http/cves/2001/CVE-2001-0537.yaml:4cbe8a8098fac93c94873e361baf14494de79096 -http/cves/2002/CVE-2002-1131.yaml:4a658f900bcef0a234f3c59f78061aa638b2d0a6 -http/cves/2004/CVE-2004-0519.yaml:65ac157809afae3e2fb659a7c919dc005b66b21f -http/cves/2004/CVE-2004-1965.yaml:c972294e1a933c9f531ff5c66183407c8826ea6a -http/cves/2005/CVE-2005-2428.yaml:0c3245f0e0b308d308f597c68ffd0ddaecafbb2c -http/cves/2005/CVE-2005-3344.yaml:9281c0183172e0207ea9af61fa4741319de4f115 -http/cves/2005/CVE-2005-3634.yaml:378a71429143e7b79d58c8a277863b56a6d1b28a -http/cves/2005/CVE-2005-4385.yaml:bb108d9dbd83c32fb27363c425692794a8f40780 -http/cves/2006/CVE-2006-1681.yaml:2fa1e8ef6287621456cfc4177ae8bc23c11c906f -http/cves/2006/CVE-2006-2842.yaml:bde5cb5ca63e4bc7f0c507d736ba4c62441f70e7 -http/cves/2007/CVE-2007-0885.yaml:69e943ee27a367bce66074a43eba0e1a0e593a2d +http/cves/2001/CVE-2001-0537.yaml:0e2533abcda8816e0623227fbaa03815e5557b0a +http/cves/2002/CVE-2002-1131.yaml:92baae5f46a813b39b092586bcd666671a64c4d5 +http/cves/2004/CVE-2004-0519.yaml:74dbfc16255346e35d9467d8100be7d505df4c9a +http/cves/2004/CVE-2004-1965.yaml:aad00ebd25dd3dbb0bd6d3a89b4334c19bd94b7a +http/cves/2005/CVE-2005-2428.yaml:e63ce8813a803e81e28f48264924ed7b53820cd8 +http/cves/2005/CVE-2005-3344.yaml:f6c8b54fe6b72603548b2674cbb0e79036977c45 +http/cves/2005/CVE-2005-3634.yaml:9395f794b0706b18fc639d892a71f44c1dba8e90 +http/cves/2005/CVE-2005-4385.yaml:3f2df8b3a11b56b520ce7fd4ce1a765f5c9d81f4 +http/cves/2006/CVE-2006-1681.yaml:a5a87f1fab0c252c8322c876c42c8ecfc0f3cc70 +http/cves/2006/CVE-2006-2842.yaml:9310a711d121f3d7d1383795d7d50af97a8f2640 +http/cves/2007/CVE-2007-0885.yaml:b1ede1a60ec71b5298a080211b47f34fc97b9e52 http/cves/2007/CVE-2007-4504.yaml:39b440699eb7201e1a6131b17ab17c937831122a -http/cves/2007/CVE-2007-4556.yaml:1744799b9c3b68123e75049ecfde1fc957d4c97d -http/cves/2007/CVE-2007-5728.yaml:b69194d4d02f86a275866aa5706a4f5b776e7fb8 -http/cves/2008/CVE-2008-1059.yaml:9ccebbd2c866952626146195dcd5bbe4eff103d2 -http/cves/2008/CVE-2008-1061.yaml:87ee71bce000275bed336383c6979614caf70559 -http/cves/2008/CVE-2008-1547.yaml:ebcbf35be8546ba43a76a3feee3fc217295d250f -http/cves/2008/CVE-2008-2398.yaml:b4af0b3d52cb56a6cbac523c1c0384ba7d4b924f -http/cves/2008/CVE-2008-2650.yaml:055fba5566002829c71d1dc25c560c4d0b66abde -http/cves/2008/CVE-2008-4668.yaml:fb12120d5046143bcf642be693de262bae1eb050 -http/cves/2008/CVE-2008-4764.yaml:ffa8ef2b4e1869d5e2aea20d77b9fe2f7e27c99b -http/cves/2008/CVE-2008-5587.yaml:3d7fa72c59adb64c3f09ce9e2830549e18e7ebed -http/cves/2008/CVE-2008-6080.yaml:0300d15a18769498b00eece98271f0f2c3184fcf -http/cves/2008/CVE-2008-6172.yaml:d4f61c8e955483b9cf2c76271598e791d04375f5 -http/cves/2008/CVE-2008-6222.yaml:9036e8e5755818e8490958062a7c1988d0b40791 -http/cves/2008/CVE-2008-6465.yaml:8de0e2cf47c716844e0a39b7c90aea91bb56b744 -http/cves/2008/CVE-2008-6668.yaml:807b29f2da4db008291def0ab33d60914652801d -http/cves/2008/CVE-2008-6982.yaml:dd5f37219e18a078e7da1a9e400c2e2a5cc0d3e4 -http/cves/2008/CVE-2008-7269.yaml:53f402d7bcd6a674ea59a287c8d94074e82467cb -http/cves/2009/CVE-2009-0347.yaml:fcdfbc15c87f7594b25b1b77c26eaffba7733456 +http/cves/2007/CVE-2007-4556.yaml:93945fb8db8ac1603c4df7510501c5baa6b1e484 +http/cves/2007/CVE-2007-5728.yaml:975f3ba784973dca4c56d50134c387b73f0e47f0 +http/cves/2008/CVE-2008-1059.yaml:2efef50c94bb78daf97cf8bf62eebda8cdd97a33 +http/cves/2008/CVE-2008-1061.yaml:9af3f70824a78b872c0e888f4cea0f4e2a9e29c6 +http/cves/2008/CVE-2008-1547.yaml:7c8b829154fee41c49a135b7d9806a3611c4445e +http/cves/2008/CVE-2008-2398.yaml:9075facaf0bc2a4835ca360c0167726f4213fb10 +http/cves/2008/CVE-2008-2650.yaml:7a374eae56679beaccff9b98a270d60b79de17c8 +http/cves/2008/CVE-2008-4668.yaml:1152e56e1445b8e67c8e87688c9f748ffa509643 +http/cves/2008/CVE-2008-4764.yaml:c189d86922c18bedac505e867567e0c53a19cca2 +http/cves/2008/CVE-2008-5587.yaml:f3b951c26faa481de14288240ab7c1f1338f282e +http/cves/2008/CVE-2008-6080.yaml:67fd00e908c1b69ae8a7c4c70f77aad4c7810315 +http/cves/2008/CVE-2008-6172.yaml:c62eee1712909a9dd4de27e82e2d572d9f7e572b +http/cves/2008/CVE-2008-6222.yaml:cbe0920b67af2a4a1aca7649d4d51172090e46a7 +http/cves/2008/CVE-2008-6465.yaml:fa8648bfad9ef8c644e1f7ece9b9ba58e8a1845f +http/cves/2008/CVE-2008-6668.yaml:5dac36be065f5189b1375420040c3c603ac1d5cd +http/cves/2008/CVE-2008-6982.yaml:3fa8951241cecc57ee6e9813123e681f45604ccb +http/cves/2008/CVE-2008-7269.yaml:83377a28db84efee857e7f5f3c38cbefa0f08db7 +http/cves/2009/CVE-2009-0347.yaml:5c92dad4e21812986dd8b2dc4e9b7f54051f79bc http/cves/2009/CVE-2009-0545.yaml:0f315849754aca8103724e75e8110c538fa76ebc -http/cves/2009/CVE-2009-0932.yaml:84377f727cf5fbdba9cca41129b19deabbfab3a7 -http/cves/2009/CVE-2009-1151.yaml:0de78bdb25fe6626f75a9220e1fb57b0ceffd401 -http/cves/2009/CVE-2009-1496.yaml:72115b123bb4223aa66713debdca8b3a4aeebfd0 -http/cves/2009/CVE-2009-1558.yaml:e0eafad076bf4aa8b9a9f73fdd4516cc5bdfe260 +http/cves/2009/CVE-2009-0932.yaml:a9f759e9e5d46d1040b6b88f55f6c05f364859f6 +http/cves/2009/CVE-2009-1151.yaml:44a3451dbcf6b68a5339acf6d67ff99f0cd29162 +http/cves/2009/CVE-2009-1496.yaml:6d5cf54775ae71dc61085ae6494c6d049f05f73c +http/cves/2009/CVE-2009-1558.yaml:05f84e7c817424dbbfed2421419a27773ed96816 http/cves/2009/CVE-2009-1872.yaml:8d9c05ce4110639ab65ff25df1740966658671fc -http/cves/2009/CVE-2009-2015.yaml:c17e4c61224ab40feba89313d47d20d82fb4ef15 +http/cves/2009/CVE-2009-2015.yaml:581f6e873968f115fb2058f9ec2f03e70f9cbf49 http/cves/2009/CVE-2009-2100.yaml:5298440281009f835d592c2c9182679324418228 -http/cves/2009/CVE-2009-3053.yaml:48861682ae725b805be09b89570c8f9dbcc1134c -http/cves/2009/CVE-2009-3318.yaml:4fe7dba3bef72f9bf6014a43103bcc1c024e48cf -http/cves/2009/CVE-2009-4202.yaml:d2feedb274d3d92b0afb8e7167d1c558972608a9 -http/cves/2009/CVE-2009-4223.yaml:96178f3fab7b1486625105b2aa0137790b436cb3 -http/cves/2009/CVE-2009-4679.yaml:f34071656219ccc6aef52d9cc74db724fe33199c -http/cves/2009/CVE-2009-5020.yaml:5097c67df8685b2ac32878b27e516f0076f4395e -http/cves/2009/CVE-2009-5114.yaml:82207be1777726c0c72c4e14b80d0ec29124c150 -http/cves/2010/CVE-2010-0157.yaml:5ae2703977b821a655d71691328a2e3fa2a75d61 +http/cves/2009/CVE-2009-3053.yaml:d1a513cfaa667ad55f37a69ca4efe497dbe4a8f0 +http/cves/2009/CVE-2009-3318.yaml:4cf7dad51bb407cac194098f6aa696c59b6eb69b +http/cves/2009/CVE-2009-4202.yaml:84b1fe606b25a28c1804aca89b0c6d07f8870ced +http/cves/2009/CVE-2009-4223.yaml:b949ed494482077a5b3e94b77323a2dcfc37998a +http/cves/2009/CVE-2009-4679.yaml:47e3e919a864f1b0446448f14d13e7395d27cc84 +http/cves/2009/CVE-2009-5020.yaml:e92cb108efe53e64302f371503e17095933750b0 +http/cves/2009/CVE-2009-5114.yaml:2d1ca540dd3b133034fa7488d21fb23bbee482d6 +http/cves/2010/CVE-2010-0157.yaml:47d34f5e72951896371e0820e11a92d386e00d07 http/cves/2010/CVE-2010-0219.yaml:b4cf82b9f0270950ad0e462e04a5d944a0c3fdf6 -http/cves/2010/CVE-2010-0467.yaml:f346bc2752eeb03daf8bde21cb852f0ed60615dd -http/cves/2010/CVE-2010-0696.yaml:9d95653f0ffda596f217e93a9a556c82dfa0e66d -http/cves/2010/CVE-2010-0759.yaml:780c7c3d39218ebb97dc7d90a013db906a6d6897 -http/cves/2010/CVE-2010-0942.yaml:449ef5827e3946a5ad5096a66319a8c8af08f70f -http/cves/2010/CVE-2010-0943.yaml:83e64b0d12048e6d0eb13fe3ff624f88351ea61a -http/cves/2010/CVE-2010-0944.yaml:9b93d4652b5c34c81ad6b5beed0a9d5a95314ac3 -http/cves/2010/CVE-2010-0972.yaml:17c3c376fb84227ce74826965d89a0880f189dd7 -http/cves/2010/CVE-2010-0982.yaml:e9847fc6c363995788cbc3e5d5048ca2d1f5b1bd -http/cves/2010/CVE-2010-0985.yaml:7cd7468fedfbdf65362842d1dcbb2ba2a7de8e71 -http/cves/2010/CVE-2010-1056.yaml:cc28d3541fb0043bd2d932e106f8c7c97796af83 +http/cves/2010/CVE-2010-0467.yaml:e3593a8fb4a422a94f2bb2bae3d8b83ba97550b8 +http/cves/2010/CVE-2010-0696.yaml:971cda54e774fae7ac71e75038fff67bda3aa652 +http/cves/2010/CVE-2010-0759.yaml:0769c81415e66d77b7e9ba0888aa3a4ff3ea6052 +http/cves/2010/CVE-2010-0942.yaml:5ae943a2757b7b12e84941254a488540968c8ccb +http/cves/2010/CVE-2010-0943.yaml:8ef35cc492352b532f640fb5bcad3c11f19ea52d +http/cves/2010/CVE-2010-0944.yaml:20f1835ac1de202b65f48ce7528deb1f56c855f9 +http/cves/2010/CVE-2010-0972.yaml:10a0be310ed00e8ea455622b23c4b9d7437d120d +http/cves/2010/CVE-2010-0982.yaml:baf043547a7764b2c7c68b8a65f65fd0f124705b +http/cves/2010/CVE-2010-0985.yaml:beb046786d064fbab1f21d88646001d698d61578 +http/cves/2010/CVE-2010-1056.yaml:a0c4148fba6519914d6088774518040d076d9256 http/cves/2010/CVE-2010-1081.yaml:1d651ed87b995eabc072b585c2bdfe4f1ca01cb6 -http/cves/2010/CVE-2010-1217.yaml:06862a0ea9386ce8ba17d08e1a5f1b5c17cef55f -http/cves/2010/CVE-2010-1219.yaml:1924cfa6c7529e098589a491fc90eedca1fe1738 -http/cves/2010/CVE-2010-1302.yaml:0bcb7b943d1cdf4906743573915a423e6068602f -http/cves/2010/CVE-2010-1304.yaml:5dcc6c4e736987f2fb5ff6791f5da9d45fea082c -http/cves/2010/CVE-2010-1305.yaml:2a51ad12efbb96940976488ea7551e820974b64c -http/cves/2010/CVE-2010-1306.yaml:5955864582f6db8fcf4acee475bb836d532c03dd -http/cves/2010/CVE-2010-1307.yaml:6fded50d06a301080d06299964eb1520398c9231 +http/cves/2010/CVE-2010-1217.yaml:43994ad04e9d36205365237f7bba29086724a70d +http/cves/2010/CVE-2010-1219.yaml:e3a69a363966b00434340d96631d1ed8b23494c4 +http/cves/2010/CVE-2010-1302.yaml:6ebc89b02aa1b31048f76a85af9b0b94efecb695 +http/cves/2010/CVE-2010-1304.yaml:57d985b54a5a9344e3301556f2f70e13849734a1 +http/cves/2010/CVE-2010-1305.yaml:b861a4ebca9f1554b6049ac3c9540d433793b2d5 +http/cves/2010/CVE-2010-1306.yaml:a207c99b62bcd6f598522a42c44dce586cc3ff7a +http/cves/2010/CVE-2010-1307.yaml:513f4d47c1a9586dd4850f63fa894745439ea597 http/cves/2010/CVE-2010-1308.yaml:4aa4c05a0373fd776a677ecbe7cac8bd993e26bb -http/cves/2010/CVE-2010-1312.yaml:a433b00b1e556ca375c370722977c1c405be124a -http/cves/2010/CVE-2010-1313.yaml:798e793df9e639a286253b0838942e8d83c4cc1e -http/cves/2010/CVE-2010-1314.yaml:f395c33c5a26149ab23fabee62bb86abc78ab9e5 -http/cves/2010/CVE-2010-1315.yaml:b203505d244c79ec13500044e3922abfda7e843b -http/cves/2010/CVE-2010-1340.yaml:934444ec1c22ad51dc6ff94e77d05897b56afd32 -http/cves/2010/CVE-2010-1345.yaml:28d008a51082f3a779d511bdd31625af91c00a7b -http/cves/2010/CVE-2010-1352.yaml:d9d31ca1a7593a4a6d849a958621f77f22b1effc -http/cves/2010/CVE-2010-1353.yaml:961ed5c72501e5626760aa33d28559034b79b3d8 -http/cves/2010/CVE-2010-1354.yaml:b573947baa8a433bfd1c1c50138d1290dd98a889 -http/cves/2010/CVE-2010-1429.yaml:bfc2e77328a162babb97eb2264967b87bc90a4a5 -http/cves/2010/CVE-2010-1461.yaml:6183088ebab1c2fa22812c342607ca26bd21997c -http/cves/2010/CVE-2010-1469.yaml:a36342fadf0393926cb8548d0c5de3c2e1cd2dc2 -http/cves/2010/CVE-2010-1470.yaml:0bd4d189e5a3933663ad32f590689151e0d487f1 +http/cves/2010/CVE-2010-1312.yaml:5039c6739a05a3b7bec99e268628aa819062d6f3 +http/cves/2010/CVE-2010-1313.yaml:ce82c609cddfd91baf0c2f8eb4a99d5e4fd43c10 +http/cves/2010/CVE-2010-1314.yaml:67fa9997dbc71cc88ae047e83bf2ab9b4a3ca0a1 +http/cves/2010/CVE-2010-1315.yaml:3e84c5e57b9f817fe087accec46e428da2f4d7e6 +http/cves/2010/CVE-2010-1340.yaml:8e37f79891d748caf5f86ef14e05ee5bf3db1f48 +http/cves/2010/CVE-2010-1345.yaml:75b9c87e48b15257378cd979021d657041e58682 +http/cves/2010/CVE-2010-1352.yaml:c7b08979314ed2055d00f43380bed729ac96b87f +http/cves/2010/CVE-2010-1353.yaml:af75350a79c5832679ddfe782c0cef180df2db0f +http/cves/2010/CVE-2010-1354.yaml:aed0557a2e5a038abc3c2bcaa0502ab7f24a040b +http/cves/2010/CVE-2010-1429.yaml:50eb2ae5c7527edb4811aa3b87da43b8b222721c +http/cves/2010/CVE-2010-1461.yaml:93d12db11681f5c4469d18aba7988ee1ff0c213b +http/cves/2010/CVE-2010-1469.yaml:70b46529136a59440fbdb76d1e455b4cc865481e +http/cves/2010/CVE-2010-1470.yaml:29dfafa30f359a379ec32a1915b38180c5ddb069 http/cves/2010/CVE-2010-1471.yaml:7a08324c63c22bab844901b3ce5a6341c655fc10 http/cves/2010/CVE-2010-1472.yaml:b156d65d4fe4c7bfcf0a30ccfcac7745a65dcba6 -http/cves/2010/CVE-2010-1473.yaml:b00a00bf07109c6c9071d523a5a3a98e6da11a4c -http/cves/2010/CVE-2010-1474.yaml:564ff3fa2a4bbe44bbe375b9756747418959ccbf -http/cves/2010/CVE-2010-1475.yaml:9faf4dc43def1904f88491947cba2e599ddabc41 -http/cves/2010/CVE-2010-1476.yaml:8c41013316a4385833d6b0d5ec6b93b35f79efff -http/cves/2010/CVE-2010-1478.yaml:fbf9551c6f5354ef0423a256d55811a0c050d65e -http/cves/2010/CVE-2010-1491.yaml:c3d845b1666bf2110fe889941611ce4bd3665359 -http/cves/2010/CVE-2010-1494.yaml:8c11361b2b80b9a401aef817da785851e196a635 -http/cves/2010/CVE-2010-1495.yaml:b2e15a570aca9d8a7f3df1c15b6dcba50002d990 -http/cves/2010/CVE-2010-1531.yaml:bab6bc29bad8a0126643bdc61998142ad9e26777 -http/cves/2010/CVE-2010-1532.yaml:3b570531e203e7296cef82055329228683fbb20a -http/cves/2010/CVE-2010-1533.yaml:3c7c933393f28a46e32421cde9107cb22172c887 -http/cves/2010/CVE-2010-1534.yaml:6610fdf5ab42fa083362f6cca5ff06a35c8e6e89 -http/cves/2010/CVE-2010-1535.yaml:a59608a5132a1abbac463c26164195ed1ab7ca14 -http/cves/2010/CVE-2010-1540.yaml:76b58f2bcc370aa92b36811d241a27256d7f9997 -http/cves/2010/CVE-2010-1586.yaml:331dfb6b1d08dcef939388bbd3d7d8fe122068e1 -http/cves/2010/CVE-2010-1601.yaml:9b7523797ac9995705f69e65aeca05fe66ef99d3 -http/cves/2010/CVE-2010-1602.yaml:eb38fd5b5ac2ea46add1df90861e9f3bb5b546fc -http/cves/2010/CVE-2010-1603.yaml:4f6442526cf2b18fc047d00077fff43992dd0982 -http/cves/2010/CVE-2010-1607.yaml:1cfaab320ecab7613ac185a37ec3d187559073db -http/cves/2010/CVE-2010-1653.yaml:501c88bd452c14fe99464fc652b6bf46a6662389 -http/cves/2010/CVE-2010-1657.yaml:56ace1dd66fba57e86ae6aeb277eeb94469a39f1 -http/cves/2010/CVE-2010-1658.yaml:2935942271c586fd3d7968e72be9db8925c8456b -http/cves/2010/CVE-2010-1659.yaml:82694e212e98736ba27075487e475b7cccb8a951 -http/cves/2010/CVE-2010-1714.yaml:d7b409ca0f333e49789793cabec37600b13e12f6 -http/cves/2010/CVE-2010-1715.yaml:135882e9b31f70c09f33a18d45c230903d84b0cd -http/cves/2010/CVE-2010-1717.yaml:ba2fe8be8ebe8c56392b09229e9229664ed952a6 -http/cves/2010/CVE-2010-1718.yaml:56ad2b38b6b099eb3652d99ce6c49b0134f02b01 -http/cves/2010/CVE-2010-1719.yaml:0a47f1f40f89b9f5619b30582e6fc6000912471d -http/cves/2010/CVE-2010-1722.yaml:28e54393a6d007463feb9cb140da9ddbd207520c -http/cves/2010/CVE-2010-1723.yaml:9e0ea4bba22fdd04c7440a8c6071059dee1a8f62 -http/cves/2010/CVE-2010-1858.yaml:9c453926128e5276164b93740b3d8fddee468603 -http/cves/2010/CVE-2010-1870.yaml:1d6b4fe5c27bc64fcaf05378a58cce36f14aa1c8 -http/cves/2010/CVE-2010-1875.yaml:60d4c4127ed456e57bff03aaa1e4761cb3fc68d5 -http/cves/2010/CVE-2010-1878.yaml:e8815e976f3a85e740847af59b19c7aa96be15be -http/cves/2010/CVE-2010-1952.yaml:679aa3acd82cf9c4102dd8870808bcd9f0fc29bb +http/cves/2010/CVE-2010-1473.yaml:ff6d678ff12dfe0a800b6689ed874b27b43bf2cc +http/cves/2010/CVE-2010-1474.yaml:03e34fe0f50b4f85516da9e8841c993fb32df945 +http/cves/2010/CVE-2010-1475.yaml:0a832bea5658cade85a71a51747a2490aba5bd30 +http/cves/2010/CVE-2010-1476.yaml:25786db2ccb1194e5fa81f38b4a59a909d3ff006 +http/cves/2010/CVE-2010-1478.yaml:71d8fd309ed444f8a402abd5d527c69195dd48ec +http/cves/2010/CVE-2010-1491.yaml:50022e180e8e630ad668eaaa19967885ee471b9a +http/cves/2010/CVE-2010-1494.yaml:54e4c59a25c61e0d16032a6cd4693c9a709c0082 +http/cves/2010/CVE-2010-1495.yaml:7702b89d3dcc73b6de4378d28ae0692cd6f0f353 +http/cves/2010/CVE-2010-1531.yaml:2c20eb361e3685ab6311f3bab1900320de1a2971 +http/cves/2010/CVE-2010-1532.yaml:a9eb5ba8cf1ab8161ffbe0a4fdbacc94e357aa9a +http/cves/2010/CVE-2010-1533.yaml:3b16bd8765a6a034020ae7deebb932d9f1d20ce1 +http/cves/2010/CVE-2010-1534.yaml:d9cdf4fcbbc0f13abfb9d016e5de1639e3eb5620 +http/cves/2010/CVE-2010-1535.yaml:5b5fbe4edad31883cd50105edb138cf298148701 +http/cves/2010/CVE-2010-1540.yaml:f1e3c493b3ca21f66c5c0dce7454ada60a1319b2 +http/cves/2010/CVE-2010-1586.yaml:2a95b21bf667e6c340dbeb9d8856ca9f2de2270b +http/cves/2010/CVE-2010-1601.yaml:09f9af111cd6c4277f8abb060704fd66d1d5cc51 +http/cves/2010/CVE-2010-1602.yaml:c60e60bd4499acff5fd4b0a4c2c82d7efb5141ef +http/cves/2010/CVE-2010-1603.yaml:780d356781a7ae445cbbebbeb7f6a177ba785ead +http/cves/2010/CVE-2010-1607.yaml:07face9789d281646e799a49b453428cd52d3bff +http/cves/2010/CVE-2010-1653.yaml:b92de6229c98204320cd19caf92b8fc69722d011 +http/cves/2010/CVE-2010-1657.yaml:ea7d1c72ecf954ce77a11f2ee6144cb2d4b13f04 +http/cves/2010/CVE-2010-1658.yaml:bdcbd26e4277d7952703098399629699e1c7a7b0 +http/cves/2010/CVE-2010-1659.yaml:d004f90a63a660a4f2318bf652530ef81e149c06 +http/cves/2010/CVE-2010-1714.yaml:7521c5ca52e74a4c51a1f078b7f8895885c6945e +http/cves/2010/CVE-2010-1715.yaml:aec406347e179dcc1821b316042f23b9b1e60ccb +http/cves/2010/CVE-2010-1717.yaml:d8faa79c18f72eee4ab7ddb8cc01e1aded7c7e78 +http/cves/2010/CVE-2010-1718.yaml:7a76f8ac2d93717128f0ee581c0317bb21d33f2a +http/cves/2010/CVE-2010-1719.yaml:5b8d50a14919748f451ed0139233cb5481a31380 +http/cves/2010/CVE-2010-1722.yaml:6d9cd487ff26d0039fec2ac04cf2d642f353e2b8 +http/cves/2010/CVE-2010-1723.yaml:32fe697a3d4e1f3ba9f1ffb05cc0eeebd23295e3 +http/cves/2010/CVE-2010-1858.yaml:ae09fe6bfed79b326ecf1e245021ed39a2b5d2a0 +http/cves/2010/CVE-2010-1870.yaml:0c0dba6ad9d084a752cb89609b931032f4f609e2 +http/cves/2010/CVE-2010-1875.yaml:b2fa10d6381ab0cd227c510ed95977e534bc7469 +http/cves/2010/CVE-2010-1878.yaml:7c0d7d8be19a077bbae14bf509fe9df9264af738 +http/cves/2010/CVE-2010-1952.yaml:4144b247d17ff80ebd6167271bb3bb745562151c http/cves/2010/CVE-2010-1953.yaml:c35bb71d990df0d9d3d7eaf92078753447c099eb http/cves/2010/CVE-2010-1954.yaml:72fc8a597c461bf74d16db60cdc49e3f7c4e7590 -http/cves/2010/CVE-2010-1955.yaml:71d25d8810dc3da251beeb3f04a5d7b64d9c5bf7 -http/cves/2010/CVE-2010-1956.yaml:627faf4b6f762f84bd30f4e816f33bb2b20328c0 -http/cves/2010/CVE-2010-1957.yaml:7993615e97227e249e951a1fd117a91410733b5a -http/cves/2010/CVE-2010-1977.yaml:d242b2c9f5e4e3cceaca7561f08d7eb291d49b22 -http/cves/2010/CVE-2010-1979.yaml:90109228ad2e346d39df7c7cd3010ee6c94f3800 -http/cves/2010/CVE-2010-1980.yaml:190a843f63a0755f46680e505ef335a29fdd98c9 -http/cves/2010/CVE-2010-1981.yaml:7779d9ad99556a93a1490a1181782ce7d8272fc5 -http/cves/2010/CVE-2010-1982.yaml:f57c50541ec73db33a9207f764a5f91e8e42e425 -http/cves/2010/CVE-2010-1983.yaml:2dd4af85f9faf3f796017a986b90efafddead912 -http/cves/2010/CVE-2010-2033.yaml:927374d8da993a7f32260c434d0d24aaa4b999c4 -http/cves/2010/CVE-2010-2034.yaml:a08ef063af5de36d8777d7872b23b4a75d0d9bfa -http/cves/2010/CVE-2010-2035.yaml:067bb2289e61ea10effc72f97ad0f1a203689a38 -http/cves/2010/CVE-2010-2036.yaml:6c6ed3f66c048f6f726a0d5877700fbb1e40f27f -http/cves/2010/CVE-2010-2037.yaml:1068df61410e4b59e10de05c2df32603656e5717 -http/cves/2010/CVE-2010-2045.yaml:e78ec9d3480f8e92ac2cd3598220cc9a3c8d9fab -http/cves/2010/CVE-2010-2050.yaml:fae36afcd05ebecb5394e070fccea49af177d171 -http/cves/2010/CVE-2010-2122.yaml:bc8d52493712a3ced9da028974a9fbdd53bd057b -http/cves/2010/CVE-2010-2128.yaml:80dfdaa4c5117ab4e698e82257b2240d8db686ad -http/cves/2010/CVE-2010-2259.yaml:393fd8976edae7089ef57469b2c22bba0d0d4f78 -http/cves/2010/CVE-2010-2307.yaml:22a91f958c8f03f41d321e91ad4fb36fbabbcf98 -http/cves/2010/CVE-2010-2507.yaml:fa618f0471fc2c06915d363e42860fbe88e21429 -http/cves/2010/CVE-2010-2680.yaml:930a1fc4f7a8bd47328aacb400485099c7e911d1 -http/cves/2010/CVE-2010-2682.yaml:1108e0379c9227d3cbc8b657cbad9c7412ab58f6 -http/cves/2010/CVE-2010-2857.yaml:8d890858d83da2e451a5e6eecfb19ab16985fc1d +http/cves/2010/CVE-2010-1955.yaml:0bbecbc88be3366249f91e2b1ab64653ed7e29db +http/cves/2010/CVE-2010-1956.yaml:936c3226e4a1df55aad5bd4f2f2c2f52b712e301 +http/cves/2010/CVE-2010-1957.yaml:3ef5d518df95aaf92fdccb150b9a8339dba52e1d +http/cves/2010/CVE-2010-1977.yaml:717d54be1d01d002a856eedcd6c64b6deddb4ff1 +http/cves/2010/CVE-2010-1979.yaml:e35f2b37bb6babbf9d9a00f77fdb0718776cfc4c +http/cves/2010/CVE-2010-1980.yaml:15bc9c93a25357f0f2512a128897b6e5d88b9a5c +http/cves/2010/CVE-2010-1981.yaml:507682e7ad13255a17b86782f48b254bddeb1fc0 +http/cves/2010/CVE-2010-1982.yaml:e282595039aa5ad0b70430f48b3266735bfbe790 +http/cves/2010/CVE-2010-1983.yaml:e51dbb21f0bdac7def6367f2e4d4032271817f14 +http/cves/2010/CVE-2010-2033.yaml:b30668f9faac754e94746919cde2b36114667e7d +http/cves/2010/CVE-2010-2034.yaml:c41c9be605c6764b82d14bb3d7a145cb4d85c854 +http/cves/2010/CVE-2010-2035.yaml:a02fe1d2d11eb8f847a5323d38fccc1ac80ba934 +http/cves/2010/CVE-2010-2036.yaml:62ec4e93c02094781df0c8db67a4bd79226eb4bf +http/cves/2010/CVE-2010-2037.yaml:e89a6761a072261a7b51f643acd0d33b0693b2b0 +http/cves/2010/CVE-2010-2045.yaml:d025724b51e82b74fc7b9eae34dbfab62a69bd16 +http/cves/2010/CVE-2010-2050.yaml:46d4dd324eccbb50582cfd23fc6d440c22294b32 +http/cves/2010/CVE-2010-2122.yaml:69bddf66ca88c7a89f0f05700b911cb0a39729eb +http/cves/2010/CVE-2010-2128.yaml:2d1064c1850bc3114c566a32ca664fbcf6957431 +http/cves/2010/CVE-2010-2259.yaml:c2c104a8995d5a01b0338502bbf68f0c261cc96d +http/cves/2010/CVE-2010-2307.yaml:97c2eac4da120c5be758999cfbf1dafc8dce21ec +http/cves/2010/CVE-2010-2507.yaml:1dcee5f5a1c6ba2acab480223391ab35db86ac48 +http/cves/2010/CVE-2010-2680.yaml:769fcf5fef9d5f61c3ace2ab47f98368f769780b +http/cves/2010/CVE-2010-2682.yaml:e2aeff7c7658ac1aa5bd1ffbb867e6770ceb0fbf +http/cves/2010/CVE-2010-2857.yaml:83c38f91c7d751398feaa8aea775b717c24bf061 http/cves/2010/CVE-2010-2861.yaml:6086b32ba5e753e913a86a694cd00b6a79be677a -http/cves/2010/CVE-2010-2918.yaml:ac4b24911633ee6631246af3ee31d020b75cc72f -http/cves/2010/CVE-2010-2920.yaml:417092420923cc3a72c8a47fae882cfb8eaa8897 -http/cves/2010/CVE-2010-3203.yaml:d6fa315735346de9502aa714091757ed85d9b839 -http/cves/2010/CVE-2010-3426.yaml:4673dfb63123faa451b0d7fb0af1fec35bf464ac -http/cves/2010/CVE-2010-4231.yaml:9515e97d8d6c47b1c9c47c83847317318b8d4815 -http/cves/2010/CVE-2010-4239.yaml:6b2de02f4e6cf3786841e74be31f7eec5ce25bc1 -http/cves/2010/CVE-2010-4282.yaml:5416c18f2ccaca80bb9166890695978eaeaeb0e9 -http/cves/2010/CVE-2010-4617.yaml:5cf4522ea66f50fc19242c25c9edb1611d86ebe1 -http/cves/2010/CVE-2010-4719.yaml:761da5b76b99a9fbd2ddbb198ff3195c58feb27b -http/cves/2010/CVE-2010-4769.yaml:4770573023b32c051be83f96313adde350ea9d9e -http/cves/2010/CVE-2010-4977.yaml:8724e532da3d96e8d90e6e54435ce3e999f6f57f +http/cves/2010/CVE-2010-2918.yaml:384bf71d90253e5ab684294fc16cd846c63e0055 +http/cves/2010/CVE-2010-2920.yaml:4f263498606375eada279aecc100d8fb60022d21 +http/cves/2010/CVE-2010-3203.yaml:bd032e1edd5a7df7233f5722aada420d3c1d6a3d +http/cves/2010/CVE-2010-3426.yaml:459593c7c160e74d40c1db67ce1695ff8e65ee59 +http/cves/2010/CVE-2010-4231.yaml:f62e315cfa6ca62a311a4c5587880f6eb0266daf +http/cves/2010/CVE-2010-4239.yaml:8cb850c97d6305259aac27ee6c49f07285ca56a7 +http/cves/2010/CVE-2010-4282.yaml:edda821c3419d88eb6470a15a6c731c7b7069ae1 +http/cves/2010/CVE-2010-4617.yaml:7b5259f9cdffae407d82b5435f1112d583554eb0 +http/cves/2010/CVE-2010-4719.yaml:dec41a09bd65d4503055c57f80676dddd4396403 +http/cves/2010/CVE-2010-4769.yaml:92a2986f13828f6ef33fcd5c9d4256091a23df25 +http/cves/2010/CVE-2010-4977.yaml:c25b37a65ac743f56fbfeaff036bc74784235880 http/cves/2010/CVE-2010-5028.yaml:fbe457b3b77a774721b159ca29c4cabc13af56d2 -http/cves/2010/CVE-2010-5278.yaml:2e4d098487292ecc20abd747ad11f9a0883def26 -http/cves/2010/CVE-2010-5286.yaml:1366fa749abd0eb514090ee969d34a49829e7c00 +http/cves/2010/CVE-2010-5278.yaml:c0d0605b9af60e55999f71a678cac9557104e8d4 +http/cves/2010/CVE-2010-5286.yaml:413058e8bb72980f15efd20e93973abf640bf50a http/cves/2011/CVE-2011-0049.yaml:adb4f4a39abcc1726a5a29e47f4e9f3ce6ba054c -http/cves/2011/CVE-2011-1669.yaml:681a4d2624eaa61e3100676460f8d62ea24a0fa0 -http/cves/2011/CVE-2011-2744.yaml:49a26ec4bc8afd9f7263f38a3ac1a11c78eeaf95 -http/cves/2011/CVE-2011-2780.yaml:bc0c9129e2d300b15b80255b8415afab74a3171c -http/cves/2011/CVE-2011-3315.yaml:e42a81ddb28b66cc9fc030368c7312b23b5b587f -http/cves/2011/CVE-2011-4336.yaml:53d5ae8a8f4f86fa407c971b3e64dc1985fed97c -http/cves/2011/CVE-2011-4618.yaml:34af0a51d10d3fd375e17679fed1aa1ef32b94b2 -http/cves/2011/CVE-2011-4624.yaml:690f3e3cc95e44012c6ca0f8d132d3cb396bc941 -http/cves/2011/CVE-2011-4804.yaml:643b1d50496ecfb1a0ea5851cba38c333cfe5c2c -http/cves/2011/CVE-2011-4926.yaml:9d65a34da253c5c30001129e53d4b02b7953dfa1 -http/cves/2011/CVE-2011-5106.yaml:d564b98c9719d8b5b16bbad61e86185e57f98e4f -http/cves/2011/CVE-2011-5107.yaml:71e547641caf55fd504a9a4e4ae8aa9205470ff0 -http/cves/2011/CVE-2011-5179.yaml:3d3ad9fa2771d173a26e69ea652953dff6062c0f -http/cves/2011/CVE-2011-5181.yaml:b0b0766dc45bf730d5ccaada9956296892aab4c8 -http/cves/2011/CVE-2011-5252.yaml:755de75cc1f46ebab08cf828c050c7277794da2f -http/cves/2011/CVE-2011-5265.yaml:0d9448088d7b21e0a6b2b54a2c874e4e0ac09ead +http/cves/2011/CVE-2011-1669.yaml:28bcda9de7c3e95b7def307252e2bb4df652a66a +http/cves/2011/CVE-2011-2744.yaml:6a22e5a2982b06b639437ccd21a0a5f335b33c95 +http/cves/2011/CVE-2011-2780.yaml:ea8f32f0138360e75bb873ca3b80ae8dc5cc0685 +http/cves/2011/CVE-2011-3315.yaml:4aa163ff243c7fcafa51fae9859d547a47e33dcc +http/cves/2011/CVE-2011-4336.yaml:2ef0d8188ed031123a2c232ba11bd49b08350088 +http/cves/2011/CVE-2011-4618.yaml:f21d6445795eb3d95de15b4982f3c1e893e68230 +http/cves/2011/CVE-2011-4624.yaml:5a0f7df99a199fec5213f29d1e0ea67a31c2a9d7 +http/cves/2011/CVE-2011-4804.yaml:8c2fb660bf70b1670f726a8a630ec36b6c3e2d88 +http/cves/2011/CVE-2011-4926.yaml:d1b2f8d9f96c42f6775764fcff07eb004131fe96 +http/cves/2011/CVE-2011-5106.yaml:b549f374eacb1758bb063ec0cebe7df5a10a9ec2 +http/cves/2011/CVE-2011-5107.yaml:5fb94f80db5257df9679150e3a04a587f0e90ecf +http/cves/2011/CVE-2011-5179.yaml:32fa41b9e0a2207d60b3ae2dded23deddc7f1c6b +http/cves/2011/CVE-2011-5181.yaml:109163e21e28891f43dc1881f01d8dc0a0f5d711 +http/cves/2011/CVE-2011-5252.yaml:ff9d30e8d5c2953e3bc7c7402bb2b3b4fc80335a +http/cves/2011/CVE-2011-5265.yaml:07d1f0722962bb0c049c4d1cae070a474b042796 http/cves/2012/CVE-2012-0392.yaml:c0cdbfb9faf920d4ba78942348993338ceda0296 http/cves/2012/CVE-2012-0394.yaml:ed9717c6640fe22937a018d02163462d3e1f1c34 -http/cves/2012/CVE-2012-0896.yaml:6813303ce19d79d254ea3b26ccc4a7d28322deb3 -http/cves/2012/CVE-2012-0901.yaml:ab4fd2789b1db086cd0e54df016474ba9b1a4e25 -http/cves/2012/CVE-2012-0981.yaml:18cf40c2fa6506a81163ba8e45fb1fb03b745d68 +http/cves/2012/CVE-2012-0896.yaml:dec9b8a0d0ceaa61d461fe0505f7ddbb1705291f +http/cves/2012/CVE-2012-0901.yaml:faa3397df63f6eafe919155f42353bbaee1df1c4 +http/cves/2012/CVE-2012-0981.yaml:0906699cd73cf77e761c9aebcebb46ad3ea5accc http/cves/2012/CVE-2012-0991.yaml:c8247f06c708727964b7d06fad5a503cb50dfa1b -http/cves/2012/CVE-2012-0996.yaml:011b3b14c734c43ad7a9df7283253584ce4a6dec -http/cves/2012/CVE-2012-1226.yaml:63e16a716d6058954dbf736822a8609485f6cdd6 +http/cves/2012/CVE-2012-0996.yaml:1710e8b2ae0bd23c9ff1470fbe4e6c88a51c8c2f +http/cves/2012/CVE-2012-1226.yaml:10711e9bd35c8406b48b6fcacb6f294b263934ec http/cves/2012/CVE-2012-1823.yaml:b3ca96913fa1e45c2dc8a76d1c3861e710dcaccf -http/cves/2012/CVE-2012-1835.yaml:28116a27af1bff85fc5803b5e433303cc798bcf4 -http/cves/2012/CVE-2012-2371.yaml:e7d6fb6f34cf7d2d884824f45cac0a63c0a85373 +http/cves/2012/CVE-2012-1835.yaml:2b907f608f12a17fd909f82f36a12b0d2f587e6e +http/cves/2012/CVE-2012-2371.yaml:9422e3d099c942a40689492b9dcda0efafbb9c56 http/cves/2012/CVE-2012-3153.yaml:b3fc2475328c24153985472abdf1c941b5fed5be -http/cves/2012/CVE-2012-4032.yaml:842af978abafca8c77aaa19f3ab2d9c51752f04e -http/cves/2012/CVE-2012-4242.yaml:3f10fc34b4cd1ac5e454420116be533deed92431 -http/cves/2012/CVE-2012-4253.yaml:9efb326b3113fef3579e9fc40234e67f75717dd7 -http/cves/2012/CVE-2012-4273.yaml:65fe4bbd35ed9cbb6b119629dd1bc9a47ffd3543 -http/cves/2012/CVE-2012-4547.yaml:b1df6df7b986c2c0867eb478d9a73f6d228e6ccb -http/cves/2012/CVE-2012-4768.yaml:bdc7521a4f409cb1f3bdf2596747803a306b7040 -http/cves/2012/CVE-2012-4878.yaml:fc333135209297838a0aa5ff4f45f05499966aaa -http/cves/2012/CVE-2012-4889.yaml:87fafb4997afcbe1f10412017d6ebae20438a05c -http/cves/2012/CVE-2012-4940.yaml:9eae1401c442a237a1d500d35d86a6500520cb8b -http/cves/2012/CVE-2012-4982.yaml:4fa65b2dd854a6fdd3569842e363915c295ea3ef -http/cves/2012/CVE-2012-5321.yaml:316d580a3b0da90b37aaea52ae17cc9c1b2ff1ce -http/cves/2012/CVE-2012-5913.yaml:cdaa1a1e1934f94734177e8cfce57a6e637dcfa7 -http/cves/2012/CVE-2012-6499.yaml:f6cb7b63f74dcc9d81ea5731a262395bbdb0f274 -http/cves/2013/CVE-2013-1965.yaml:1e6188331297b4e576139f36cccb17b9ee8236c0 -http/cves/2013/CVE-2013-2248.yaml:bf28cb31ce4e243ef03131ce4e1d64cbc68e8d52 +http/cves/2012/CVE-2012-4032.yaml:edd5a56a4bfa5cafae49ac3c6ad9e3a7c5600ffa +http/cves/2012/CVE-2012-4242.yaml:8f3f23bf48658f7e21536563b1459b77a21fe03e +http/cves/2012/CVE-2012-4253.yaml:d403c3976d477e80dbd223008982d496df3fe364 +http/cves/2012/CVE-2012-4273.yaml:a1deb62d97ad0f6743236ad9ea3c68c1b6f7d913 +http/cves/2012/CVE-2012-4547.yaml:eb69c356f0c1cdd68a9b5f3b4266a6ee0ed01e4e +http/cves/2012/CVE-2012-4768.yaml:d2e2d97149f0cae611911e764f3ffc580c7e9884 +http/cves/2012/CVE-2012-4878.yaml:f5621278ce9c50a554f1ca0caf079d232c6f21a6 +http/cves/2012/CVE-2012-4889.yaml:880bf8724f399e46c9cbfa3380cf59c9f34b8584 +http/cves/2012/CVE-2012-4940.yaml:ca59370be2287ce1eec8eb88c71c1a2c2e8506b2 +http/cves/2012/CVE-2012-4982.yaml:63143adfa141b2b23efeb6aebca8a351d43f34f3 +http/cves/2012/CVE-2012-5321.yaml:4ef30eb428dc016f17cdff5fdc5f1366d46fcc6e +http/cves/2012/CVE-2012-5913.yaml:d419b1b168eced700ae827bf6e0970be228d7038 +http/cves/2012/CVE-2012-6499.yaml:418ed4acf4ccdc8d6ce873b4a974547aa35a9cff +http/cves/2013/CVE-2013-1965.yaml:d2d20303ae44f4e213e4edb0ed70d322449b8c7b +http/cves/2013/CVE-2013-2248.yaml:08d78295437a7ac49ce322f1ab08dc83d54193f1 http/cves/2013/CVE-2013-2251.yaml:f37f7170ea92ecde9b07ff6425cc283986229686 -http/cves/2013/CVE-2013-2287.yaml:7c2e3b8179d488111cd444c2d8a823c13dcf1f4e -http/cves/2013/CVE-2013-2621.yaml:f3c918c8389ddad25fda258d437a33358fbbebb6 -http/cves/2013/CVE-2013-3526.yaml:299ade96ec7e3c736b7ebf7728dc401310b3e1c3 +http/cves/2013/CVE-2013-2287.yaml:ab751bda3e1b760ef88c2e11302498589faff804 +http/cves/2013/CVE-2013-2621.yaml:b3efdda59a3ea6e12ab3f484f4b8c302c46c23bf +http/cves/2013/CVE-2013-3526.yaml:5a248bb3d3a88d6df22f748690f905ba87bd0386 http/cves/2013/CVE-2013-3827.yaml:1a0931c1101ec5669cbd953fc2fe6f39dfb1607b -http/cves/2013/CVE-2013-4117.yaml:1f8459901446197c1ff1f7ef45b1bc80ffe434cb -http/cves/2013/CVE-2013-4625.yaml:61811310b021917f45bf6c2f91e8c1f838fd9973 -http/cves/2013/CVE-2013-5528.yaml:6ca4ddf2af30b46df793023690a3b6e01deb43fa +http/cves/2013/CVE-2013-4117.yaml:55824decf792f8d8c8c88b738a677ebca469967a +http/cves/2013/CVE-2013-4625.yaml:447aa2d3ce1c834db428e34ae6bd0bb2bea0c923 +http/cves/2013/CVE-2013-5528.yaml:1640614ea010605dba9077ff9b79ea9fba9efc75 http/cves/2013/CVE-2013-5979.yaml:de780705d7c3f09320cb15501a2dae2134681595 -http/cves/2013/CVE-2013-6281.yaml:34dfafd2530de01877993d0d26ab6fd138142898 +http/cves/2013/CVE-2013-6281.yaml:018451e66edcea215f64fe9d684cf23a49358b2e http/cves/2013/CVE-2013-7091.yaml:b139c5c64090f950b7d81df1321518b34f2f3d1b http/cves/2013/CVE-2013-7240.yaml:d7ba78561c3eb2d33782a932a4754549d2fc0f24 http/cves/2013/CVE-2013-7285.yaml:563401b0e398fd6a57673df2a58a0cf060240d8f http/cves/2014/CVE-2014-10037.yaml:e87fd91bb40d395d6931627d66deee7759d78e0e -http/cves/2014/CVE-2014-1203.yaml:e7359d556949c23ee3d44800d87a3750e73d142d +http/cves/2014/CVE-2014-1203.yaml:4cf85a3a6fc6d30a92d4daf35ab8b2d0dfacde73 http/cves/2014/CVE-2014-2321.yaml:9fc56cf0aab40a3fa52b345feb244e378e5c3ce4 http/cves/2014/CVE-2014-2323.yaml:179415eb7f0b7b934ea091d530fcb4afcbcbcf35 -http/cves/2014/CVE-2014-2383.yaml:16c6891c6dfe4614f9f9b90309fcc8e276c955c0 -http/cves/2014/CVE-2014-2908.yaml:f02706f236d1455edb23f9235bdc0bcdfc4e1222 +http/cves/2014/CVE-2014-2383.yaml:4d08c957a2a84eb4fb62feca705e9c22601cadc9 +http/cves/2014/CVE-2014-2908.yaml:bfe142eb91d70192bf6736b4af12c10d90de3f96 http/cves/2014/CVE-2014-2962.yaml:236b034ab2fb2c089d755f305118113c8e206ad4 http/cves/2014/CVE-2014-3120.yaml:2e9c07d85dc8b83a77784a6498157b1d5cab0a96 http/cves/2014/CVE-2014-3206.yaml:cf02ea6c0683ce85245fe701d6c04c50d82c219f http/cves/2014/CVE-2014-3704.yaml:d134e31107d007304f032051cb4e9a1aec54096b -http/cves/2014/CVE-2014-3744.yaml:efb94d04a42600a9f87af3a6a9d88f109aa35444 -http/cves/2014/CVE-2014-4210.yaml:ee9a71055dd61f877562a2efdcee67f5306914e0 -http/cves/2014/CVE-2014-4513.yaml:853043c81c4931f3ed1fc9fdc3d419e86ae19800 -http/cves/2014/CVE-2014-4535.yaml:cb06c7780e5e9a695fd7163529df6c9d54dd9c68 -http/cves/2014/CVE-2014-4536.yaml:d46b9ff647c4fcc4210de13e90f2c75b11c2178a -http/cves/2014/CVE-2014-4539.yaml:d89ed066ff75910916b8af517efc61525ba88338 -http/cves/2014/CVE-2014-4544.yaml:fe009e2322df2e86c42ec1478a59f6dd3955f88e -http/cves/2014/CVE-2014-4550.yaml:80f160ae0929711f6a8bf2364f671d06a550104c -http/cves/2014/CVE-2014-4558.yaml:f83350a37f5e7ef319a7f37fd94e4f8f50a05d77 -http/cves/2014/CVE-2014-4561.yaml:07fc43b22328781380e36602a99c55b8554893a6 -http/cves/2014/CVE-2014-4592.yaml:a0c6ea45af1c09b717a8c37ded272d15ed92be33 -http/cves/2014/CVE-2014-4940.yaml:08e2d85b714ac420d431f56ff863e67bba68fb03 -http/cves/2014/CVE-2014-4942.yaml:165da359ec61d8bbcc87720ba75438a0c5a94cee -http/cves/2014/CVE-2014-5111.yaml:598c72b72e0294d072617d5f0fc65bc09934255b +http/cves/2014/CVE-2014-3744.yaml:cf37d0ef8b6dad56477b08124d325b94848e6f33 +http/cves/2014/CVE-2014-4210.yaml:d4e3597cf120161ab9c589953f0dd2c6f865d670 +http/cves/2014/CVE-2014-4513.yaml:1176eded64ecddea7aef4d2a2f4f19d25e746d95 +http/cves/2014/CVE-2014-4535.yaml:aae5e918077e460ef861ac4429d3abea3901c5db +http/cves/2014/CVE-2014-4536.yaml:24bce5aee852382a59242aef4d4bfcdbf2548da5 +http/cves/2014/CVE-2014-4539.yaml:129b0c4189a479de9ae5d6113b0b1e9e0df18349 +http/cves/2014/CVE-2014-4544.yaml:506346eebacfc951e66f66e74f6394993a9fd41b +http/cves/2014/CVE-2014-4550.yaml:4fb93ec2d9c4b365247f9bb4523e200d4d0b599b +http/cves/2014/CVE-2014-4558.yaml:b2ac5d4c825710a5f2d56a534c79df813fe49925 +http/cves/2014/CVE-2014-4561.yaml:f0ac24cd50bdc4838cd7c475d6c79d78f5ffc51e +http/cves/2014/CVE-2014-4592.yaml:466218563ae9fee9b59dd4d3190c09c4b21142cd +http/cves/2014/CVE-2014-4940.yaml:fa31e3b37a5237e792c5840945f681ce0436b903 +http/cves/2014/CVE-2014-4942.yaml:4fa52a75b291ed60a186ba145f472173340c9873 +http/cves/2014/CVE-2014-5111.yaml:30a926535dfd25543f5e00e4ee723d2612c7052e http/cves/2014/CVE-2014-5258.yaml:96cb30459f5f244d52a086dfccef3e2953e14c2a http/cves/2014/CVE-2014-5368.yaml:7465e4d1dc11cce8e93aabb8fc560433aad895a2 http/cves/2014/CVE-2014-6271.yaml:1e66aea403b8845fc9a535c27a7a1d9f13fd3e75 http/cves/2014/CVE-2014-6287.yaml:49c1d0a80dcc741997738c84746c7c5891a0a504 http/cves/2014/CVE-2014-6308.yaml:3c0f7fceffacec6cebef3830c448724aa83034d4 http/cves/2014/CVE-2014-8676.yaml:187dcb4a4f5cfd13266e06cba479c09c65fa0b2c -http/cves/2014/CVE-2014-8682.yaml:52b9ebe35f2779a684c3ce1373b7eead9b8d07be -http/cves/2014/CVE-2014-8799.yaml:fa867ae677977323b95c579fd7e2d572e4ddc73a -http/cves/2014/CVE-2014-9094.yaml:32f0d7cd3a9c28df19cb68cf0313a5336aaed051 -http/cves/2014/CVE-2014-9119.yaml:7ad313c80ba6fe39bb33d01b7e10de8d361485b2 -http/cves/2014/CVE-2014-9180.yaml:695e715ee37479a0d7792153ed35beb609285505 -http/cves/2014/CVE-2014-9444.yaml:cdfb121caef9ecf4d56d2437ca06702f8f25f87e -http/cves/2014/CVE-2014-9606.yaml:47c0992bf89d6d2e630a0fa78b18be35a02f42b8 -http/cves/2014/CVE-2014-9607.yaml:52fb006d46ab1089d3df278298271c3a76e27e39 -http/cves/2014/CVE-2014-9608.yaml:d6f584ff064ef3f454ae9a84caf3a6b6d1f9c703 -http/cves/2014/CVE-2014-9609.yaml:819d74318dd2a48f596a82182919dc935c447458 +http/cves/2014/CVE-2014-8682.yaml:293b529fb90ec5f6e9760b2a6daccf939b020036 +http/cves/2014/CVE-2014-8799.yaml:acc80bf15280338c2f5853c6025e715e1f04333a +http/cves/2014/CVE-2014-9094.yaml:e764440b85d3fdcac44721dd8972d6c7aca210e8 +http/cves/2014/CVE-2014-9119.yaml:cad59ad82042d2f0e3cc30c73ac40bf3691d8c2b +http/cves/2014/CVE-2014-9180.yaml:96045824eaaa81253902c491df27b284c8a3991a +http/cves/2014/CVE-2014-9444.yaml:df4f885df77038352e8c09b74042189cf4a542c9 +http/cves/2014/CVE-2014-9606.yaml:6301ed6410dc41f56e22e928e49a716f6eaf95e8 +http/cves/2014/CVE-2014-9607.yaml:0e570524863c2c28987d1db36afb7c486628eaab +http/cves/2014/CVE-2014-9608.yaml:b9622b3e5584a846a0c4bf2b3357c11ed7679c90 +http/cves/2014/CVE-2014-9609.yaml:a1ff7f9357bdc2bb3f38fc38d53637635d8eb4a5 http/cves/2014/CVE-2014-9614.yaml:0524b5315d2f2d2eecfd9a09085c18cd4b8cda66 -http/cves/2014/CVE-2014-9615.yaml:3e184a313bdf0b98cccb2cb77fc3ecd285404b3b -http/cves/2014/CVE-2014-9617.yaml:4f63efb727f170fec6e37074a68770736d538120 -http/cves/2014/CVE-2014-9618.yaml:dc6c63c206d20b0e166e5b83d0fca52633131679 +http/cves/2014/CVE-2014-9615.yaml:cd25c9d27a967d5b20bc5db59a5342e8ca8c24cf +http/cves/2014/CVE-2014-9617.yaml:f2605650372449d0f6b2917fb4d7b76755e8a02f +http/cves/2014/CVE-2014-9618.yaml:b430da4e23a27974fccd63fedd0a23b757bcc1e4 http/cves/2015/CVE-2015-0554.yaml:ad6a8a46890616570bc97ef1e8903ef555894aee -http/cves/2015/CVE-2015-1000005.yaml:9af51e3fe7b141ad74062ff956942f8e25ae60f2 -http/cves/2015/CVE-2015-1000010.yaml:d3d7d138b611529069dee9c5d147ffe24ccec461 -http/cves/2015/CVE-2015-1000012.yaml:79fae5a09e0488dc0149eb9b5ec40e588e292cc2 -http/cves/2015/CVE-2015-1427.yaml:c0172922e08c4054f9c963d694d2fa1793483672 +http/cves/2015/CVE-2015-1000005.yaml:9f75a4c524d5533d8686d3088a49de3bdee626b4 +http/cves/2015/CVE-2015-1000010.yaml:6197887eb5a4f25fe9875535aca7a029d07148bf +http/cves/2015/CVE-2015-1000012.yaml:247170270c66b78f53335d10d529e5c60898ae7c +http/cves/2015/CVE-2015-1427.yaml:0be0992b1a2279d1dfd6feac3d60c16de611c9e4 http/cves/2015/CVE-2015-1503.yaml:24813d103832609dba7a795532cf94331a10048f http/cves/2015/CVE-2015-1579.yaml:dd85be570990c46b6e98245596d73dcc2f0166ca -http/cves/2015/CVE-2015-1880.yaml:8908e020f25c01eeddb61e8d0ff4865536ba953b +http/cves/2015/CVE-2015-1880.yaml:c0f12e841d9faa120ee052d5104cb4d05a3a4c83 http/cves/2015/CVE-2015-20067.yaml:785c1c2db6a4483739645939a7ba573a05503406 http/cves/2015/CVE-2015-2067.yaml:ae5d8bbcc1d17e195989f1da9f6c88458bbaea5a -http/cves/2015/CVE-2015-2068.yaml:9435104e811e25f66ff75611192b508f4fedac9a -http/cves/2015/CVE-2015-2080.yaml:0cf5908b759752c5d2d9dd71b28871145ed7225c -http/cves/2015/CVE-2015-2166.yaml:e4e305b47ae5345710f59fc87ef7278e7aa31b10 -http/cves/2015/CVE-2015-2196.yaml:dcda74215a6be57df747b5e87a47cf04919d720f -http/cves/2015/CVE-2015-2755.yaml:51289655e459a91fa31e296d33bd1f8e1b5116c4 -http/cves/2015/CVE-2015-2807.yaml:5e9bbcde6597496328a005a49e21483f0e3f2c1e -http/cves/2015/CVE-2015-2863.yaml:1c31ef5cd4f57281979ba6ee09762563c3f5b56d -http/cves/2015/CVE-2015-2996.yaml:a54cb23e676bcb75fb17c3f104f52822032ca55f -http/cves/2015/CVE-2015-3035.yaml:4894d22585379a9042e939c547f61a424ffa396e +http/cves/2015/CVE-2015-2068.yaml:3454d73c7018ed754fc68d74a3fd2cc65d577002 +http/cves/2015/CVE-2015-2080.yaml:b0e9dda6655d6cacf105d80e2b21b363560ae4ed +http/cves/2015/CVE-2015-2166.yaml:c8cf51f9889074c2802cf1e6f733e32e9711b702 +http/cves/2015/CVE-2015-2196.yaml:e7377577d610f154131474bfb2c3d0fb41e6dd15 +http/cves/2015/CVE-2015-2755.yaml:dfe58fc8848d9a71d544545e8b7541aa9ba448c0 +http/cves/2015/CVE-2015-2807.yaml:57efe8fad04716861086c27a6ce13f7c33aaf10b +http/cves/2015/CVE-2015-2863.yaml:1f847f82ceee8102ea7cf138d7b482db027ed025 +http/cves/2015/CVE-2015-2996.yaml:0c542d7dbc50cba22f23b44f15563226177a57c1 +http/cves/2015/CVE-2015-3035.yaml:68465cda46424b6ecb918748faf9824855361c41 http/cves/2015/CVE-2015-3224.yaml:2ccef753c9bde7bcb34b3ceaf4d70aed784f1b28 -http/cves/2015/CVE-2015-3337.yaml:8c883266a9112661240c6aa6797491996bbfe18a -http/cves/2015/CVE-2015-3648.yaml:45ab91c974c68b44cf0d1d3007dc6cfebc18675f +http/cves/2015/CVE-2015-3337.yaml:3e664584840a3fe4edf1bd199c5debd0ddf55a82 +http/cves/2015/CVE-2015-3648.yaml:d67eaa03367cd8670a33ad170438bd536c287ab5 http/cves/2015/CVE-2015-3897.yaml:532621c769194b947385a36da08bf8b88e626ad7 -http/cves/2015/CVE-2015-4050.yaml:2e4fde223425c275935a9000f351b047b320c12c -http/cves/2015/CVE-2015-4062.yaml:9a02ba5867d9a26d74a189938658f8bce4c0029d -http/cves/2015/CVE-2015-4063.yaml:bf659f6f743328ee3f4c9fd02f5f6de0f8edaee4 -http/cves/2015/CVE-2015-4074.yaml:bc0d2a98ecfb215bb1ed0da46d0c881942e13cff -http/cves/2015/CVE-2015-4127.yaml:d7cb7722439d06b70129dc5d84efc158c776ebef +http/cves/2015/CVE-2015-4050.yaml:dc1d19a9afb8eac04f04d99d1868c12158a386c8 +http/cves/2015/CVE-2015-4062.yaml:a7ea24ac0cd0ae71acb19aa03a29a645797af504 +http/cves/2015/CVE-2015-4063.yaml:ca538a219a38dfddd34a6a7c74a225d04c35be2a +http/cves/2015/CVE-2015-4074.yaml:21da540d8e653e8826e1520975e3b44e29753737 +http/cves/2015/CVE-2015-4127.yaml:600b40c1a7b366931d8f60076ddd14b44532bdf7 http/cves/2015/CVE-2015-4414.yaml:d8e58ad8c6f395568441cdb2b4c58c368d4bffd6 -http/cves/2015/CVE-2015-4632.yaml:ca38ebaee9dd8b5c600541ba3a960e12b4b920c6 -http/cves/2015/CVE-2015-4666.yaml:ba4350a201540a68f8dd00d226a3093461579309 -http/cves/2015/CVE-2015-4668.yaml:a7fd03fe78433ec643f8159b61122f884fe029d2 -http/cves/2015/CVE-2015-4694.yaml:e9a228e570b6d863823c3ec3164a6426e055c533 -http/cves/2015/CVE-2015-5354.yaml:22394730edeb4263aa15888baaf2a98ee39bd7ba -http/cves/2015/CVE-2015-5461.yaml:5f94de6c1ee78b6405036075dfd3b6837ad3b1fd -http/cves/2015/CVE-2015-5469.yaml:2c4ed7a2f1010b350d1d2a2c4dd04fee9934cc6a +http/cves/2015/CVE-2015-4632.yaml:86479143cd067e42a6f990d2ffec5ea8f5c3cbaa +http/cves/2015/CVE-2015-4666.yaml:7ea9cd9ffdd9cf392771329dc4034da6e4eedcbd +http/cves/2015/CVE-2015-4668.yaml:70cb7ba49c697365d6653a1b819266b09a7c7fbf +http/cves/2015/CVE-2015-4694.yaml:4e1d7ecbb63f6fe205520db326abbf81ad3dff9c +http/cves/2015/CVE-2015-5354.yaml:4a7307c2c84f40585d12b3ba3a61e01b43f1cb58 +http/cves/2015/CVE-2015-5461.yaml:b3de62a767365473433e4903ce3a2d02437c74fe +http/cves/2015/CVE-2015-5469.yaml:a4900093339071bc6d48c00e1209b8937bb10463 http/cves/2015/CVE-2015-5471.yaml:3179ac43b7da3d160ac8abceea392e13abae7bdd http/cves/2015/CVE-2015-5531.yaml:1b184fe3dda38575a0df650924e3b50e9e8c2784 http/cves/2015/CVE-2015-5688.yaml:c1110dc8b641d261b97983e27cad55de4969f755 -http/cves/2015/CVE-2015-6477.yaml:ad8be8ee089803a4a7c0feab7c00eb11e763a380 -http/cves/2015/CVE-2015-6544.yaml:05ee325331147657a5a88a2fd94e4553881eeee4 -http/cves/2015/CVE-2015-6920.yaml:b11dad7bf093a9dcf88ac62af8c56daa4b24455d +http/cves/2015/CVE-2015-6477.yaml:6f971b739c69b88f4e44435ba93c1637eac1e9d9 +http/cves/2015/CVE-2015-6544.yaml:99eaf4deee42f462ea60198dcbbad46ea9784701 +http/cves/2015/CVE-2015-6920.yaml:dc7a81f6fb8c122eb8140f2b04a8a02e886f61c7 http/cves/2015/CVE-2015-7245.yaml:445a1410998f1b9785566b43e134aa75a2604afc http/cves/2015/CVE-2015-7297.yaml:fc0e45e765ba12ab68ddccab18304d18fe49aa64 -http/cves/2015/CVE-2015-7377.yaml:ae57dcdc9e2d04269ac59c3cba5be30a75a06dd3 +http/cves/2015/CVE-2015-7377.yaml:4eac02f33d5d79ac142c851231c8a21d84c96f8a http/cves/2015/CVE-2015-7450.yaml:69f8986c209b95a033d644814601ac02058cb3b4 -http/cves/2015/CVE-2015-7780.yaml:3a53d234dbc5ddb13be895a3237e2314dec09c99 -http/cves/2015/CVE-2015-7823.yaml:e2922da8dcc6004343615b5962494eb83cff77c1 -http/cves/2015/CVE-2015-8349.yaml:5dd01f2253d24cdbcf224b6ab260310749f71866 +http/cves/2015/CVE-2015-7780.yaml:67ebb5e0b38d7ad9c3930cee784c491d649ea91f +http/cves/2015/CVE-2015-7823.yaml:d13b5e41e15703c171ab5f1cab0b2417bcd5b0fe +http/cves/2015/CVE-2015-8349.yaml:39811c2b81d4fef4be55f47fe9742e5849e70125 http/cves/2015/CVE-2015-8399.yaml:4db37957f52bae35f96fd08713e49b7ed5d590b0 -http/cves/2015/CVE-2015-8813.yaml:8b90a394d3b6daea7ddeab3a9aca2a43b8fdb4ad -http/cves/2015/CVE-2015-9312.yaml:669c7b7ca76782e24f464cb8ae54d9a2a6fce70e -http/cves/2015/CVE-2015-9323.yaml:08b7ead58f5db7d75a2f6ea033482a0b8b55f5e5 -http/cves/2015/CVE-2015-9414.yaml:f921748e7f6f07e57bcb14c7869aec82e2d6b7fe -http/cves/2015/CVE-2015-9480.yaml:9305f21384135bc3a72b37ee91c10160b3c3b584 -http/cves/2016/CVE-2016-0957.yaml:5a8352a39364218407a6d24f58c8644b70d05456 -http/cves/2016/CVE-2016-1000126.yaml:803c33ee0ffa64d2f1655d307bc60b5818e29e69 -http/cves/2016/CVE-2016-1000127.yaml:48804b6f3996911663ee00b186fdef560b8da5ab -http/cves/2016/CVE-2016-1000128.yaml:29c6b86edf7d6b3e669df17fe46f4411cb0985b6 -http/cves/2016/CVE-2016-1000129.yaml:a04b8a7a51a3c0ee868f2dc24f57a1c47ac02464 -http/cves/2016/CVE-2016-1000130.yaml:0ec7140c08146e84694de6e75918285b046534ea -http/cves/2016/CVE-2016-1000131.yaml:7272e9af11d150916899aaac455d5cf64ab9c9ae -http/cves/2016/CVE-2016-1000132.yaml:146b316061f137aef139c19780287a774e9c201f -http/cves/2016/CVE-2016-1000133.yaml:0981dcc97b7ac77d775720827805e4590f37bfbc -http/cves/2016/CVE-2016-1000134.yaml:da4eabac63aa23b7f7564fc33ed589ae7f921a50 -http/cves/2016/CVE-2016-1000135.yaml:d81752946bf569a1c549e6794c97c6eb62c03d48 -http/cves/2016/CVE-2016-1000136.yaml:519e6d96cd2a0f04195a8ae81c6e64f0cc9d8820 -http/cves/2016/CVE-2016-1000137.yaml:ee2448fd91afa24a1350e14293261fd1a25dc283 -http/cves/2016/CVE-2016-1000138.yaml:7807b04e2b88f2a36fbd5b981d0705ee01aa2185 -http/cves/2016/CVE-2016-1000139.yaml:28f148c1517e23affe6dbc4ada2a52606fb1f544 -http/cves/2016/CVE-2016-1000140.yaml:2a3026a6c439f90cebae0f9bbb26da3d6cc26439 -http/cves/2016/CVE-2016-1000141.yaml:e1e08e3658563134a6eae5836ade14b417e54c9d -http/cves/2016/CVE-2016-1000142.yaml:1d24522685c456ebdc71313aa897dc09db193234 -http/cves/2016/CVE-2016-1000143.yaml:bf33f5a7701305d4ad68e059c9d5bc8ae4d461aa -http/cves/2016/CVE-2016-1000146.yaml:06a3853b31c3670d5f7a025461246028d221506e -http/cves/2016/CVE-2016-1000148.yaml:670cbdebed56f94c590baef6f4bf12a3ed648892 -http/cves/2016/CVE-2016-1000149.yaml:ba56dd2275812ce4a22bca2c7e9d6e88989cc013 -http/cves/2016/CVE-2016-1000152.yaml:54830a8e8b45d7973a9d5ab228dce1dceebc9d48 -http/cves/2016/CVE-2016-1000153.yaml:c5395f475e59c3153c790c7f1c116400c97da1f2 -http/cves/2016/CVE-2016-1000154.yaml:a3fb3f88f61e61ba047cb161f5498768da20a01e -http/cves/2016/CVE-2016-1000155.yaml:2ebb182404275af721cf2ab528df63b3f8e30c2a +http/cves/2015/CVE-2015-8813.yaml:b76fe43c234e29662731c39a7b552cad652a01c4 +http/cves/2015/CVE-2015-9312.yaml:aad5f871acb39560fcfa94c90145d9057d481e6d +http/cves/2015/CVE-2015-9323.yaml:c8461f0dbe2a438f1dee68dca6f05790bdebfccc +http/cves/2015/CVE-2015-9414.yaml:2a4061e05fa0d7fb26ca225a5cc7089537ae3c82 +http/cves/2015/CVE-2015-9480.yaml:f2d6e039de96cb4f40d7460bf372123d8bcfa8aa +http/cves/2016/CVE-2016-0957.yaml:38116d5bdca330760d85299215530b059c94fe64 +http/cves/2016/CVE-2016-1000126.yaml:f556e0d3014036a0ceb52e05f3e78609631e5bae +http/cves/2016/CVE-2016-1000127.yaml:2d25aea05b3c81341e45b0aa2308c35178525d25 +http/cves/2016/CVE-2016-1000128.yaml:129e139e2f094fbe0792ea3057c558891d182ce0 +http/cves/2016/CVE-2016-1000129.yaml:dddd82d64deec20fa8e41bd3d48ef5e4603006fc +http/cves/2016/CVE-2016-1000130.yaml:15866766b69f92fc2199b4945d4e0ff8af967e53 +http/cves/2016/CVE-2016-1000131.yaml:ed3aeee0f83b96c67f86f8d748f4692ebfcdec06 +http/cves/2016/CVE-2016-1000132.yaml:b775ac02ddcb9f2628676e84bd7fbb4ee67c8c27 +http/cves/2016/CVE-2016-1000133.yaml:643799053719f639e6aa13e40ebf4f856b595b27 +http/cves/2016/CVE-2016-1000134.yaml:0d50cbfa588427c97f5deab6d77aec6c80583236 +http/cves/2016/CVE-2016-1000135.yaml:01bbe03bd3b7699976f575b31954021fc887cdb6 +http/cves/2016/CVE-2016-1000136.yaml:0ba0cf777c7a9140571a6843797bf23b476f880d +http/cves/2016/CVE-2016-1000137.yaml:2aadd07ad39a0a83835f14196285c2ee132f0ded +http/cves/2016/CVE-2016-1000138.yaml:976fea844d6de68a1ef84d41090cdbc664dfca75 +http/cves/2016/CVE-2016-1000139.yaml:fbc9cdf35dac003b93d49415cee92e91b9e02e25 +http/cves/2016/CVE-2016-1000140.yaml:86bb6aca86490b02f0ea81eebe3dcf4c48b850e7 +http/cves/2016/CVE-2016-1000141.yaml:ebd9a808f8a055255c1abb95a6f2007484f627c8 +http/cves/2016/CVE-2016-1000142.yaml:36c52c6bd84aae09267a4a37a127deebd283f134 +http/cves/2016/CVE-2016-1000143.yaml:a6e6528c155676317537f19779fb544979f212a7 +http/cves/2016/CVE-2016-1000146.yaml:1bd6f1a898d6cd770787381376085dde4dabe15c +http/cves/2016/CVE-2016-1000148.yaml:b66ac451a2d81e35841bcc53f5af666991ff2b7f +http/cves/2016/CVE-2016-1000149.yaml:2476a7aac5e3b37ac23bba996bac08ed637bf6e4 +http/cves/2016/CVE-2016-1000152.yaml:9d73b5ad897a470a7a3620eea1068d22437f04fb +http/cves/2016/CVE-2016-1000153.yaml:e51336bb7f7f71894402c7f972a5c49bf3cb2ee2 +http/cves/2016/CVE-2016-1000154.yaml:5aafb2f831e71122a0ef795776d73bb31e486ed3 +http/cves/2016/CVE-2016-1000155.yaml:2505d76c1bc83c0ae0dab7e03acdedf0b981802e http/cves/2016/CVE-2016-10033.yaml:fceb5169aabc2a90ad3c1729a28d91bd9bfbd2fe -http/cves/2016/CVE-2016-10108.yaml:a84e21d05f9fa70e9d514e009682e4b82b2126a2 -http/cves/2016/CVE-2016-10134.yaml:7d593228ec1ee987630e386e9e984f3be14bca22 -http/cves/2016/CVE-2016-10367.yaml:7d8b492beee3ca8644ff90de5b6cdbf8d3dc8a36 -http/cves/2016/CVE-2016-10368.yaml:09a3e541a684b975427415d61c6a2516fc5150f0 -http/cves/2016/CVE-2016-10924.yaml:9ff66ad014c437495067eacd9866807736a9cb17 -http/cves/2016/CVE-2016-10940.yaml:4a8ad92d519e1fd904055457c98df0a4992ce252 -http/cves/2016/CVE-2016-10956.yaml:53dae6c8e9f374ed95a25d71ef92dd0e24c2a947 -http/cves/2016/CVE-2016-10960.yaml:043530b11450e552556cff64ec6a942c580149cd -http/cves/2016/CVE-2016-10973.yaml:76b036ef55c40c3216203375369d51cf71b959c7 -http/cves/2016/CVE-2016-10993.yaml:107f5fcf56098d32b004b60effc0aed38cd261de +http/cves/2016/CVE-2016-10108.yaml:c3a5aba94dcc602e5054bbeaf387d228aa976594 +http/cves/2016/CVE-2016-10134.yaml:596777e57519fa450b50ebaefc25352daf1bb120 +http/cves/2016/CVE-2016-10367.yaml:00bc94180a0d2b3c43c5bac2fd2e38f5a9f752d0 +http/cves/2016/CVE-2016-10368.yaml:ece3044b1ed14829c4985e5b73e847e60b209a8a +http/cves/2016/CVE-2016-10924.yaml:cc91f617dc327feb945239181e8075f6074a5f3c +http/cves/2016/CVE-2016-10940.yaml:114c9c9c42fb0d0ffe03625d029ecd71f3256f77 +http/cves/2016/CVE-2016-10956.yaml:7cfef820535ce745d6c738147c8fc8d549a458ab +http/cves/2016/CVE-2016-10960.yaml:c9cc221e09be68751e46ba59fbd08833a4a4633e +http/cves/2016/CVE-2016-10973.yaml:3a0c38014ab119ec129acaa5b184ab335212cb54 +http/cves/2016/CVE-2016-10993.yaml:d672df06403c9f20feb23daef7f903abef255daa http/cves/2016/CVE-2016-1555.yaml:b490142c86c4c5c39d2c685fe6606c06e2f006d9 -http/cves/2016/CVE-2016-2389.yaml:8d008797cbc0c5bb4bd03ad7652de4fc72f25e70 +http/cves/2016/CVE-2016-2389.yaml:385322a569bb2a0390bf30841c41726f1e1f6286 http/cves/2016/CVE-2016-3081.yaml:c822fe1dc8665ecd5c6b11603e33922a1d772747 http/cves/2016/CVE-2016-3088.yaml:a4a67d5081eb8b588664d1516ed55be35d0ff548 -http/cves/2016/CVE-2016-3978.yaml:71abb378666535b58e5db209dbbb8f5648b9b8da +http/cves/2016/CVE-2016-3978.yaml:594a52842a88e6da2fe6ba20bbb931810293d804 http/cves/2016/CVE-2016-4437.yaml:b43d38eb16801112e495f3be28fea1ae5eb32055 -http/cves/2016/CVE-2016-4975.yaml:ec408d927cbd5bac3bcbe2135dfbc010dfb419e8 -http/cves/2016/CVE-2016-4977.yaml:36669c3fc3a24f50b84c39a2a67ee6afc1554ba4 -http/cves/2016/CVE-2016-5649.yaml:c86f0b86c20ae68b893054dfecb01e3a5a8be2fc -http/cves/2016/CVE-2016-6195.yaml:ab883e6230eb5c6356f28e01ac6b29db078f16a8 +http/cves/2016/CVE-2016-4975.yaml:b6bdc1c9f799e1df35b986c81b423ea46f59e992 +http/cves/2016/CVE-2016-4977.yaml:5fff94abbe43b01489c4bdc4748b8835cc046d88 +http/cves/2016/CVE-2016-5649.yaml:33fd4709c1ecdc47b97d2c6905e6cb6b410eaf83 +http/cves/2016/CVE-2016-6195.yaml:27a2493e563e0769fabd38743eafbfaf8297fc11 http/cves/2016/CVE-2016-6277.yaml:c1e90c5d2a8a86e7c52fa7685245a493b657ea22 http/cves/2016/CVE-2016-6601.yaml:54bed45f6a06dc0afe40094751cfb2ce02de0630 -http/cves/2016/CVE-2016-7552.yaml:be23ae8e525e622d2b3286cae5db3b57a1adffd8 -http/cves/2016/CVE-2016-7834.yaml:6a90436dac0afcc8fa75d43bb21acb1def098caf -http/cves/2016/CVE-2016-7981.yaml:449c6fd385aca0af56d2669b6f1eede0be8f9334 -http/cves/2016/CVE-2016-8527.yaml:899e304433caac6d4f8d19cb5a3c07aff76d40ca -http/cves/2017/CVE-2017-0929.yaml:afc5ac9fe0699b77d974c4233dfbbf75e7d992b9 +http/cves/2016/CVE-2016-7552.yaml:99665cc470aab4fe701af85d1ec4f27c42e70299 +http/cves/2016/CVE-2016-7834.yaml:8305485901360f949e08adbe53a500958f634d17 +http/cves/2016/CVE-2016-7981.yaml:053e1ff264391b0f2f41eaf8ec3a2dafc384f697 +http/cves/2016/CVE-2016-8527.yaml:ff5e23241d82d916de0ba7cdc98d11e54b686fda +http/cves/2017/CVE-2017-0929.yaml:9f0a93a7f41c7982176672a67e3c63d87a8b0cfe http/cves/2017/CVE-2017-1000028.yaml:5a9b1854daa7142bddc5e567071a1b44c4949203 -http/cves/2017/CVE-2017-1000029.yaml:b9dc16dce2fccd42c9233bae9944a2f58019bc33 -http/cves/2017/CVE-2017-1000163.yaml:24f18ec02dd39474d09a655f21b07be92fedb7b3 -http/cves/2017/CVE-2017-1000170.yaml:fb723fe1cd73448f58d61ea1498a18d5d4108704 +http/cves/2017/CVE-2017-1000029.yaml:083d72dc94b748e83a60ea41ace9ee3a9499757e +http/cves/2017/CVE-2017-1000163.yaml:7d3928c8a1606735842e3e21d08a088a6a91bd88 +http/cves/2017/CVE-2017-1000170.yaml:3671fd4aa20a28ba895c4a08491e7fc7363da037 http/cves/2017/CVE-2017-1000486.yaml:50f57c6bad5eb9e2fd754062ed315bd0f64c7290 -http/cves/2017/CVE-2017-10075.yaml:45ba5920c2db4847003ec679d84592099a370809 +http/cves/2017/CVE-2017-10075.yaml:297d1ae2bf08330c18d5dfb5be59b5f5c2d03552 http/cves/2017/CVE-2017-10271.yaml:d806dc695b011e103b1ee6c2434af5da43b77e53 http/cves/2017/CVE-2017-10974.yaml:2cd7084772f580d515c802853e1513b6567a3acd http/cves/2017/CVE-2017-11165.yaml:2143895c745472581967c66b9a3aba408d192654 -http/cves/2017/CVE-2017-11444.yaml:276e2b034ca6c0cd0fa58246e1d90832a1e93664 +http/cves/2017/CVE-2017-11444.yaml:f840360d6232cab48d10dadab77d13291aa24015 http/cves/2017/CVE-2017-11512.yaml:45f12edaf319a13ec10ef9b310600fb62588ff56 -http/cves/2017/CVE-2017-11586.yaml:a38413165501df3bc38b1b66d2e1871e1d3b349e +http/cves/2017/CVE-2017-11586.yaml:3b33a190fe2d197c170f87050e7619734e9b7ec8 http/cves/2017/CVE-2017-11610.yaml:848cab7db89ae3f77beaa7189ee846e7267215a9 -http/cves/2017/CVE-2017-11629.yaml:4312899be573e42e4ba6a1b2b577e35693157440 -http/cves/2017/CVE-2017-12138.yaml:578a49c3f40442c44c594c453aa5a2344802d884 +http/cves/2017/CVE-2017-11629.yaml:5c1687ff023b472573ddca5fd46b6c502b0ed88a +http/cves/2017/CVE-2017-12138.yaml:ec85855df8b6f8b4cf0162b74e25123933242228 http/cves/2017/CVE-2017-12149.yaml:caedabade832af4746e81cc593370ab2423c9970 http/cves/2017/CVE-2017-12542.yaml:5459264842cfd935c34d135aa4fb4ad1463f998f -http/cves/2017/CVE-2017-12544.yaml:99057c9bab3b4c0464a4f27265eeed262828d5e7 -http/cves/2017/CVE-2017-12583.yaml:1c1274d97f240ce836a71e399d32c78680e102d2 +http/cves/2017/CVE-2017-12544.yaml:bb214bdb6f7bcd786dab0a4e3ccd6ee6d9e13eca +http/cves/2017/CVE-2017-12583.yaml:4cce0d2f8ba7152921e5211b8eebc83a41e71ac4 http/cves/2017/CVE-2017-12611.yaml:ce70628eabc704e5a37751a600a47e48a9df12c1 -http/cves/2017/CVE-2017-12615.yaml:5e68486df7772601c66324f8073ea64f6fd5dc6a +http/cves/2017/CVE-2017-12615.yaml:b843dde085636d4d03de819d3082577ffa674561 http/cves/2017/CVE-2017-12617.yaml:88371be607757662bd7772addcbf1ec4ea3b1023 http/cves/2017/CVE-2017-12629.yaml:f0b26fb202887ed295965f7b28d426a8e8775833 http/cves/2017/CVE-2017-12635.yaml:87fdb9e1ae7c38640cd76cdf1f1c20e0bd72b16b -http/cves/2017/CVE-2017-12637.yaml:9c22508d7057c64ab0c8439f7ccf0dbdc55b9016 -http/cves/2017/CVE-2017-12794.yaml:dcd73805da1efc6144911bbff9475289e3db9421 +http/cves/2017/CVE-2017-12637.yaml:b3d533ddcc236a4a1900c2bccc295560b0a03fbd +http/cves/2017/CVE-2017-12794.yaml:bcf593ab47e0df48784c21a0e39ebbedbb9560ba http/cves/2017/CVE-2017-14135.yaml:4680c2870b5f367428d95d238780a6901aa0773d -http/cves/2017/CVE-2017-14186.yaml:42b364d42da51bfc5c1ebbf392c46a7fcb08e578 -http/cves/2017/CVE-2017-14524.yaml:644a0f94442d5f337f03e5f517bd96ee61f0b566 -http/cves/2017/CVE-2017-14535.yaml:7a2645a90307f9115545d45a472153ad815bee75 -http/cves/2017/CVE-2017-14537.yaml:985d0db0dd784fd12d416cd9309d8a6f8812ba99 -http/cves/2017/CVE-2017-14622.yaml:f78c93e0aced5c4a0cae1bacd8b4a2f74d86b77d -http/cves/2017/CVE-2017-14651.yaml:c0d0aa444c26be6d43c9f20bf30fba9d6129528a +http/cves/2017/CVE-2017-14186.yaml:125065889ddae753c8af255950a23d5f07396b00 +http/cves/2017/CVE-2017-14524.yaml:7ddeb6de8ae7842c3032452450754bc8d78a69f9 +http/cves/2017/CVE-2017-14535.yaml:5197ce58cf4e697ffac8bbe7fff8ec9d83cdc917 +http/cves/2017/CVE-2017-14537.yaml:a16467613483a3b8c9409e2f34da34f9e2adbc89 +http/cves/2017/CVE-2017-14622.yaml:f1638dd15300e9aa595d0403a801a6d0978bae3d +http/cves/2017/CVE-2017-14651.yaml:2409cc80e248787e166531ac5568558752fafacd http/cves/2017/CVE-2017-14849.yaml:03c0c0eef0a97a6b380a30f3345c66cc81491664 http/cves/2017/CVE-2017-15287.yaml:aa2f3c3d5788dbac0cd84261379fe8c07144edff -http/cves/2017/CVE-2017-15363.yaml:ab9a53f79e3d18129f3c7b58010d2e8b1cdf9d53 -http/cves/2017/CVE-2017-15647.yaml:5a4046f465bde3e0746937724cefcf7bfccb4e91 +http/cves/2017/CVE-2017-15363.yaml:34f257ec1ffbe7eef42054c3eed91345245009e2 +http/cves/2017/CVE-2017-15647.yaml:3fd60e90e942f063b328fcc8162dc03d7b1f2eca http/cves/2017/CVE-2017-15715.yaml:62e23a19330d7270d69ed133c5d8181e747468a7 http/cves/2017/CVE-2017-15944.yaml:df29201a118ccbd218e550383d9cdf02c4858b65 -http/cves/2017/CVE-2017-16806.yaml:938d679990b67e000f82dc51dd7576601a137757 -http/cves/2017/CVE-2017-16877.yaml:28bfe611705c1ea03c2ac5a729ec19ab7be7c823 +http/cves/2017/CVE-2017-16806.yaml:ea06685e3c3cd8c341aed916bb9d4f6c9cf6be3d +http/cves/2017/CVE-2017-16877.yaml:9f93919347931b5294546d4691e1620ca331ab1b http/cves/2017/CVE-2017-16894.yaml:d15c14fe912020b969b78484fa2fb74a84f78394 -http/cves/2017/CVE-2017-17043.yaml:d13bce25aadd7623bcf504da18314d448bfc1fd9 -http/cves/2017/CVE-2017-17059.yaml:8964ae2d781bf1146d9a5cb05a1497e250376352 -http/cves/2017/CVE-2017-17451.yaml:540a3a3cc9f04b74681b30c3d5d5d793dacfd763 +http/cves/2017/CVE-2017-17043.yaml:29f8903f31d9683b8dece7c4d1f62969ab7e3d15 +http/cves/2017/CVE-2017-17059.yaml:3465e923f25bcfed2b242dbdc38083a3379323dd +http/cves/2017/CVE-2017-17451.yaml:fbea2de6d734b756a920a5529bdad9fbf15bba3c http/cves/2017/CVE-2017-17562.yaml:1f8ab84b5cb798379473669339c1a5502d132d6b -http/cves/2017/CVE-2017-17731.yaml:dca7ae080e8a334f1430735f033ec6ca0bab8a64 +http/cves/2017/CVE-2017-17731.yaml:02cd4e80e5c84283964398a8f4da76730ca97b8b http/cves/2017/CVE-2017-17736.yaml:d5cbbd2c446093d06f1569d6b4023ce38add564a -http/cves/2017/CVE-2017-18024.yaml:aef2330e7ad774c0ba7c1ed92e8ac57d7ca42c11 -http/cves/2017/CVE-2017-18487.yaml:f88f4ca1afbd507f360b91eaa7fb1249c058bb32 -http/cves/2017/CVE-2017-18490.yaml:9d16093854dbe3852ec42a04f0d2cb3b62876b13 -http/cves/2017/CVE-2017-18491.yaml:b9f6d3662fb94207204ed7d6b24f85ed4fdfcb4a -http/cves/2017/CVE-2017-18492.yaml:e016c19c1996b6c22b8b91c2cdaf304909e4a731 -http/cves/2017/CVE-2017-18493.yaml:2becc675bc6a1e322ffc1c7a32ed4b8168644d73 -http/cves/2017/CVE-2017-18494.yaml:a991b9646e1897a189637cf2d588cb7d28424cb3 -http/cves/2017/CVE-2017-18496.yaml:9c3640b0c31a656fe115ce0b11c242b304390eea -http/cves/2017/CVE-2017-18500.yaml:b4935d4a2f54ef2aef6374957b675abb381be0f4 -http/cves/2017/CVE-2017-18501.yaml:8730487bf34168c2924902d72da825bd94aad611 -http/cves/2017/CVE-2017-18502.yaml:4710bfce8d57b65f8ff6148faed9ab785d101b0c -http/cves/2017/CVE-2017-18505.yaml:b249f39e317e6b1570b5d9ec491970d895f4657b -http/cves/2017/CVE-2017-18516.yaml:a36f66f4f7747e8ab0b18e1d4c2866a6a5e34780 +http/cves/2017/CVE-2017-18024.yaml:677ac77abb3b80dc1aa1ff2de12947f5d20e1d73 +http/cves/2017/CVE-2017-18487.yaml:b39a9b390b9a6860d571b7976e0c5d2dbd6d8063 +http/cves/2017/CVE-2017-18490.yaml:9d15d99646a116b15be5c119f7aa12f9e65a8019 +http/cves/2017/CVE-2017-18491.yaml:20d1b9ba2ecd36e3a50e54f36504a1ad3940ad89 +http/cves/2017/CVE-2017-18492.yaml:eb7b313d2018f165c474f4df4c98842ea77ca1ad +http/cves/2017/CVE-2017-18493.yaml:0887660643a63fa291134b30986635429f31d734 +http/cves/2017/CVE-2017-18494.yaml:81a3866658a6571bae01ebb60e58a3f428399276 +http/cves/2017/CVE-2017-18496.yaml:c9872fc0aec183590ffcc45d721b0618c4986f4b +http/cves/2017/CVE-2017-18500.yaml:b237c3a468988a2206b49002f6e227d7bb836967 +http/cves/2017/CVE-2017-18501.yaml:0bc2cc6a5ab1099ee40412394d947fcfc6014bcd +http/cves/2017/CVE-2017-18502.yaml:b93c2fd814b68d0a46997f2eef320c64515a1e47 +http/cves/2017/CVE-2017-18505.yaml:5affe9e4316d3785bea381e199dde42e141c8df8 +http/cves/2017/CVE-2017-18516.yaml:1c6f7e060361b945ced3ab89cd5266e331186b75 http/cves/2017/CVE-2017-18517.yaml:b2f16128e5224d560c438776df3d1feea6ebcf10 -http/cves/2017/CVE-2017-18518.yaml:9433868e6137dc7188bba89a60b1e1efe87674fd -http/cves/2017/CVE-2017-18527.yaml:1cf1d37b7d9a049891cdbe6eec33a12a1ffef3f5 -http/cves/2017/CVE-2017-18528.yaml:05d67da143727e4d2c619560bca37742d4f11b1c -http/cves/2017/CVE-2017-18529.yaml:b6d3607b8965e924984e888999a0c99ad5ff52d7 -http/cves/2017/CVE-2017-18530.yaml:d6335048b26e606231d2584daa76a41e669b2702 -http/cves/2017/CVE-2017-18532.yaml:1f78e233bee2b0ce5d7ca2811d4e8ad6bf854056 -http/cves/2017/CVE-2017-18536.yaml:5e61067b5fc310f609112f008714e8e123283e7e -http/cves/2017/CVE-2017-18537.yaml:355b7b92239e5e3ccc752d706de8f5c1a0e48d48 +http/cves/2017/CVE-2017-18518.yaml:7f9b0e9ed736167246c916798588ea3e29175aad +http/cves/2017/CVE-2017-18527.yaml:2beaf1571e91c4b0a65aa5d201839048027e37b3 +http/cves/2017/CVE-2017-18528.yaml:6c7f420030ede31df2e793d0e2da988d465405cb +http/cves/2017/CVE-2017-18529.yaml:96710c830aa19bfb17b215a976020f14b48388b5 +http/cves/2017/CVE-2017-18530.yaml:3e79db675c709e59d601bc63fec299a4994a5e65 +http/cves/2017/CVE-2017-18532.yaml:db23ed137f08cc6ba1a782734289be08d29a06d6 +http/cves/2017/CVE-2017-18536.yaml:caff5a717b203e1f7109d7c2e007af82ce82f9c4 +http/cves/2017/CVE-2017-18537.yaml:f4775a0b35216551d240cfb4eb99957a234a35f4 http/cves/2017/CVE-2017-18542.yaml:b71b8efc73c95461b121b69290cf1fba4f1924fd -http/cves/2017/CVE-2017-18556.yaml:08ab903562df644fbee89f7aedd6a10f85bc5d00 -http/cves/2017/CVE-2017-18557.yaml:091dd4a687156cea31a7be5b92b8ac73245028d7 -http/cves/2017/CVE-2017-18558.yaml:6693ec9e8af385341a9f44a9a9a13aa5b43aa33e -http/cves/2017/CVE-2017-18562.yaml:bb98ad4ea98897f931163f7319d734c8ca278354 -http/cves/2017/CVE-2017-18564.yaml:1c9bf50932f5296c79db323b42eb1713b5c68d9b -http/cves/2017/CVE-2017-18565.yaml:434b3348cb3a72135121baf385045d3ebe9ccde8 -http/cves/2017/CVE-2017-18566.yaml:aad3aae00f7801b046ef31f41f0a25ea526454d5 -http/cves/2017/CVE-2017-18598.yaml:b803e69a0471465e5cbb8886c68a8ed70fb0eb38 -http/cves/2017/CVE-2017-18638.yaml:f624bcb5b646649c62809506a1f28985fc9443a0 -http/cves/2017/CVE-2017-3506.yaml:b3faff5d371e88666a2f32e7f226daa97d158b4e -http/cves/2017/CVE-2017-3528.yaml:c85b149ce629378e588cdfa40cf377968ad30a36 -http/cves/2017/CVE-2017-4011.yaml:f012a0f94967809eaa8ea9e17966545f7d5eae91 +http/cves/2017/CVE-2017-18556.yaml:93d3279ac0231bf968a64a551156f98cdd4f44be +http/cves/2017/CVE-2017-18557.yaml:a2089697c9c306847057eba1edd0bf4c4b0824cb +http/cves/2017/CVE-2017-18558.yaml:1b09a534dec3156105e78bda21ac3191f7074e8a +http/cves/2017/CVE-2017-18562.yaml:ebe62654d0e274ed8fbbb26cfcd2f2c967635715 +http/cves/2017/CVE-2017-18564.yaml:570d86009975edb3d8142466f22053ea3fa06e0a +http/cves/2017/CVE-2017-18565.yaml:2007ce67927b111d7ddc7ebc10a638193c930da3 +http/cves/2017/CVE-2017-18566.yaml:e0f95b3867742050725915d4b6ab1931a53206aa +http/cves/2017/CVE-2017-18598.yaml:c2c17682491ab7e9bd6ffa57fd090d115a60e134 +http/cves/2017/CVE-2017-18638.yaml:5829da4cd0815cf6a36d66c321096a07b5e2a892 +http/cves/2017/CVE-2017-3506.yaml:0c2e8acc6501bf3deab4b51ac45ea6254b6bc627 +http/cves/2017/CVE-2017-3528.yaml:8c653c2d64f33a82acae8c6ff828c8ec3669cf23 +http/cves/2017/CVE-2017-4011.yaml:8327f2b88e70580c894077f6f91f51e3696e3e6b http/cves/2017/CVE-2017-5487.yaml:e3c4d5d07d6553434dea8ec6471b010166a8cb22 http/cves/2017/CVE-2017-5521.yaml:14a4604827648a67fe559fdf94fb0d226eec71eb -http/cves/2017/CVE-2017-5631.yaml:ecec93533df59b9d652650dd95d5bd91fcf8ac04 +http/cves/2017/CVE-2017-5631.yaml:a838958e909a692dc2164b7d92a23970fdb51a14 http/cves/2017/CVE-2017-5638.yaml:2fab0cabc54d3d0eadf470c978bff699cb0f104f -http/cves/2017/CVE-2017-5689.yaml:eb49becef77048df6f697fef22fb37a06f375192 -http/cves/2017/CVE-2017-5982.yaml:6654b09e0bd08a2f1d698f4a74bcc4675b1805b3 -http/cves/2017/CVE-2017-6090.yaml:ea8529495dc2d55056838344c21a114e7e9282b6 -http/cves/2017/CVE-2017-7269.yaml:2b14774d2a6ddcf6e489526d531ebea88648f026 +http/cves/2017/CVE-2017-5689.yaml:4bebb899ab471bd2b82540dd602b29bf5e0b95d7 +http/cves/2017/CVE-2017-5982.yaml:1fd805c6228f13752ca0280118487b32bdd5d665 +http/cves/2017/CVE-2017-6090.yaml:1eb225d00f423ddc18cc585ff1ed43a8bd8b0eeb +http/cves/2017/CVE-2017-7269.yaml:2a7a47f1fc486077924214af6b16d81311ad720c http/cves/2017/CVE-2017-7391.yaml:7fb8a06032866f7bc69478e0725d8e125713ab92 http/cves/2017/CVE-2017-7615.yaml:0d75df4aa032315a2a75f29547eeac33a2b399b7 -http/cves/2017/CVE-2017-7921.yaml:a3a2277d0b76e4f31f8385697a26b6d615cfa556 -http/cves/2017/CVE-2017-7925.yaml:2f4a1aef9b177bb932f1f79c2c466905e13db27d -http/cves/2017/CVE-2017-8229.yaml:3b63a5a8c92c19f30deced3e51974d9c2edf7fb8 +http/cves/2017/CVE-2017-7921.yaml:a0affdec432fb0ca83a8da8fbe68ec1e73142709 +http/cves/2017/CVE-2017-7925.yaml:986c6ff8a6990936b0ccc611b381fd2290d38258 +http/cves/2017/CVE-2017-8229.yaml:c70a151e019ada53f96311317228698b8aab5547 http/cves/2017/CVE-2017-8917.yaml:182a6118794019322adb0bd1299f3fe344e71cc7 http/cves/2017/CVE-2017-9140.yaml:9b5a9b093ad629a5da404dfc3355712398407eb0 -http/cves/2017/CVE-2017-9288.yaml:47324c152336a52678afafec523b71421d0be6e8 -http/cves/2017/CVE-2017-9416.yaml:28600dcd6045cf5f2cbfb2cdba422cec9410a2b9 -http/cves/2017/CVE-2017-9506.yaml:90af36ee05d0a253dfe6828f2792eadbb553877f +http/cves/2017/CVE-2017-9288.yaml:46d393bb228f7340555c140f4a7f7583085833aa +http/cves/2017/CVE-2017-9416.yaml:79c3c62caacab70b9839fe57e23ac26fcbf98f6a +http/cves/2017/CVE-2017-9506.yaml:514f7bc2e83cadc5963aae4f15d6ce59a28c6d34 http/cves/2017/CVE-2017-9791.yaml:78f4e7cc235fdb88d45b32837212f30126cfa7e0 http/cves/2017/CVE-2017-9805.yaml:d643e257a4c7d456394ec38c83851f386574a76d http/cves/2017/CVE-2017-9822.yaml:fa5c44b2d54a956a4f6cb3ce60f5d0d7e6cedee6 http/cves/2017/CVE-2017-9833.yaml:77fe94cade448e27152c0527d5ab0bcb6638fe9c http/cves/2017/CVE-2017-9841.yaml:fec714f868006623c03bf97e800d9d68a2aa57aa -http/cves/2018/CVE-2018-0127.yaml:4a132660cd42709f1dcb4ce082d8d10abce5484e +http/cves/2018/CVE-2018-0127.yaml:39b071fce56177745e250cfdd3226288e1eb08dc http/cves/2018/CVE-2018-0296.yaml:907606fc9cb6cd891a19e846437a121a87d33302 -http/cves/2018/CVE-2018-1000129.yaml:5360a07f9e50ffb79c942f84501d2a03dd81edfc -http/cves/2018/CVE-2018-1000130.yaml:5187da4f5072efa3d34a34cfcfd6bff0f4928f7d +http/cves/2018/CVE-2018-1000129.yaml:1c0923a63a3fe4aced0fb3c8e8c0c71b0e48ecab +http/cves/2018/CVE-2018-1000130.yaml:b1ebd8f751b521594d56973c7e5f2128d253afb1 http/cves/2018/CVE-2018-1000226.yaml:c281c617a4958f9f577b7b20f3fd3161100f0d89 http/cves/2018/CVE-2018-1000533.yaml:3f0b1ecdd84904c2beab2df673293a512cc9ebbc -http/cves/2018/CVE-2018-1000600.yaml:2e9d9cbde963c85750b674176a6d73e4700af5b6 -http/cves/2018/CVE-2018-1000671.yaml:26a8e33d536314a885921d791b14b3210fd35fd3 +http/cves/2018/CVE-2018-1000600.yaml:546d6572421d37b2dc2bb3a424772a5ae6b82aa6 +http/cves/2018/CVE-2018-1000671.yaml:b0d4d8b1fa7b9639e598e211a7c949c9b0fab068 http/cves/2018/CVE-2018-1000856.yaml:f98ee2b47adadf0f1d06e202f5922c9ef821dc3a http/cves/2018/CVE-2018-1000861.yaml:e056a4efd3d7c61bbaebd3fafac70d4400c498db http/cves/2018/CVE-2018-10093.yaml:f71f5ee5a973b1ac8a2ecc2a920c5b67f55a6a9f http/cves/2018/CVE-2018-10095.yaml:69bfe5c9b65fb9b5bbdeffda3d4126d16e7b9c74 -http/cves/2018/CVE-2018-10141.yaml:a53b89496d564060e1d05a40d41e4eca7b536b95 -http/cves/2018/CVE-2018-10201.yaml:4961cc75beab4d4e9299c29f68ecc3ab4d82976a -http/cves/2018/CVE-2018-10230.yaml:9b193a84c5122932034614a4bb5306a57f8c0b78 +http/cves/2018/CVE-2018-10141.yaml:db8d58c726933ca951de9545955d2d6996b72120 +http/cves/2018/CVE-2018-10201.yaml:512bd42f6820d1f98891790035048acdca56adc3 +http/cves/2018/CVE-2018-10230.yaml:510d8243602b2956eb90b3aabe8737e9ef5c317f http/cves/2018/CVE-2018-10562.yaml:a6abf4a359a96cfe5b80159369887bd028a62911 http/cves/2018/CVE-2018-10818.yaml:a7fa0aec3caa627fe454421831f62bc991eed9d6 http/cves/2018/CVE-2018-10822.yaml:52a53b5bbc51de2904bf467116303551b4eb91f2 -http/cves/2018/CVE-2018-10823.yaml:306f514d3139f8fa14f114c8edf0c73473318cf8 -http/cves/2018/CVE-2018-10956.yaml:b9d6d72b58c6d66d61b3a84d461503ebb73624df +http/cves/2018/CVE-2018-10823.yaml:14d4c629c9f17e2fcb1141390df5a1f7243506d1 +http/cves/2018/CVE-2018-10956.yaml:b95cda77218b9e381b7257e11629f5f59762b266 http/cves/2018/CVE-2018-11227.yaml:b3f5f051b483f432d3370de5a63d8a158c0a51b0 -http/cves/2018/CVE-2018-11231.yaml:26a811ff4841d789c97f5b5d9b9708ddea926f27 -http/cves/2018/CVE-2018-11409.yaml:3c584a1bcae61762277534830b8b10fbc6538c6c -http/cves/2018/CVE-2018-11473.yaml:3df131f997e074c988b615d5e2ae8115c9ba239a -http/cves/2018/CVE-2018-11709.yaml:2e93f8934237f33c82952f3aa94be2325f9153ca +http/cves/2018/CVE-2018-11231.yaml:fedcadab8d9e30a7046f09698e3c428de9b013e0 +http/cves/2018/CVE-2018-11409.yaml:727ea02fc26013a14e36a6b9056c025917f022df +http/cves/2018/CVE-2018-11473.yaml:d194576782828b3918ee68a7ccde851aba7a822b +http/cves/2018/CVE-2018-11709.yaml:01a1b9f0d6242f0d65ae55f0488a3502891e9aa6 http/cves/2018/CVE-2018-11759.yaml:573cd6fe1d72830c97517ab93d097e5833f018b9 http/cves/2018/CVE-2018-11776.yaml:7541001116d345ab9ef0cac69d0655ca83e106dc -http/cves/2018/CVE-2018-11784.yaml:25c18388d73b989b4973e73b78fc4390b0e4d25a -http/cves/2018/CVE-2018-12031.yaml:04bd073e79dfdbfb617d09985764aaf29790b516 +http/cves/2018/CVE-2018-11784.yaml:9c2f1fc6d20b81dc4391931411ad52a48ad83c1d +http/cves/2018/CVE-2018-12031.yaml:35d8361cc5a7f6c0b1d4e2a220edc57d2332396a http/cves/2018/CVE-2018-12054.yaml:0ea810d624d2d9f60c877860e30fca8d81a07b25 http/cves/2018/CVE-2018-1207.yaml:3927dbb0bbdb0a644ad741802d42ea31204b4058 -http/cves/2018/CVE-2018-12095.yaml:b162f91d54ed487cfd64614d94b70c0ce7fb3525 -http/cves/2018/CVE-2018-12296.yaml:f1e4965e449f7ebb45ca56b7dc58c45e6e92654d -http/cves/2018/CVE-2018-12300.yaml:0b04d906a25dce588f44f6f255f001728b22f3e8 +http/cves/2018/CVE-2018-12095.yaml:84efd3f5b97511f08af4f7134e0c47ee43d37bd8 +http/cves/2018/CVE-2018-12296.yaml:e229c62e697fff78eb2a44a1a87b5e59d7b88d89 +http/cves/2018/CVE-2018-12300.yaml:f19b6b9ba02e58e547cac878841286a60512f10f http/cves/2018/CVE-2018-12613.yaml:3b75c4b71dc48053c4b3091ced2861c745be7772 http/cves/2018/CVE-2018-12634.yaml:e1dbf53cdbc3e88a680d78991ba7b91536732a89 -http/cves/2018/CVE-2018-12675.yaml:8dba3321267bb7f7fbf38d3889411d9202e90123 -http/cves/2018/CVE-2018-1271.yaml:72274bd7764c375d80d1cdc4ce819376993b6756 +http/cves/2018/CVE-2018-12675.yaml:59d45637218042202b0fce5933b1b74be36640df +http/cves/2018/CVE-2018-1271.yaml:b681daffb3efc17327ecbc1de179132b98a5a470 http/cves/2018/CVE-2018-1273.yaml:a82e8aebc5d7a3b5751b7ed03c8520fbf1b5248e -http/cves/2018/CVE-2018-12909.yaml:a4173b1c14806f7e6569b697dbb0e1b372e9e30b +http/cves/2018/CVE-2018-12909.yaml:b6a747cf8c6004b6509737bdf966f99c626a91bd http/cves/2018/CVE-2018-12998.yaml:4251b09ac2382e3813de29ffc6265f0668cd29c5 -http/cves/2018/CVE-2018-1335.yaml:1cdf76cc829e7b950ef6d2e96b8a37a463532a7b +http/cves/2018/CVE-2018-1335.yaml:8913a725cd1ffcf32cd95e03ec88454f7cf3c00e http/cves/2018/CVE-2018-13379.yaml:5221ac2b530b9bd8de4aa7348901dd8ca118f416 -http/cves/2018/CVE-2018-13380.yaml:6e5179b92dc30247309d8f97778fd1de78277232 -http/cves/2018/CVE-2018-13980.yaml:e1c63817ace22e7e4dc70449318b97ec521962b4 -http/cves/2018/CVE-2018-14013.yaml:9c77bc8860435eebb2abb04622a54ada10452cb5 +http/cves/2018/CVE-2018-13380.yaml:0750d2c4ef2286cfb43fbb5eee8afe5cd52c904b +http/cves/2018/CVE-2018-13980.yaml:834f3b3eb58a6c15a4b271a2583688016c6f3cf1 +http/cves/2018/CVE-2018-14013.yaml:7b6f25461ac4f5bb5e8ee96ca82b93003f74e9ae http/cves/2018/CVE-2018-14064.yaml:a2f2731e6e69aa2b322a00917e6f1cfc4de72726 -http/cves/2018/CVE-2018-14474.yaml:3506c8b6dc1eef341d43bd433a2c5b07992c158c -http/cves/2018/CVE-2018-14574.yaml:8822f9e51bcc716fd51d84b4291f85fafeef2b0d +http/cves/2018/CVE-2018-14474.yaml:e112b38c60cfc652874403676858197196f20dc4 +http/cves/2018/CVE-2018-14574.yaml:252d6d602159a58ac7332d350775e140909392d0 http/cves/2018/CVE-2018-14728.yaml:2d78ae5ca02e800c088789a376d6b816fedfac15 http/cves/2018/CVE-2018-14912.yaml:82ed5b4c174af10f4b0fcb0767c0881ba35c01fa http/cves/2018/CVE-2018-14916.yaml:e8036396c68ecbbd712a3e2e9e1be23422e3250a http/cves/2018/CVE-2018-14918.yaml:8776aaeebbc82b381827f291f5ccf9e6329191c4 -http/cves/2018/CVE-2018-14931.yaml:1daf2650f1e20c16acf2b9af262e1dc5ed640f07 -http/cves/2018/CVE-2018-15138.yaml:dc154aa1f481db25da65f43dfb6461a3f540b481 +http/cves/2018/CVE-2018-14931.yaml:60cc5a6b8f1597609e928e4719ad67efa3279827 +http/cves/2018/CVE-2018-15138.yaml:6c0493a203e12018b794131ccb85ed1ca0948b09 http/cves/2018/CVE-2018-15517.yaml:fec1315c3ca6011bfe23f981ed46434ec3702e6d http/cves/2018/CVE-2018-15535.yaml:5a5d130c1e74142fdc26197ac4293ec3f983cfb7 -http/cves/2018/CVE-2018-15745.yaml:cd6c530fb4b445e2b91fa1e8c64762cb351aeadc -http/cves/2018/CVE-2018-15917.yaml:ba97b3e5efe1242d03f80b8cacccfc8b2d060917 +http/cves/2018/CVE-2018-15745.yaml:a90697a2582b01f92386082a42d931e124118443 +http/cves/2018/CVE-2018-15917.yaml:2d2fabd7d33d0f0c7f24be2987eca2fd01cda07e http/cves/2018/CVE-2018-15961.yaml:c6d6d1e1a44dbd2bf75e260c1741cce01dcc58ae -http/cves/2018/CVE-2018-16059.yaml:6e14b66e9cdedb5b02845e84657407fe0ae15115 -http/cves/2018/CVE-2018-16133.yaml:0b6e6e861b32e5377ccfe24fdd320ab31f9cc647 +http/cves/2018/CVE-2018-16059.yaml:502731c7efe2f5d1116a531f0111eac957d74ea1 +http/cves/2018/CVE-2018-16133.yaml:46953b60de853202614f3dfdfa62faaa2efcc51e http/cves/2018/CVE-2018-16139.yaml:97f39c6c97eed643bfc9fc7f6b8dcd92c82e1d6c -http/cves/2018/CVE-2018-16159.yaml:f7e562eb64bff345055cb49c9e4679830247a68c -http/cves/2018/CVE-2018-16167.yaml:4e8df956dbe720d98b98149e6029ac85661003a5 -http/cves/2018/CVE-2018-16283.yaml:2f22eb2d5c2416a01baff00236b3c928e8c0c65e +http/cves/2018/CVE-2018-16159.yaml:99b135a372d9874b52718f3c32daced2b8d69df1 +http/cves/2018/CVE-2018-16167.yaml:3147e193af600854dcabb860ed5084e4b1aadcf2 +http/cves/2018/CVE-2018-16283.yaml:265994ebc9992efa921f0a9478a2410c335c0d5a http/cves/2018/CVE-2018-16288.yaml:3e7800cabcace98a19d34bdd2bc6c79d5da4d9f7 -http/cves/2018/CVE-2018-16299.yaml:79d0e97cb6254eae07808def19478aa70ec1d3ca +http/cves/2018/CVE-2018-16299.yaml:d1d69cab1f7fb4e1033e94ef346537632bdcc248 http/cves/2018/CVE-2018-16341.yaml:0e46eee24d582952eee8b66879b5817147e220ce -http/cves/2018/CVE-2018-16668.yaml:bc0b7e59709515148c44333a126b574d454eb0aa -http/cves/2018/CVE-2018-16670.yaml:d280582c7ce90abdd58eff1ba904a37ceee8d00d -http/cves/2018/CVE-2018-16671.yaml:3f1802050a5cb6bca43d16d0c7579442f65948de -http/cves/2018/CVE-2018-16716.yaml:f3c81f994749d1fe1d48ae9327988f747492c56b -http/cves/2018/CVE-2018-16761.yaml:871d96e57f6b2d8ac948afdb34f2c6b7c17b29e7 +http/cves/2018/CVE-2018-16668.yaml:c135664dcaa6d42aa0be6803821dbb288f1e2294 +http/cves/2018/CVE-2018-16670.yaml:b208c95c8be15f38c6d49dd0b343305dbb164902 +http/cves/2018/CVE-2018-16671.yaml:3e41126bb6515e9cc8765cbfe23880a8431a521b +http/cves/2018/CVE-2018-16716.yaml:3f1822fe37c8c5e8d187f72b5c0852ae604b5d09 +http/cves/2018/CVE-2018-16761.yaml:0db5ede4056f20ac8200fcbf42699555e32e1cc4 http/cves/2018/CVE-2018-16763.yaml:abc09f153893ff357c66d0e81387a577c56c5d2b http/cves/2018/CVE-2018-16836.yaml:3f28c708a6ccd3842165c2bea38e19a9f5c2bd40 -http/cves/2018/CVE-2018-16979.yaml:8c8a2fc61ce7768a2c7c7baebb314e4fd17fb8cf +http/cves/2018/CVE-2018-16979.yaml:e91ad4b3fdeb449de7627b8388ba61119ceb663f http/cves/2018/CVE-2018-17153.yaml:3ba998e5197e0aa3d05f573daaf154855887387c -http/cves/2018/CVE-2018-17246.yaml:347da1a920dd1ed19b29e269f49b47858eda8f7c +http/cves/2018/CVE-2018-17246.yaml:a0794890ada9e49bf14616fd1fe702780235abc1 http/cves/2018/CVE-2018-17254.yaml:0442ff022202570dc404539bc639f17dcdad86a4 -http/cves/2018/CVE-2018-17422.yaml:d9b81049aa71a1956f785bfa08850d7eca4b1e56 -http/cves/2018/CVE-2018-17431.yaml:01dd1e1618a2ca175b3c59d5a486a3452b831a7b -http/cves/2018/CVE-2018-18069.yaml:48b776d4806a4770fadc4e07e837a4c6aacc377f +http/cves/2018/CVE-2018-17422.yaml:84f56a0b1a69217d887d0649798228a208432185 +http/cves/2018/CVE-2018-17431.yaml:79dc307b0c4356666d30a2b610d3af3010a61270 +http/cves/2018/CVE-2018-18069.yaml:7a89f11daab93c2783783555eef2064914dde337 http/cves/2018/CVE-2018-18264.yaml:bdd184c4100811e6da0665185adde7a88b252a9f -http/cves/2018/CVE-2018-18323.yaml:f4ad87c6fc9b543f6ca516ab977e31429fe946b5 +http/cves/2018/CVE-2018-18323.yaml:744c129419a26e2be4e7a1bd97d8ba84a0d19d36 http/cves/2018/CVE-2018-18570.yaml:d0486ec979e9680161feb31bc90a392387c47ab0 -http/cves/2018/CVE-2018-18608.yaml:7ce9ca8f7192932c31509ad98fd84475de64b1dc -http/cves/2018/CVE-2018-18775.yaml:87973811f5565f941e54f3a41de986363e0dd86e -http/cves/2018/CVE-2018-18777.yaml:cbb54402f96f002a73e70f184e906ff25a8fd1d7 -http/cves/2018/CVE-2018-18778.yaml:1111c9b4a1bb30acbe2284fb9728c821013a5f3a -http/cves/2018/CVE-2018-18809.yaml:852bc9e5e5b435862fd57058f834c769650c5d09 +http/cves/2018/CVE-2018-18608.yaml:1ca23c4037448b00f27aa02ff52632a9a01ff6bc +http/cves/2018/CVE-2018-18775.yaml:5fc4c05650acf44aee47d1048e78821ae44494cb +http/cves/2018/CVE-2018-18777.yaml:1ae5a44c84d1283213d839ee4d6db1fc77d206cf +http/cves/2018/CVE-2018-18778.yaml:57a65b762deadda87dc3f5a9a24602580119f3c2 +http/cves/2018/CVE-2018-18809.yaml:6a5aaacd1acccb0e0368df4495a7582649514297 http/cves/2018/CVE-2018-18925.yaml:97047f3e9d5a38b03e313feb07a4e4a868dd18de -http/cves/2018/CVE-2018-19136.yaml:b1f7e2c0e68daae18b1425ac03a04782b380567f -http/cves/2018/CVE-2018-19137.yaml:53790b1b75b5258bed460c526dc447d7123d563d -http/cves/2018/CVE-2018-19287.yaml:4510a55bfafa0f9e57e6225ed5c58a4501043574 -http/cves/2018/CVE-2018-19326.yaml:d11eb937590327e7fb7d8f3e6b73d8dfa421e613 -http/cves/2018/CVE-2018-19365.yaml:6f766456a29896324ebb48d89568dc9fc7242bc9 -http/cves/2018/CVE-2018-19386.yaml:73131cd2518e322eca8ea15291fa1a41477623ed -http/cves/2018/CVE-2018-19439.yaml:2e50c9383f32925ab38d281a1dfad41e65770f3d +http/cves/2018/CVE-2018-19136.yaml:8af861c3d9da80c8081c216dcb9ff8cacff00ec6 +http/cves/2018/CVE-2018-19137.yaml:c4f958bdc0b10f753f8748d59dd1a5d180c7f087 +http/cves/2018/CVE-2018-19287.yaml:bfe852c8b0f40dc787e6108c534b7809bddc150d +http/cves/2018/CVE-2018-19326.yaml:a99bd791b3fcab259aa3dfafc70216846c74ad6c +http/cves/2018/CVE-2018-19365.yaml:21bbd8487e2ea70c763f1c9dc40f1ddbfd979424 +http/cves/2018/CVE-2018-19386.yaml:85a41172f8aa2ba913ca08f5fb4ba38fa4925f1f +http/cves/2018/CVE-2018-19439.yaml:269df5b48b5775ad9cc09d9cb10bf0c6e796e66c http/cves/2018/CVE-2018-19458.yaml:2dfc66274c76d02f8b7f38c99ea002b0f1ee4f20 http/cves/2018/CVE-2018-19749.yaml:86e7db61f0146e8241f13a207470b9ec17e2bb6e -http/cves/2018/CVE-2018-19751.yaml:56fcf182a3f5e5d61279f7b97d17ebe3cddbf963 -http/cves/2018/CVE-2018-19752.yaml:5a694d18ca9c91b9c6be2b1bdc86bf0503596b50 +http/cves/2018/CVE-2018-19751.yaml:020ca66fe909419520ef642ce023cb68c4ea2dbe +http/cves/2018/CVE-2018-19752.yaml:ec6fbfa59abd57cd5dcffd447bf8bbf17fae8545 http/cves/2018/CVE-2018-19753.yaml:910d5c32eecf0e8bfd5f98bc32c564b4c00ff854 -http/cves/2018/CVE-2018-19877.yaml:06b332383ae405334483e962868c9591c1dc8443 -http/cves/2018/CVE-2018-19892.yaml:1ed24ce4772806e458157fb40912eece549c25e0 -http/cves/2018/CVE-2018-19914.yaml:1dc2b614c478b63a7387abdcff87189d0856b5d4 -http/cves/2018/CVE-2018-19915.yaml:ae9dc3feee20d32d3bda556e3a57952cab15a345 -http/cves/2018/CVE-2018-20009.yaml:0b4fc4e7173bd0da8406757f3c671bf39591cef2 +http/cves/2018/CVE-2018-19877.yaml:685b105a6c8559677a9330b4086279880c7152b2 +http/cves/2018/CVE-2018-19892.yaml:4769556e14c8fbfd3e18a480e52bb8d11e34350b +http/cves/2018/CVE-2018-19914.yaml:2d573406ad1d8d55fbbfb929a4ec2bc3c74f4495 +http/cves/2018/CVE-2018-19915.yaml:aee99381ebad46f23cf37b1620bb4436f7366748 +http/cves/2018/CVE-2018-20009.yaml:d5475e79a6d2bab97f23cb73ca3fb828a809cd16 http/cves/2018/CVE-2018-20010.yaml:0ed8849a7dd793404481c55adaf947ee1088c704 -http/cves/2018/CVE-2018-20011.yaml:2a8eedcfdf8929813c4e5a732e0fe7e174da0c1c -http/cves/2018/CVE-2018-20462.yaml:2703259738c69f27db7b674df63d3a981ec93a38 -http/cves/2018/CVE-2018-20463.yaml:1664fa126040fd189f9439974546fc22fa498d97 +http/cves/2018/CVE-2018-20011.yaml:e14cfc583cc02c1cf601c29fc6e41beddf88dc89 +http/cves/2018/CVE-2018-20462.yaml:a646b2f8c2dff4ce00c5327fa63fc0217aeed0a4 +http/cves/2018/CVE-2018-20463.yaml:01763242945ec48f7f3e4ba27f772a29fe93684d http/cves/2018/CVE-2018-20470.yaml:d36ea4a647162ac4ba520c9ecff4375e66784cb6 -http/cves/2018/CVE-2018-20526.yaml:b0b8eaf17f26b6ca6dc5bca178e15e4066170e86 -http/cves/2018/CVE-2018-20608.yaml:ba06e32a10cbd347fdc154254d629a5aba53fcd3 -http/cves/2018/CVE-2018-20824.yaml:eb08e7e1f58ef80c0beb2f9920d924230a563897 +http/cves/2018/CVE-2018-20526.yaml:6faec1f269ce4509464394acc54ea1eaf7734f08 +http/cves/2018/CVE-2018-20608.yaml:68fa3b101af716c3a0ae754e5a7b4d37e32365f2 +http/cves/2018/CVE-2018-20824.yaml:a2061ec04cc2affe0fdf29aca712cb696a11b4c6 http/cves/2018/CVE-2018-20985.yaml:f2e478ef663184098852d1e57f8b3bb143d3ae21 -http/cves/2018/CVE-2018-2392.yaml:aa359e1bf56b1e35c24def4b1da5a12da9b7df73 -http/cves/2018/CVE-2018-2791.yaml:ee4f8aeb488424830a101383356ac95ffc775aed -http/cves/2018/CVE-2018-2894.yaml:db3a28b4e727e9edbaa0a347dbd1cd4b09b1d306 -http/cves/2018/CVE-2018-3167.yaml:1c6a3cf8706661c929e1b96ecfd24ac7cf58be01 -http/cves/2018/CVE-2018-3238.yaml:56b8f8a2dda4f94fe066bcfdfaafe3f19d56f8df +http/cves/2018/CVE-2018-2392.yaml:6f99b1e5a3da6b350dc7f94edccea19e1238ce4a +http/cves/2018/CVE-2018-2791.yaml:bf2a710faadd5e691e9d86ecc790975ebd9caa97 +http/cves/2018/CVE-2018-2894.yaml:25aa37eee5a13d691357284a51d458095e4ab390 +http/cves/2018/CVE-2018-3167.yaml:f0ce18fbe88f5566500761beeeee9ae3dd537c28 +http/cves/2018/CVE-2018-3238.yaml:5dba4ba0995daa2443148b62e53c6e5dce168616 http/cves/2018/CVE-2018-3714.yaml:cf5d9f8db3b1ba24eaa8f321e961ef7a9777162a -http/cves/2018/CVE-2018-3760.yaml:358545eaee5aff9fa20d041f81d42d1056ae767b -http/cves/2018/CVE-2018-3810.yaml:ab3bda89fec9518c8c9851d5a8bf255b026030a8 -http/cves/2018/CVE-2018-5230.yaml:0a7638485f86a71cfa188f42585ad401c254c965 -http/cves/2018/CVE-2018-5233.yaml:dc98788e596a64dd478baaf40f361d5aa817ef96 -http/cves/2018/CVE-2018-5316.yaml:6945b9df7425d45bf33a40ad6f7dbfef1f55707c -http/cves/2018/CVE-2018-5715.yaml:e82e7b663e7c688f6646bb7fbf06d315c389b954 +http/cves/2018/CVE-2018-3760.yaml:4b568fcbc607216c6ad1d7b2a05dd0eb0fc7df3f +http/cves/2018/CVE-2018-3810.yaml:ea03d69ce1ae8af5b8110c28f1fac3ae3fe0b540 +http/cves/2018/CVE-2018-5230.yaml:cda23b55e8a61b1fbe2d5c5318e67ef9f8c7df76 +http/cves/2018/CVE-2018-5233.yaml:1ad97efe843f054865f288d08e8547311b25168d +http/cves/2018/CVE-2018-5316.yaml:ab42c4944b0010b5cf991e73779c10cf11db7f42 +http/cves/2018/CVE-2018-5715.yaml:57da76bc2e77ae5a2724ac8041924e0d5e546e53 http/cves/2018/CVE-2018-6008.yaml:481794edae79bfcf7945946da4e002d75d6c8a65 -http/cves/2018/CVE-2018-6184.yaml:5cb484d711ca4011a163a9972c90e3ef5ea87537 -http/cves/2018/CVE-2018-6200.yaml:294982950a0c9323c44448dc47a3204888b835c5 +http/cves/2018/CVE-2018-6184.yaml:98553dad17732dcdfb7f09323453b67275c54882 +http/cves/2018/CVE-2018-6200.yaml:ae49ff562be19902a8cc05dd44966cd86c11e15a http/cves/2018/CVE-2018-6530.yaml:25c3d45c8290a331fd55fced8d79364ec44304d6 http/cves/2018/CVE-2018-6910.yaml:4a2f18065f1e5f38253fd04235a6d63241887cce -http/cves/2018/CVE-2018-7251.yaml:daee9bdd4bec25271a570acdc898bcd2c62665cd -http/cves/2018/CVE-2018-7282.yaml:ea6fd6df2a60a228cde308dade122558ac404c0a +http/cves/2018/CVE-2018-7251.yaml:8acb3ccc729239aa8161a08239cfe7d536ade732 +http/cves/2018/CVE-2018-7282.yaml:27ec4ce497b05e72dda2cf8e1434fcc90e64482b http/cves/2018/CVE-2018-7422.yaml:60d4a0c8672cc2c2bd0165cd41ee1af4497ced1b -http/cves/2018/CVE-2018-7467.yaml:a01fc74a27b5d0b25896a4e40d6050c2e7efe87b -http/cves/2018/CVE-2018-7490.yaml:0f671e767ab206c123a0ef3939f01e1248187fa2 +http/cves/2018/CVE-2018-7467.yaml:890b939e307ae60443080295592747a3ddeb925a +http/cves/2018/CVE-2018-7490.yaml:82921c44c2e75cf88f383308d9ce15c7b0e89ef6 http/cves/2018/CVE-2018-7600.yaml:5e15828558c4bf70c009a2dc78c6d52c997bec06 http/cves/2018/CVE-2018-7602.yaml:92775acf744915ddde86e6c09d167db85e8d61e0 -http/cves/2018/CVE-2018-7653.yaml:6a7de49f1e8747167b5220b0c27a0c6203bc2237 +http/cves/2018/CVE-2018-7653.yaml:301999cec5044517f17069c1f8d70210ab12bffc http/cves/2018/CVE-2018-7662.yaml:b51c897df5660c5286768fd6eb2791f6edb150c3 -http/cves/2018/CVE-2018-7700.yaml:a3c861fe35fae8a83393e2758884e672783ebe4a +http/cves/2018/CVE-2018-7700.yaml:6acee66ef7def1b5c23986e6d124e2afb846fb5f http/cves/2018/CVE-2018-7719.yaml:e0c8eb68df8a6102ef4dfac99627268da5fdeeee http/cves/2018/CVE-2018-8006.yaml:052b8571c39bbdaf9b7854f1a3409c6947bcd431 -http/cves/2018/CVE-2018-8033.yaml:bdd4b2ad777cfa553ac0b77fac7b48fcee375d72 -http/cves/2018/CVE-2018-8715.yaml:1be34cb912d1710a1d468bde696f417ab95e5d50 -http/cves/2018/CVE-2018-8719.yaml:976729305250a9d4d96d33430e62f049409bd858 -http/cves/2018/CVE-2018-8727.yaml:f7c45f542c5f0cb51f83060cfe04dc169d51377d -http/cves/2018/CVE-2018-8770.yaml:0887f79145c007b84c0139ee6355f4804aa5df4c +http/cves/2018/CVE-2018-8033.yaml:f7f196d67aa994c130f8b262f0926575c6b0db83 +http/cves/2018/CVE-2018-8715.yaml:cceeac0cfeb2bf19f245f930b7bc2a5623e4a3d3 +http/cves/2018/CVE-2018-8719.yaml:581f847019aedd8e1d3ed13f7884906cfa85076d +http/cves/2018/CVE-2018-8727.yaml:2d4036f57018b38cd0b50ecdc05326b5e420c110 +http/cves/2018/CVE-2018-8770.yaml:0dbd8bd2339aec8a3c60ccd768e069e1ce179691 http/cves/2018/CVE-2018-9118.yaml:3b29f7c83757a007a3d265dc7f5b5678c5e416f1 http/cves/2018/CVE-2018-9161.yaml:22e9b8bbc0514f502e22609016c730fc5c819c27 -http/cves/2018/CVE-2018-9205.yaml:47aeaec0ad76b4cee9ea369cc0c6e91229cc000d -http/cves/2018/CVE-2018-9845.yaml:c3d73bfc395da3557dedbdbcba13a1dc668487a7 +http/cves/2018/CVE-2018-9205.yaml:38aba152490c45cb1005072781441e6a6ff5c004 +http/cves/2018/CVE-2018-9845.yaml:e3befbeb8130dac412f7fac0f5e099cabfc07f35 http/cves/2018/CVE-2018-9995.yaml:abc349a7dd64a5b25b67de4fe2ff177dbc946c76 http/cves/2019/CVE-2019-0193.yaml:d6f834be45a4511ea6b598acf08f099980a53574 -http/cves/2019/CVE-2019-0221.yaml:28c5225f9d0f702bee13f8b10b0c16e4ef450866 +http/cves/2019/CVE-2019-0221.yaml:f4d08fbb2acfeca72b3ec911ed8d5f277f0711ba http/cves/2019/CVE-2019-0230.yaml:0ee7ef7bcf2d5820e9ce8e610a9d871e85367d42 http/cves/2019/CVE-2019-10068.yaml:88d07427e0aba4471d00c0c4baf91f3a60dac4a0 -http/cves/2019/CVE-2019-10092.yaml:4cb75d0b8f2c64d61ca657d2bbea0ba75d45ef71 -http/cves/2019/CVE-2019-10098.yaml:2ce59e96d637392439bd79fa7264cca1939373f4 -http/cves/2019/CVE-2019-1010287.yaml:e522e3378a7b3e4a264eff891d85e8375df4a526 -http/cves/2019/CVE-2019-1010290.yaml:a76e65423a9328136b62cb0bb38f2314cb3e0060 -http/cves/2019/CVE-2019-10232.yaml:7fb8875479587ff27f68d4c371a006e673fa99db +http/cves/2019/CVE-2019-10092.yaml:5f5306537ef83c8b33f38c0b87da44dceb5e5777 +http/cves/2019/CVE-2019-10098.yaml:d00a9f769bf1ee05810118e4dcf27ab50861ca72 +http/cves/2019/CVE-2019-1010287.yaml:5cc8f7994873b88123c4a072ecca81125d586fd1 +http/cves/2019/CVE-2019-1010290.yaml:13a1ed9401f7afbc21bbeabd91dbef4a410d7ef9 +http/cves/2019/CVE-2019-10232.yaml:1743503e806079a5bd227702f28133a4293c84ab http/cves/2019/CVE-2019-10405.yaml:b5daeec3f62d211e5b02dd583a9e57434a892d98 http/cves/2019/CVE-2019-10475.yaml:b67f84d324c06ddfe0aa7f46eee362155aee3eb6 http/cves/2019/CVE-2019-10692.yaml:b5e7d0a0c60b4558346be19828ce69e18a42f2f6 -http/cves/2019/CVE-2019-10717.yaml:d1ca53124fc3216a0296c8489844a01f4788248c +http/cves/2019/CVE-2019-10717.yaml:8addc58a7caf2f3051c6072d33309dddb0715454 http/cves/2019/CVE-2019-10758.yaml:bc3c031b6ff7fdd0eb1cf23ec3d21b7e872eb490 -http/cves/2019/CVE-2019-11013.yaml:6f24bbf2eb5727e01ffaeee1225b080022201178 -http/cves/2019/CVE-2019-11248.yaml:01f1d8b6b4f4950e5e84e9d4c6ce505ea693ca6c -http/cves/2019/CVE-2019-11370.yaml:bb589f72268651e68df74f26c0574d92d721bb7e -http/cves/2019/CVE-2019-11510.yaml:7c37f47a91c1407703c9d250f67f6a4f314234fd +http/cves/2019/CVE-2019-11013.yaml:a3bc6b74d261267a7b610dafe984067b6c779267 +http/cves/2019/CVE-2019-11248.yaml:5e44147ddb208f6e6aad82c55118efabf4332156 +http/cves/2019/CVE-2019-11370.yaml:9dd491498b49dcf0e822f03a48062c1430c5a627 +http/cves/2019/CVE-2019-11510.yaml:4b7f22871c4802c379add6ba585b414ee185366d http/cves/2019/CVE-2019-11580.yaml:583171e2a1be653c0d0a49b9a7d2dcb7a927d14b http/cves/2019/CVE-2019-11581.yaml:bf460611dbc143a6c36432cbceef601f2a0af0e1 -http/cves/2019/CVE-2019-11869.yaml:a76e8cd082e7d75937d0de5e0f0de3960c394fb0 +http/cves/2019/CVE-2019-11869.yaml:44fc0eb2056130f5905e4c7775cac05291584bfe http/cves/2019/CVE-2019-12276.yaml:e0e3f6d5bc1e5199fffd965f4cbab2de3b90f187 -http/cves/2019/CVE-2019-12314.yaml:1d6402fca8cdaed7373e84b75da3a73f3a432c51 -http/cves/2019/CVE-2019-12461.yaml:12c50ab8c569b2ab55776be0301d746fbeae8875 -http/cves/2019/CVE-2019-12581.yaml:c1713716d7a9e2f32831972ca4286651096e4685 +http/cves/2019/CVE-2019-12314.yaml:ce127e1333483c02157aa3d2427a57832bc0f006 +http/cves/2019/CVE-2019-12461.yaml:1634d9d8bd838ea910ea1f201f626fdbd285eb6e +http/cves/2019/CVE-2019-12581.yaml:43074546f1a143cf4e6159857600fb4659777479 http/cves/2019/CVE-2019-12583.yaml:293f771c45a7698c52e0415b02237cc3f9bfba77 http/cves/2019/CVE-2019-12593.yaml:9afe8005862bbd62c5db3517429fb196c6829d15 -http/cves/2019/CVE-2019-12616.yaml:5cff26eb362d1b765e283aadd11d503a754031d0 -http/cves/2019/CVE-2019-12725.yaml:4770069c682316544fffd7511fe07aa03a3d03cc -http/cves/2019/CVE-2019-12962.yaml:275e2b0ad1dea104ec9ccdf5972d81698b5e8abb +http/cves/2019/CVE-2019-12616.yaml:18dc7fb768f292978cb6dad15e9a697328f71dc0 +http/cves/2019/CVE-2019-12725.yaml:72d495f266fcf34c8dd664201b09c157b9675b92 +http/cves/2019/CVE-2019-12962.yaml:b00e7062c351def37f0811ed1bb86564912d1f87 http/cves/2019/CVE-2019-12985.yaml:094b871b30c660f5ac3a8556b05545d4cdf7c4fe http/cves/2019/CVE-2019-12986.yaml:8678d4a5b0a8868400e708ce7bf067ea7a80f3c4 http/cves/2019/CVE-2019-12987.yaml:80b781abac2809e27b433768aac9877f12115562 http/cves/2019/CVE-2019-12988.yaml:dcad6a5b8882a8d7542736278e4d1aaa94fa0a0d http/cves/2019/CVE-2019-12990.yaml:03944aeaec23e42a990314fc4bb45486fb007934 -http/cves/2019/CVE-2019-13101.yaml:77b7422cf29278d3666209fd27f7d46cef727c49 -http/cves/2019/CVE-2019-13392.yaml:2d4a1a3aa981e67f5e9d82d5a6c0d99134dba793 -http/cves/2019/CVE-2019-13396.yaml:651fcb3a392c63f0a81271fd9824d322147c3492 +http/cves/2019/CVE-2019-13101.yaml:cfd954812cb9d85b441c41bda4c3684636621d0c +http/cves/2019/CVE-2019-13392.yaml:9cb40b4677d80d1ca7e7832515d0aca6d053f6a1 +http/cves/2019/CVE-2019-13396.yaml:463b0f45175c1f67e61d66e675ed2f8eef3af2d8 http/cves/2019/CVE-2019-13462.yaml:def0ad1ff8a4fbb64f75400fbbd0071e9a2d82d7 -http/cves/2019/CVE-2019-14205.yaml:7d43fc327fa04437243d610c63516402290e28a4 -http/cves/2019/CVE-2019-14223.yaml:64c1fa0ce72c40bfc6917eee506cf914c88905dd +http/cves/2019/CVE-2019-14205.yaml:cc4be522419235d6b6205d88d46bf108dc0361be +http/cves/2019/CVE-2019-14223.yaml:0a7839b5d6fc7c7a0f43812a005761c2dbc47f43 http/cves/2019/CVE-2019-14251.yaml:0cc9dd712d21b2241af8b0f0d2b186c7fe9bcb19 -http/cves/2019/CVE-2019-14312.yaml:938842be83935667cdbc466466fb64a12aebdfee -http/cves/2019/CVE-2019-14322.yaml:f69011a1cae7629f30c39afcec3da82ecba2dda9 -http/cves/2019/CVE-2019-14470.yaml:2fffb23f325d84a5e4f7772d5405b66a4fd68adb -http/cves/2019/CVE-2019-14530.yaml:c8f0d3ed0b0cf83f86b96b1956abf69d17c2a9dd -http/cves/2019/CVE-2019-14696.yaml:acb64af48f7ea7546fe8cbd89b546306f4b44201 -http/cves/2019/CVE-2019-14750.yaml:8c54a10c7e0b898a037bf91caf27ecbc6abfcf59 -http/cves/2019/CVE-2019-14789.yaml:46c9a03c7600456a43e15de98b4ee065b52f4fca +http/cves/2019/CVE-2019-14312.yaml:7355d740ef605e88b0cdea0cdf1e851e49101994 +http/cves/2019/CVE-2019-14322.yaml:6ac788f571c481ef17c463f780b901a887b3a0e3 +http/cves/2019/CVE-2019-14470.yaml:cd209846adc72e8a2d2bdf81bfd23f2b5076ab13 +http/cves/2019/CVE-2019-14530.yaml:bb23e6cfde17e5b60420addf8c7a8194d155d0b4 +http/cves/2019/CVE-2019-14696.yaml:015630de8071835ac48a599f4f623eb045921794 +http/cves/2019/CVE-2019-14750.yaml:ed3a58a8c2da0859b00fdabf2961dbde5a85a021 +http/cves/2019/CVE-2019-14789.yaml:550ceeb3f3dc890af0c159468264d80a01f61d11 http/cves/2019/CVE-2019-14974.yaml:25c085f35de44c9186283cc81b3a44905f43d8b0 http/cves/2019/CVE-2019-15043.yaml:1ca4b021588004f462e2cdef2957265cc87a7a8a http/cves/2019/CVE-2019-15107.yaml:c6c9f1a7c80c4f01b885e9db6d6921d767fb4e60 http/cves/2019/CVE-2019-15501.yaml:be9601e8f03c00a6342f66abca79fd6da5542f75 http/cves/2019/CVE-2019-15642.yaml:47b4ec16ac5406a4a6e4bb9fe119dc2677c54a3f -http/cves/2019/CVE-2019-15713.yaml:03f75bd1427559beeb48acab1f8f928eb0f2167a -http/cves/2019/CVE-2019-15811.yaml:1cc3223f4feadb6f03693bf16e422f2cd8715426 -http/cves/2019/CVE-2019-15829.yaml:9c1c3673546446ad0d0d170b10c0d740c98a209f -http/cves/2019/CVE-2019-15858.yaml:c52ed88849288245511d4af56c27f4fef971cebb +http/cves/2019/CVE-2019-15713.yaml:a891a5d9c1a4bd07088f700e26fd4c95cc7154f9 +http/cves/2019/CVE-2019-15811.yaml:3dbd46a0a4405d1ca3eda581b67c4734fd9479d0 +http/cves/2019/CVE-2019-15829.yaml:4647c5d79c09a9fa9384a995e2f1ecabf419b68b +http/cves/2019/CVE-2019-15858.yaml:a5e3a005c45c9c7fa514772bca6b84183efc0df3 http/cves/2019/CVE-2019-15859.yaml:9f1de3caa593fa426e2cb333dec707b7b7320fe4 -http/cves/2019/CVE-2019-15889.yaml:8768ed7238b75ffa10501a87a5dfc7ccf47b22cb +http/cves/2019/CVE-2019-15889.yaml:a41a54d2491c94aa3dfeb848c1524eab590e141e http/cves/2019/CVE-2019-16057.yaml:84ccf733f1a9dcaf729ca4ebf8dc19b08be5168a -http/cves/2019/CVE-2019-16097.yaml:cf1653837b12d5b6ceb8fd9fd87b17d8867d1858 -http/cves/2019/CVE-2019-16123.yaml:a2c02e44e7dbe31f9bbc54c57783d2f4f7aaf182 +http/cves/2019/CVE-2019-16097.yaml:ee90ded59e45753ac17d8cebc432cf068d389dd3 +http/cves/2019/CVE-2019-16123.yaml:fb563ffdbe2f52d215706642a6e8d164f57907a6 http/cves/2019/CVE-2019-16278.yaml:29d931801dde3242e63c9f2d08fcce8dc21f1cb8 -http/cves/2019/CVE-2019-16313.yaml:3c176dd6a23ff1276c2c2b61c9fd66576be5ff42 +http/cves/2019/CVE-2019-16313.yaml:585661cbaf7d53f715a03a03fe0f383a44c2268d http/cves/2019/CVE-2019-16332.yaml:981298948149ab85e02e3ef2a0fa347cdfd1ab4b -http/cves/2019/CVE-2019-16525.yaml:1e37d8451281fac7be92bb9892fb40867b1f3df0 +http/cves/2019/CVE-2019-16525.yaml:c708f3c2fc390d2c5507ddf074e1092959cd6149 http/cves/2019/CVE-2019-1653.yaml:8b823806c9bb55cc8fd1a7d6ea251a019ba1e93f http/cves/2019/CVE-2019-16662.yaml:a328c1202c77e807fa0f68b67b9d45f391572810 http/cves/2019/CVE-2019-16759.yaml:4c0273bc52b4bacae2ef2df7e91966b9a5d83c62 http/cves/2019/CVE-2019-16920.yaml:fe61b41935e7819339a7cfb8b4a8f150d7780f2d -http/cves/2019/CVE-2019-16931.yaml:b7e2540645012767100c02294aeebc8585f2843c +http/cves/2019/CVE-2019-16931.yaml:95a089373aca17e7d7c184ffe553ef25f95e0e9b http/cves/2019/CVE-2019-16932.yaml:f95304cecc933234cec493104fc784d7a8378fdc http/cves/2019/CVE-2019-16996.yaml:faf4197a60ce145363602977bd2e8b23a549d5e8 http/cves/2019/CVE-2019-16997.yaml:33351052aa9a9dc011c5be53ef305b271835af6f @@ -1362,36 +1362,36 @@ http/cves/2019/CVE-2019-17270.yaml:297aa62d7635e7dfb9b6a26ab923efb368031ec7 http/cves/2019/CVE-2019-17382.yaml:b52bc9cf2093a0e51071445a09cacea490cd2d70 http/cves/2019/CVE-2019-17418.yaml:84aa3fb29d7f1dce7b12219def75444f7e184b43 http/cves/2019/CVE-2019-17444.yaml:201cc16e6ae9729725ea84752984ab9967cd1224 -http/cves/2019/CVE-2019-17503.yaml:a19f61668a46c266103f196926bc9ba8ae76eaa2 +http/cves/2019/CVE-2019-17503.yaml:2f817d00ee81ae1593a190226416876acaddeff5 http/cves/2019/CVE-2019-17506.yaml:79e41e34a99ac435db2fd9c9a286b82ff4554efb -http/cves/2019/CVE-2019-17538.yaml:8a0c24849ac3647dd0a8a006376cd64f44218160 +http/cves/2019/CVE-2019-17538.yaml:213f919ce445a6a2260920ed4b54c763c1c30127 http/cves/2019/CVE-2019-17558.yaml:55bfdb37ebe61fea7a1e1818e8e235c7edf14568 http/cves/2019/CVE-2019-17574.yaml:124ee76d6cbc89cbcc525dfc80da84c8797f401b http/cves/2019/CVE-2019-17662.yaml:fb138ea63216fa4a72c467b59342b02c21e2759c http/cves/2019/CVE-2019-1821.yaml:8a5778dce40bea4534c857e5f05545ce2f17dcd9 -http/cves/2019/CVE-2019-18371.yaml:16f2ecf007d3348e00095acbb8c6f07ea8cdf0e1 -http/cves/2019/CVE-2019-18393.yaml:10a464bade103f8bece198c76c2da1b68fce2bfc -http/cves/2019/CVE-2019-18394.yaml:180b93a9ddf6602a4f352d0757525d7ac458ce8c -http/cves/2019/CVE-2019-18665.yaml:7aa64e29dc4bcb40f1c8e0eeac2acf261b2d078a +http/cves/2019/CVE-2019-18371.yaml:f4c861e1d0aa23793790498bd6f8017b950cebd4 +http/cves/2019/CVE-2019-18393.yaml:5e7c5d42737ac9d3af2474406d1eb1c8912c05c7 +http/cves/2019/CVE-2019-18394.yaml:b9d03d03d802baef3d24f578d2285124515208cb +http/cves/2019/CVE-2019-18665.yaml:fb657e0ccf58edf20ea0b4566d77e98eca8ee265 http/cves/2019/CVE-2019-18818.yaml:7519db0adde6c7b1df81b5289f661d4632f8f654 http/cves/2019/CVE-2019-18922.yaml:162fbeabe24aa59bf6513e436f02443281c785e1 -http/cves/2019/CVE-2019-18957.yaml:b093c73e5dcf7660e5a7991814bb224db6a04e39 -http/cves/2019/CVE-2019-1898.yaml:d37e0887a849457c43f608767d4fa4c02288888a -http/cves/2019/CVE-2019-19134.yaml:cbcc9a1bb1f14f44646480c7dbbf6919627104f8 -http/cves/2019/CVE-2019-19368.yaml:d44c12f3204d088f8dbd386b30a579c0509eae82 +http/cves/2019/CVE-2019-18957.yaml:f914d4808532c0cfed20cfc33b09a96ec46ad1e8 +http/cves/2019/CVE-2019-1898.yaml:4527baaadf0f0cfc7ee0662e7f64bc64fd0f82d1 +http/cves/2019/CVE-2019-19134.yaml:c33edf3cf46eef35653f671c9d16de6edce9af38 +http/cves/2019/CVE-2019-19368.yaml:43c6f8ad678e2b98b05298aee060f6d96e787963 http/cves/2019/CVE-2019-1943.yaml:514411e78630be37c8b02f049419861606c45545 http/cves/2019/CVE-2019-19781.yaml:a754f0c4656e8541d5d252af720fa6cb6003058f -http/cves/2019/CVE-2019-19824.yaml:104766029b90645b05de50bc6d6867202b4fb5a1 -http/cves/2019/CVE-2019-19908.yaml:99e73b6f2e7e8a6d24a210b7f37236910ef1d371 +http/cves/2019/CVE-2019-19824.yaml:54d3e9e971f7cf7ecd6885ea6ac6b13273e79b60 +http/cves/2019/CVE-2019-19908.yaml:e8ef1a3145922d001daf1258f0d6583bbc88e4ea http/cves/2019/CVE-2019-19985.yaml:0c7c96aa5501bf1c394b2bbccff38d516063cae0 http/cves/2019/CVE-2019-20085.yaml:44b75e9538e1c8142022451f4271da55d6628f5d http/cves/2019/CVE-2019-20141.yaml:cf02ee2013db99655744e3286aa5d781ecc16f27 -http/cves/2019/CVE-2019-20183.yaml:5c1b3338912ea399f792049df34d3b6d4458eceb -http/cves/2019/CVE-2019-20210.yaml:0eb7d7dda1348925506eb531ec822396de450a5d -http/cves/2019/CVE-2019-20224.yaml:12c9c2a8e0c248000ba9637b82f262c58097f4c3 -http/cves/2019/CVE-2019-20933.yaml:aaa7cccfad0072ca9539447ce8c1736da3144a95 +http/cves/2019/CVE-2019-20183.yaml:662bfe445f30a3ba25743f2815b8fcf08b3a2d13 +http/cves/2019/CVE-2019-20210.yaml:8fbbb9dd8218d41992aa590489b8b266445a87db +http/cves/2019/CVE-2019-20224.yaml:0ffd2ceaec50ea7525807a9bbb4bd63a420f7c80 +http/cves/2019/CVE-2019-20933.yaml:8977931fb6602297b2d63c26f0ab350f81f98d57 http/cves/2019/CVE-2019-2578.yaml:ec9c04616a635c965e6aa4845287bde33132f54f -http/cves/2019/CVE-2019-2579.yaml:5f135878f502c5f71d21a0e886d9b4452c7c375b +http/cves/2019/CVE-2019-2579.yaml:2245194e9c2521acf85ec89b0ee51e74afc9050c http/cves/2019/CVE-2019-2588.yaml:d20e80f96f55358adc596d5abe0f888c537cdd29 http/cves/2019/CVE-2019-2616.yaml:49e311f6fe67768b4afded29a827fd32df9decf0 http/cves/2019/CVE-2019-2725.yaml:626c3250c69fe58e07346e20d6a2ac6a26ec3eff @@ -1399,214 +1399,214 @@ http/cves/2019/CVE-2019-2729.yaml:77b36f54d27f878224921f74773fa167e7a2b730 http/cves/2019/CVE-2019-2767.yaml:33749b1e41b6b239730112744f788f41bb3f6f0f http/cves/2019/CVE-2019-3396.yaml:760f1a2ddfea4c690636ba399af2caf83e1485bf http/cves/2019/CVE-2019-3398.yaml:dd21259a647bc3db97fa07ed92ae58e4fd18b533 -http/cves/2019/CVE-2019-3401.yaml:07cedbe98ce18d066d4fa5c1843f1aa10fcb92ab -http/cves/2019/CVE-2019-3402.yaml:3ed10c41ae44360ffc26eefd7e28ac3f0e6bbdda +http/cves/2019/CVE-2019-3401.yaml:8ac9ebdf5d539fb57b1e65ec5208f9f204f3d02e +http/cves/2019/CVE-2019-3402.yaml:baa9240ef95559a77839f059e3b0ec7862d6027f http/cves/2019/CVE-2019-3403.yaml:31d74b8aa71eccc9613514657cd6ade524c4d2f6 -http/cves/2019/CVE-2019-3799.yaml:36c937f2bcbba1945227589eb70677b9c323bdf6 +http/cves/2019/CVE-2019-3799.yaml:1f73a66a74e5671fd17de37095132a515aba2b57 http/cves/2019/CVE-2019-3911.yaml:bf2fab1ced112b14803c87c0339e7d7c262df29f http/cves/2019/CVE-2019-3912.yaml:2a76c67837a7af237689dd194d2cb9ce4ddf8dff http/cves/2019/CVE-2019-3929.yaml:36d48f0c6246c03f1c2be6baf2555eee96da0387 http/cves/2019/CVE-2019-5127.yaml:78ac2dee635da35509b8900fe277a64d6a77a384 http/cves/2019/CVE-2019-5418.yaml:dc042e32ae550d12e781f215c0df38eccd375745 -http/cves/2019/CVE-2019-5434.yaml:4d0bcd37dee24c21fa4b52bcf97f351bc372b782 -http/cves/2019/CVE-2019-6112.yaml:92b984f72d9abf74765a0be1754596d57d5f7e8c +http/cves/2019/CVE-2019-5434.yaml:0e3bc5315abd52afda9b66f3f7c4e377a4a6d9c6 +http/cves/2019/CVE-2019-6112.yaml:0c477d3e34f1d8c7e56fdf2770e65ea6407d8b75 http/cves/2019/CVE-2019-6340.yaml:051fc3558e3003c9158031b6046ee2adc633a432 -http/cves/2019/CVE-2019-6715.yaml:edc12dae9423732ed219dead74f34c446b42abf5 +http/cves/2019/CVE-2019-6715.yaml:e3f34e008e1e0b056d1f1c551ccceea5c6c874c1 http/cves/2019/CVE-2019-6799.yaml:7f85261f03d9d54e23a3b9e746577f2ef00f1604 -http/cves/2019/CVE-2019-6802.yaml:c6d8d589235096d89ec262a68f72e8b9d532717a +http/cves/2019/CVE-2019-6802.yaml:ba9b0601874a3aaa24fd68d8c2fa82e916e68453 http/cves/2019/CVE-2019-7192.yaml:a5436905cd61308de27ae60c6cd7b051f8ce011e -http/cves/2019/CVE-2019-7219.yaml:8eff99f0c2a4a1f6a47b71ae1ea35a97e86b917f +http/cves/2019/CVE-2019-7219.yaml:e8fda2bebb0e2c278ff9b66b5d163c4411ef2392 http/cves/2019/CVE-2019-7238.yaml:1763c527cbf4e3847035b556c99baf858f0ee726 http/cves/2019/CVE-2019-7254.yaml:1b6b1ea99472c5beaa2a2848ffacc054678c6ffa http/cves/2019/CVE-2019-7255.yaml:1327936e778b1e42dd2c2fb7e53c691fbd2bad91 http/cves/2019/CVE-2019-7256.yaml:7975b75ae956a21f45277877247fab747bb2aee4 -http/cves/2019/CVE-2019-7275.yaml:5486703dc814bd42236a3531804865380a681a3c -http/cves/2019/CVE-2019-7315.yaml:715d8b95f7b6babc952f63999a5d70cf3b7fd352 -http/cves/2019/CVE-2019-7481.yaml:bc861d3bd5c3b1d22a36d1c9d7eacaff29230cc3 -http/cves/2019/CVE-2019-7543.yaml:af45ca486f4a90ff659ad910245a0ca6881fed31 +http/cves/2019/CVE-2019-7275.yaml:d98abfca1454bfe3b331738e38d9f5e4ac9d72f2 +http/cves/2019/CVE-2019-7315.yaml:43203c61c07e802cb7acfe5ccc8d91f700d66e0c +http/cves/2019/CVE-2019-7481.yaml:41a23dff22e69e1a473f29f55b9cbd9d71e6ca14 +http/cves/2019/CVE-2019-7543.yaml:a35c81744d44d76f50b665144407cde97d29b4f3 http/cves/2019/CVE-2019-7609.yaml:0a0f0094d2ea4ed78e81c1779dbd8ea22ac3547c http/cves/2019/CVE-2019-8086.yaml:0446bf2a769363e307df89031c326c44a027b079 -http/cves/2019/CVE-2019-8390.yaml:a82fe803591812c0bb48938e6801cc48efb179fa -http/cves/2019/CVE-2019-8442.yaml:93f6589d9c11e3c0628a04fc5b7794fa6d020b21 +http/cves/2019/CVE-2019-8390.yaml:d7cacefd2c3ca4960ce21cc3d4ad5c34d14a83e0 +http/cves/2019/CVE-2019-8442.yaml:a5a3cfebb336d8a17002f857f322c7b46b9657bd http/cves/2019/CVE-2019-8446.yaml:e4812ee63bc006979a32c4382109de2e213439b2 -http/cves/2019/CVE-2019-8449.yaml:86d2016e3434db2862ef17a39d9f00627c05433a -http/cves/2019/CVE-2019-8451.yaml:b92a61d6ee4c12fea7d202b32c48efd1a91a129e +http/cves/2019/CVE-2019-8449.yaml:37c3d7f0b328558b442da32da47b0c344f696484 +http/cves/2019/CVE-2019-8451.yaml:352a28f69628ae90c4226975dba401a52e73451d http/cves/2019/CVE-2019-8903.yaml:13948dfd9d370e39af234c2f9c7707050b9ffdbd -http/cves/2019/CVE-2019-8937.yaml:689efd996bebb60f224e4aaf5c87dc86e096dbab +http/cves/2019/CVE-2019-8937.yaml:4fcf2572f34613914382d6d2fd52d86d9780d7d0 http/cves/2019/CVE-2019-8982.yaml:d1e39acd42acc40eafe8be947f0970857dfa0c6e -http/cves/2019/CVE-2019-9041.yaml:016f7f82df99ea91face45c3c795b2b6983b055a -http/cves/2019/CVE-2019-9618.yaml:e98d7abda5c6ee6237c43fc027465e5d092cbe07 +http/cves/2019/CVE-2019-9041.yaml:6bd88176a1e1ce38ce0cb5da3729c64148cec7b5 +http/cves/2019/CVE-2019-9618.yaml:f638ed80d7837312adec3a4a042e7bf36fcdf7ac http/cves/2019/CVE-2019-9670.yaml:2425319f91a77465f1ab81dfeecd456eac09809c -http/cves/2019/CVE-2019-9726.yaml:a3cf86d7a5346bd694d7003737fc590694755987 -http/cves/2019/CVE-2019-9733.yaml:d965e53a104af4b62f6571cf0f17543bd7c89ca9 -http/cves/2019/CVE-2019-9915.yaml:900eb173f3435b8fc7bee8686cd29732d125c4ef -http/cves/2019/CVE-2019-9922.yaml:eae51d174d83730591ee504b4792474e0f1bcc3d -http/cves/2019/CVE-2019-9955.yaml:812065d7b21a8e1955bdadc2e6883a92a7d5ae9e +http/cves/2019/CVE-2019-9726.yaml:1d465c3b06fc841f45e661f8c7d9360f522baafa +http/cves/2019/CVE-2019-9733.yaml:cc2ded2b1fa540e8cb99ae883e9bb22eecdd3281 +http/cves/2019/CVE-2019-9915.yaml:4f8a33a077b5079ca7b457989e666f92ac3c8160 +http/cves/2019/CVE-2019-9922.yaml:9c384494ede346f6c4ed1f58525e772867be964c +http/cves/2019/CVE-2019-9955.yaml:2a4f86a8156e960d475384a5c48aae7220b3672f http/cves/2019/CVE-2019-9978.yaml:820fc5f4b1c19968c2138582d50067c51cd1a36e http/cves/2020/CVE-2020-0618.yaml:21928ac3433823410e7898cef5fbaa8f7f5ab018 -http/cves/2020/CVE-2020-10148.yaml:5ee9a0276c8722c1fffb3d53e8206409f74ebbbb +http/cves/2020/CVE-2020-10148.yaml:4396daae0f3525e5325c42fb859391037d2e0f3a http/cves/2020/CVE-2020-10199.yaml:d81cc3347a29b260e9f929f7b1a7c592d6e90f2f -http/cves/2020/CVE-2020-10220.yaml:1d204044ae2e279086d92ff32f07ec972c43cb06 -http/cves/2020/CVE-2020-10546.yaml:93f20b0902a0091ffd4943086823e43276dbfabe -http/cves/2020/CVE-2020-10547.yaml:3c910de9390d6f9e1ff281c2af157a7a9f7b647c -http/cves/2020/CVE-2020-10548.yaml:c587350fb6607ce7e694cf3a5ed1e510ad6b306e -http/cves/2020/CVE-2020-10549.yaml:7d8ccad9b3ee781c1488eca8c1b5c18eed23b39e +http/cves/2020/CVE-2020-10220.yaml:9cc324322b72efbc0144ad50f39569d6a8982060 +http/cves/2020/CVE-2020-10546.yaml:0f91f63815f59cf3db4c184d3eff1600841fc37b +http/cves/2020/CVE-2020-10547.yaml:2875d4a9d475450a2f7d6d865644733fd349bb6c +http/cves/2020/CVE-2020-10548.yaml:872b935ce6d3ebd2b4fe4bfaec4c05f3b34195de +http/cves/2020/CVE-2020-10549.yaml:99b477575e480164f9a71eaa5289c1d92afccee3 http/cves/2020/CVE-2020-10770.yaml:3cbd1af38c685fb4ff0646ac2b6cc81f64eac44c -http/cves/2020/CVE-2020-10973.yaml:ffbc8dc69866e4ce94b1320e5a4758108018f0b4 -http/cves/2020/CVE-2020-11034.yaml:e9d099cf840241deaa125a6ef4327041158e699b -http/cves/2020/CVE-2020-11110.yaml:f67af77c4894902d687f732da1d5ca6e0c17feb8 +http/cves/2020/CVE-2020-10973.yaml:92f91bef0f68d4363d3fb52c74611f247654db07 +http/cves/2020/CVE-2020-11034.yaml:84e1e21b3d1e855a60d1ebbd053d221bedb62b85 +http/cves/2020/CVE-2020-11110.yaml:f0ce3f6ffe8cf2e326e80389fe1ac1d972f493cf http/cves/2020/CVE-2020-11450.yaml:a5476030004a50b2ebaead89f1f47a7a28521d9f http/cves/2020/CVE-2020-11455.yaml:3cb98871d35bdafb0545798f99b8992b782f4775 -http/cves/2020/CVE-2020-11529.yaml:cce004a5232811837dfed23ca65d8fff500c2c2c +http/cves/2020/CVE-2020-11529.yaml:9325fb680ad7864f12f7628852341ab8a7aafed1 http/cves/2020/CVE-2020-11530.yaml:b5a6cc432593fdc5fea37a356fe193a5fe9c0723 http/cves/2020/CVE-2020-11546.yaml:0ca0ee1f3daca47fcaea3352fb34640ec8c65846 -http/cves/2020/CVE-2020-11547.yaml:c5921192498efe3710b8c94bb63f0b33c27ee288 -http/cves/2020/CVE-2020-11710.yaml:8ed6d681a4463d9f0524509d670dee7fc11f54d0 +http/cves/2020/CVE-2020-11547.yaml:158d68c7e3691d5080c7504a22e08f8035bd8d36 +http/cves/2020/CVE-2020-11710.yaml:4752f9abdd304c9441c1e153a2b98704875cca43 http/cves/2020/CVE-2020-11738.yaml:6edb95b0b62eebf3f2fab4e96a36c683b704b719 -http/cves/2020/CVE-2020-11798.yaml:87d4a002b252e2814dfa742fb251fb0c2aa738cc -http/cves/2020/CVE-2020-11853.yaml:d292bd10f62989c8192266576dcd5480219c2ca6 +http/cves/2020/CVE-2020-11798.yaml:9a2692829013bf54d76157b4476d3259bee71dd3 +http/cves/2020/CVE-2020-11853.yaml:cbd63d41e59a3093dd8d6cea35cd90885a0a30e0 http/cves/2020/CVE-2020-11854.yaml:eefd8dc48440801baadaf64f22d0c68f1d1bafc4 -http/cves/2020/CVE-2020-11930.yaml:b0af7bf8515945f5f652199a9f6109cf11decf28 +http/cves/2020/CVE-2020-11930.yaml:c7d90581e5433d01eb5adf2c693697e1ccc8bff7 http/cves/2020/CVE-2020-11978.yaml:2def250eddcd1f653191496f273b8785ed248d04 http/cves/2020/CVE-2020-11991.yaml:fb2710f6d070e2b200cb3974c047d1029b0213f3 -http/cves/2020/CVE-2020-12054.yaml:fb9eeab9876bd4129956281e47277230bf4bc47c +http/cves/2020/CVE-2020-12054.yaml:7f5945a57b2407ad4a3f7867cef008f7db79b9a5 http/cves/2020/CVE-2020-12116.yaml:14d41e92efe9d2f9af6a0eb713b00a0276004973 -http/cves/2020/CVE-2020-12127.yaml:4862e7dd2ea835a59094d7f86c48753136ff7a16 -http/cves/2020/CVE-2020-12256.yaml:0fdbbe0e9b5ed14b261feea382d4adc7bdeda3e2 -http/cves/2020/CVE-2020-12259.yaml:064e0604859c0aacc6fb93ada959004adc952f80 -http/cves/2020/CVE-2020-12447.yaml:d2a63d2d079b2069035cbc336fa2a5128b78f59e -http/cves/2020/CVE-2020-12478.yaml:417e9bd1b95df2599f4af235f17448955acb4158 -http/cves/2020/CVE-2020-12720.yaml:daba355a7f40c210500d4d10b0395b8c6371edba +http/cves/2020/CVE-2020-12127.yaml:01c8ed9883ba5319ddc2a447cabe719c791e3414 +http/cves/2020/CVE-2020-12256.yaml:4e1f19ae0a6a3f7b15c827462b22293763bea717 +http/cves/2020/CVE-2020-12259.yaml:b8056e83d71f1c543c96303ff0416df1bec5101b +http/cves/2020/CVE-2020-12447.yaml:7b5cd620dbb5f65a5100f800a07442f3a0e0916e +http/cves/2020/CVE-2020-12478.yaml:2e3528c7a2fee03928741a0f38df93b085ff7ecd +http/cves/2020/CVE-2020-12720.yaml:ba763052e6b21b44ec9e2e97ff80adf29fb2c17e http/cves/2020/CVE-2020-12800.yaml:8405d99f05bcec64599153252b44f34b599a9d99 -http/cves/2020/CVE-2020-13117.yaml:26bcdcfe877c25ff10dfb457fa46da4cca9205b5 -http/cves/2020/CVE-2020-13121.yaml:aabde40a662820666b5029da1888664a3680ea44 -http/cves/2020/CVE-2020-13158.yaml:15e7931eec4a72b9b037494c64fee0b087ee34b3 +http/cves/2020/CVE-2020-13117.yaml:d20de3a478f88f33dac8224d60ab2317138f9eb1 +http/cves/2020/CVE-2020-13121.yaml:84b49c9338f423a6837c5ba1f8ad43992adb53a3 +http/cves/2020/CVE-2020-13158.yaml:efb613f16816a6f941d07ae0e532c9926da1551e http/cves/2020/CVE-2020-13167.yaml:440b1360e3ad2c24a02eb5809cc988bf347dddb7 -http/cves/2020/CVE-2020-13258.yaml:fc2bef7d4c40f5e1f4894eb88c670e23e7f91065 -http/cves/2020/CVE-2020-13379.yaml:734e4f6df3c3ce676608605856dfbd393e2da5bc -http/cves/2020/CVE-2020-13405.yaml:12612c355594439a5493aefc64fa9a7bb821640e -http/cves/2020/CVE-2020-13483.yaml:d961de9f918aa496ab225aa3a7afbece6f6e3d28 -http/cves/2020/CVE-2020-13638.yaml:b0ed3c2312b6ea3bdad625d2e3d6a094e72fb4d1 -http/cves/2020/CVE-2020-13700.yaml:3e0d427fd6f9a5bb02e875f06dd598f7d8d5ba4b +http/cves/2020/CVE-2020-13258.yaml:3609c036162457f6a79a61651d324d1ab7045d46 +http/cves/2020/CVE-2020-13379.yaml:9b316fb63cc4b70225d229d3350aa17f9fcb0b2a +http/cves/2020/CVE-2020-13405.yaml:0c6f99d9fec867e8f13a0b6d219cf10067f6a3e1 +http/cves/2020/CVE-2020-13483.yaml:b8e1fed7b0ca575f6aa0663ef5e6a11b20c564b1 +http/cves/2020/CVE-2020-13638.yaml:58d39413250c24ec226480855d3bc8fe6bee0ee6 +http/cves/2020/CVE-2020-13700.yaml:79345c0cb928a3045e64dbbf3c98aac81fe4f7ef http/cves/2020/CVE-2020-13820.yaml:31f591fa6002c390152e3667bb0fcc3be6af6ba6 http/cves/2020/CVE-2020-13851.yaml:77a880efdf4f26a66e894d20766a401c94fca379 -http/cves/2020/CVE-2020-13927.yaml:4e87d52a16c5d86c546bd4a19fd6dd30c89e0ccd +http/cves/2020/CVE-2020-13927.yaml:6c7e1fcd986ac373227baa32ed892c22e238e2e9 http/cves/2020/CVE-2020-13937.yaml:d097db656991b4eaca9479e76b3496e2d66d4356 http/cves/2020/CVE-2020-13942.yaml:f46dbac1b19d3d0704c07e9ad991000a4b75d56e http/cves/2020/CVE-2020-13945.yaml:5174d14f64a0120ed2ecb3fcfb84ae2f82faa632 http/cves/2020/CVE-2020-14092.yaml:81f2bc62a3660d02f3165cee851acc1b52005b37 http/cves/2020/CVE-2020-14144.yaml:760b8410c371d224c68d29447a0df34c9c898e93 -http/cves/2020/CVE-2020-14179.yaml:9afa9676b79811f7342dee17cc1cd7737d4fab3a -http/cves/2020/CVE-2020-14181.yaml:75305c20ad7f5f4dc1b575db23739ee11cec07a3 -http/cves/2020/CVE-2020-14408.yaml:e3df31ead9ce0dc1490f0303b8c5b22e18c0cf1e -http/cves/2020/CVE-2020-14413.yaml:ae28326a85965e57f39123be13c4d3b3f3a59759 +http/cves/2020/CVE-2020-14179.yaml:5f4fff2134a826239dc685effe437d4dc78e8243 +http/cves/2020/CVE-2020-14181.yaml:d32a845c2949cc67f3b570fbebaf12f8cbaae68e +http/cves/2020/CVE-2020-14408.yaml:f5830e4dadc91047967b283b1512d031c869bea6 +http/cves/2020/CVE-2020-14413.yaml:c6bd21d74be6c22b7cdc6bc90e01f138fab9d3d8 http/cves/2020/CVE-2020-14750.yaml:b58847df77744b48e066cb62a7c4071017a066a2 http/cves/2020/CVE-2020-14864.yaml:0b78fa47330760f36a2e88fdc2b7170ada7cadac http/cves/2020/CVE-2020-14882.yaml:f8043278b5bf1cc6abae310594cc2c4163aeeaf9 http/cves/2020/CVE-2020-14883.yaml:f4a45aa963c7afded6c5eb5de007aa038c03f2e6 -http/cves/2020/CVE-2020-15050.yaml:5f852c4e3537c01ff62e607a41f3607726ce689a -http/cves/2020/CVE-2020-15129.yaml:1f8289eafa1cd04bf4172be566d101b2d2ccc353 -http/cves/2020/CVE-2020-15148.yaml:2eb6a5daef1e998a2292e598228d8450862ba060 +http/cves/2020/CVE-2020-15050.yaml:7011dc567e51428005cf508b1e9d5b554614f3be +http/cves/2020/CVE-2020-15129.yaml:43c612e64e885964616db2e045ee5c9c62c5b3d6 +http/cves/2020/CVE-2020-15148.yaml:0587d09091ce40270157a33a8d75d9af841f7202 http/cves/2020/CVE-2020-15227.yaml:0a6893704e43389f4e4bb783684483eedee66219 -http/cves/2020/CVE-2020-15500.yaml:574c1038ae4cedc8a390c50c551c20ea31e19159 +http/cves/2020/CVE-2020-15500.yaml:cbbb3a7755393a1762c42fedc06a8b49f67e9de7 http/cves/2020/CVE-2020-15505.yaml:dd7edcc9a9186e8cc7f33bfabf111083bd06676e http/cves/2020/CVE-2020-15568.yaml:3e17a21cc9d9a1a88b3a1f02921130d4ee72e38f http/cves/2020/CVE-2020-15867.yaml:fbd6ade1988a231d4bbe781e2f6d15dd324ff410 -http/cves/2020/CVE-2020-15895.yaml:478bdc1820ba9c687197211e69372749bea4a1e1 +http/cves/2020/CVE-2020-15895.yaml:b4eeae481880a73ce416fd345fba6030c6e395b3 http/cves/2020/CVE-2020-15920.yaml:ca02966d7fa7009b71ab3ddbd5bfc22c067c9c3f http/cves/2020/CVE-2020-16139.yaml:670be4d64df30da5920776484056cee577a00024 http/cves/2020/CVE-2020-16846.yaml:62340b3c18a55dee3e1bee459af4cea2e4c3dacb http/cves/2020/CVE-2020-16952.yaml:b8b4a222eb59276d4c4a1fd602e9a7d5bcf24da3 http/cves/2020/CVE-2020-17362.yaml:0639b3046a7ef4f3bcbe002187145b689616f611 -http/cves/2020/CVE-2020-17453.yaml:ba326b5a6f253efe81b14fb38c73041155b46d70 +http/cves/2020/CVE-2020-17453.yaml:fd2b162d8f7db8da5c5da87e77f8c2e87f7bf725 http/cves/2020/CVE-2020-17456.yaml:8c0efce1ddde1bb303c20985de6cc7fd8c2bf719 http/cves/2020/CVE-2020-17463.yaml:0053cad7e246164de29a188550347eea2d39712f http/cves/2020/CVE-2020-17496.yaml:6c18ebb9eab2e681fca3235574eb926756c34261 -http/cves/2020/CVE-2020-17505.yaml:bbc7c28c6cc52ebcbe4fb802776ab3dfb058fbe5 +http/cves/2020/CVE-2020-17505.yaml:532b4320fb5c5673314eed100336391dd899107c http/cves/2020/CVE-2020-17506.yaml:03304b64c8d56c4255e1a0e704899b705b6b708c http/cves/2020/CVE-2020-17518.yaml:6a9aaac92bc082156937e401fb3c3fc684277cc8 http/cves/2020/CVE-2020-17519.yaml:229daf62007fba286371debb8a03229b43c74280 http/cves/2020/CVE-2020-17526.yaml:9d9d2a87511f47455474b46e99856cb3866804a9 -http/cves/2020/CVE-2020-17530.yaml:768c0e1691028210c316bfb6992bc5c66ae06a55 -http/cves/2020/CVE-2020-18268.yaml:1736c1105708563e291cc306682cb867b7cf89d5 -http/cves/2020/CVE-2020-19282.yaml:136f220e9b0baed51cd2491583115968df122f33 -http/cves/2020/CVE-2020-19283.yaml:8c2aaa873c76b3f6d11dc610e6b17dd29a860fa9 +http/cves/2020/CVE-2020-17530.yaml:1c87a27a9b1f06d513f71d341c4e16afe614aaef +http/cves/2020/CVE-2020-18268.yaml:78e779978e91a6355edacd4932f6775604d28f89 +http/cves/2020/CVE-2020-19282.yaml:091a22d3c8fdd9834dafc7ca2c24d0b1ea45a877 +http/cves/2020/CVE-2020-19283.yaml:857e3005497dd4d633516967e46bc284cd001e98 http/cves/2020/CVE-2020-19295.yaml:fa246a14bdece2406c08fcf8953c627c8d2cefaa -http/cves/2020/CVE-2020-19360.yaml:3377e1adaddebc03e5a0e95bd3427fc9ca18498c +http/cves/2020/CVE-2020-19360.yaml:7bc8f9ec47dca14d299dff73d6fe6bebf36c635d http/cves/2020/CVE-2020-1943.yaml:8b20a01a97dc993837afd2cfce263ebf5af3c815 -http/cves/2020/CVE-2020-19515.yaml:76f2c9d4d4ee7aebe4403d739d32870250e913d5 +http/cves/2020/CVE-2020-19515.yaml:44116e1e70962d1598cfa1ce9e8deac0be74b2b3 http/cves/2020/CVE-2020-1956.yaml:d78a6a496d734888c64b3b80bef08b38e7fc62ac http/cves/2020/CVE-2020-19625.yaml:369b9f1c78077c1fecd1be378601564820abc51b http/cves/2020/CVE-2020-20285.yaml:01de24cf2975e71df3d5b8abba822bae4f86a954 -http/cves/2020/CVE-2020-20300.yaml:74316f9c696c9baab2082e8feacbf51650733d88 -http/cves/2020/CVE-2020-2036.yaml:47bd5bac0e792056e4f6a3116fa5c6f3413593dc -http/cves/2020/CVE-2020-2096.yaml:a088bf4da9960302402cdfa4387bb33165537500 -http/cves/2020/CVE-2020-20982.yaml:70bafe61cffbf49cef614dbd0a2e0b5f864b00c9 -http/cves/2020/CVE-2020-20988.yaml:d956113ffa296a7c05e69dd518c893569be3c708 -http/cves/2020/CVE-2020-21012.yaml:f63e981b9566a7d6ec5138f1a35b30eebb04460f +http/cves/2020/CVE-2020-20300.yaml:64d0866502f206e2cca8abf05746b0742e627a15 +http/cves/2020/CVE-2020-2036.yaml:5c11f8a90d7efc5071c49f2eca6524187830e9b6 +http/cves/2020/CVE-2020-2096.yaml:e580f902f26d65453b9d1027ee31ef2367085666 +http/cves/2020/CVE-2020-20982.yaml:4b964d49ed437e52a65e185c34bd21861be2dde8 +http/cves/2020/CVE-2020-20988.yaml:5ebd78da0f5faa02f86cb59d649ca7744351a6de +http/cves/2020/CVE-2020-21012.yaml:38d169864537be5248200e33fa85456b7004258f http/cves/2020/CVE-2020-2103.yaml:cf2b825a300f27ff32d1184026e049276c088373 -http/cves/2020/CVE-2020-21224.yaml:8248346cc7bcae71d455062d5fe8d89c14cccdfa -http/cves/2020/CVE-2020-2140.yaml:e14f3f2f47d6d6e295079c01995a4719b75cbe23 +http/cves/2020/CVE-2020-21224.yaml:157af6b2ed349de491ca8849be2375a27485aa29 +http/cves/2020/CVE-2020-2140.yaml:6cff3cc2f4f8157d86b9481158a45ca19486b8a8 http/cves/2020/CVE-2020-22208.yaml:79a3d67b8197f7f8e8af3cb074de0f85629a04a9 http/cves/2020/CVE-2020-22209.yaml:50156056b31da87465bb25c0d76cc75de1f2989f http/cves/2020/CVE-2020-22210.yaml:a1e1a27f373b25af0c89ed4d7bfb6e6ef448e3b1 http/cves/2020/CVE-2020-22211.yaml:b32582f80f7e1dd21eb45c5e5d75eb02ce89e40b -http/cves/2020/CVE-2020-22840.yaml:04fbf9cc36d8a961ea93858338a07358707faf63 -http/cves/2020/CVE-2020-23015.yaml:35db30e0b56caa6325dd3394b26621b4e24b0f89 -http/cves/2020/CVE-2020-23517.yaml:2b9914220a407f03c58e75027ea91d396c366cc9 -http/cves/2020/CVE-2020-23575.yaml:95b263eaa2697072923aeeabb235ba02a55c7be0 +http/cves/2020/CVE-2020-22840.yaml:a53587b9757747ef4070c9ef98e092010616610e +http/cves/2020/CVE-2020-23015.yaml:98372b8dce519983068160b26ff5ce069be6d8e5 +http/cves/2020/CVE-2020-23517.yaml:7ab8783941ec6e913c3ff76c10e35b7d6d0bad5c +http/cves/2020/CVE-2020-23575.yaml:22d90e0e77803cb9d46fb00fa6129d162e875c04 http/cves/2020/CVE-2020-23697.yaml:9945f1cf3c7ece7566e997d181e3e0ffc1ae68b4 http/cves/2020/CVE-2020-23972.yaml:390f331de6fb9aaf80fd2be0faa111062d314375 http/cves/2020/CVE-2020-24148.yaml:a3edd7f7074dd1711d176c1641b98180b5f7b7db http/cves/2020/CVE-2020-24186.yaml:7ee18d885c4c6de8272603ad46acb89d3de600a9 -http/cves/2020/CVE-2020-24223.yaml:ea09bc011ae53193ce0c92c36aedc1eb82cef1cf -http/cves/2020/CVE-2020-24312.yaml:4863db2fe8121fadd6e04ab7e7a0ee9d74d43b84 +http/cves/2020/CVE-2020-24223.yaml:580a7018cfe27d1799978c4a079e26795ab4e4b9 +http/cves/2020/CVE-2020-24312.yaml:a7a94afeebe6fe2be81ce65769a3dc1858997526 http/cves/2020/CVE-2020-24391.yaml:1378da3756fef423fb84d8862ed72d264a85a820 -http/cves/2020/CVE-2020-24550.yaml:3a213c5bc87dccf13ee771630674b50f8d4b3174 -http/cves/2020/CVE-2020-24571.yaml:4777901cabc9438e88454882db5f43914d8417fe -http/cves/2020/CVE-2020-24579.yaml:7ebae8e7e05640a4e25d89f4c051c290e3381435 +http/cves/2020/CVE-2020-24550.yaml:d91d5e4dc35ac3b133d6be5baca08371a9addecd +http/cves/2020/CVE-2020-24571.yaml:64fc3c17bc5dfd2fadf24ea1b3a5005a03e1b776 +http/cves/2020/CVE-2020-24579.yaml:cad0a26f458b04fedbeff7cb20739d841bf6b05c http/cves/2020/CVE-2020-24589.yaml:f277daa112fe241beecbe907bb831a33628f4982 -http/cves/2020/CVE-2020-24701.yaml:63bdccd52eb1751f43f39bcd3e4785a7a3d55ad5 +http/cves/2020/CVE-2020-24701.yaml:779e9acb6f011931e6f74af0002905f3df6ef3cc http/cves/2020/CVE-2020-24902.yaml:f6e7081ea68205b553e10b320f535b73c5d2f4f1 http/cves/2020/CVE-2020-24903.yaml:f35d20580163b36efb0597acce1626ea5af43cd1 -http/cves/2020/CVE-2020-24912.yaml:8328e1c271358699be513cbf4f263c3b871768d7 +http/cves/2020/CVE-2020-24912.yaml:a9003fc2bfc38d0d699eb449efcc8ddd9d2323f4 http/cves/2020/CVE-2020-24949.yaml:6f55ec5eb4393b98a0604c34724fa192f1882716 -http/cves/2020/CVE-2020-25078.yaml:523b5b20e6c3b8666a1d6d8c7f145ed5c734a743 +http/cves/2020/CVE-2020-25078.yaml:7a2a8eee2925e49ed071457b92e112e291fb6ce2 http/cves/2020/CVE-2020-25213.yaml:545d856fb5c044f14a1fd4121ff3d1e7bf53be5e http/cves/2020/CVE-2020-25223.yaml:9e1dc35deb3f803a9c5640aa46a4ca82ad65d52a http/cves/2020/CVE-2020-25495.yaml:8bf96cd5642204fae2b605fa4f52fed7d5d33e9c http/cves/2020/CVE-2020-25506.yaml:32be4a93649ed14c32cc43e4b570b4218b0cdae6 http/cves/2020/CVE-2020-2551.yaml:0f26f7e939d5d6867206fbf3cddff60c0b6b969e http/cves/2020/CVE-2020-25540.yaml:3263a8749d22bfa4ae3bdc2378e8b64c33120b39 -http/cves/2020/CVE-2020-25780.yaml:d666c25a459a96adf44bb4d8845a32c94a66f047 -http/cves/2020/CVE-2020-25864.yaml:1942767bfe0bc5ccedd4ab6dcee17b7228395fbb +http/cves/2020/CVE-2020-25780.yaml:477886c8b1b1020a89a783ce70d58ab80f343c7a +http/cves/2020/CVE-2020-25864.yaml:1a0a5b26419ada2f6e62d5f430944b186fa41c57 http/cves/2020/CVE-2020-26073.yaml:c2480acfdbe2cb79eb9677736948078368b67f54 -http/cves/2020/CVE-2020-26153.yaml:ed789c05efba6efa34e466403127c90beb507599 +http/cves/2020/CVE-2020-26153.yaml:1f720e636e5ec2cc9a0c1cee66e1803f7202c50e http/cves/2020/CVE-2020-26214.yaml:e78b57b203e48636d265fc3e8cce21382714e55d http/cves/2020/CVE-2020-26217.yaml:2f790a15773d439d6411c1201a483e51a2fee299 http/cves/2020/CVE-2020-26248.yaml:d290cb120be1596dd425e9cc0e528b56cc0c00d7 http/cves/2020/CVE-2020-26258.yaml:9b043d7ad721fa53b0622fe138f69cee64dd69f7 http/cves/2020/CVE-2020-26413.yaml:73764be3dadcb913bd944c5da765e476b6c57a14 -http/cves/2020/CVE-2020-26876.yaml:96faa52302dfb9dfd89e1fce0301d47261e310f6 +http/cves/2020/CVE-2020-26876.yaml:560de7a069e8c8578d2cc6247264ec37c3403a74 http/cves/2020/CVE-2020-26919.yaml:d258f77e4e8f338d00117f1f0b664c6dfaaaa2ca -http/cves/2020/CVE-2020-26948.yaml:706ea789d74b095a6b67e030c4f0695095ce768d -http/cves/2020/CVE-2020-27191.yaml:74c3f34fba30870367af4bb62a0b5aafdb36e7cf -http/cves/2020/CVE-2020-2733.yaml:f06647d6a15a0dfc1d1accf60572e96f59665e72 +http/cves/2020/CVE-2020-26948.yaml:f6522e224479156b22a39626586959f299bf4d8d +http/cves/2020/CVE-2020-27191.yaml:5c015c09b719c4757d7e10902e1ac505333de5a9 +http/cves/2020/CVE-2020-2733.yaml:c8ea06770fb2c40e76d43e9dd8764af08e3587e2 http/cves/2020/CVE-2020-27361.yaml:5c776e893b27e3db80ff777b34f4025708fea0cf -http/cves/2020/CVE-2020-27467.yaml:882541e7d0d0fdb0d256e0e2da4bb4351230ce75 -http/cves/2020/CVE-2020-27481.yaml:4dd5d28d6373b75a31addcad4673679d2eecc320 -http/cves/2020/CVE-2020-27735.yaml:d8f7192a93da0d36400aaf88783f64ae9dfa3112 -http/cves/2020/CVE-2020-27866.yaml:fe37903c376d33b59e8d93ed88c468db061889b0 -http/cves/2020/CVE-2020-27982.yaml:17a1e954628e0bf61f9ed8114b4cb0048bb2a6a9 -http/cves/2020/CVE-2020-27986.yaml:1ec18e7e35c015d64d055baa70c3c85f377e4ea3 +http/cves/2020/CVE-2020-27467.yaml:ac32263aed6427ce0416d3f11fb0c00916d5aac9 +http/cves/2020/CVE-2020-27481.yaml:577c9dd12051e483370b77e8b34780a1a0984d59 +http/cves/2020/CVE-2020-27735.yaml:45d275b72dfb25ad9ecb0eb6d70f7a1a55521327 +http/cves/2020/CVE-2020-27866.yaml:ca31770b1d7f5dbf6d3123fb799b49c35b3b19ee +http/cves/2020/CVE-2020-27982.yaml:bb07aa798cb3aa9c28ef080f2cb31ec94ba87abb +http/cves/2020/CVE-2020-27986.yaml:e804e7e735949aaa49bfaef3363c531371ec1d00 http/cves/2020/CVE-2020-28185.yaml:d0f05316119c26b7567b8e0932cb511ea7a18286 -http/cves/2020/CVE-2020-28188.yaml:bb047d91f7658a0cd5c332ac13ed53b0af6b73b9 -http/cves/2020/CVE-2020-28208.yaml:e2a976733c3a02daae243287987c296a7a693989 -http/cves/2020/CVE-2020-28351.yaml:ec7c92e983baf905c2640e31361db5c9fad6f578 -http/cves/2020/CVE-2020-28871.yaml:7a5f5e96f80f327f50384e69707e9291cdec5373 +http/cves/2020/CVE-2020-28188.yaml:001a4fd6aaa41a0581ecebb8727b2511f4074838 +http/cves/2020/CVE-2020-28208.yaml:8f792df3f43ba59dac01710affd8b14640eb9516 +http/cves/2020/CVE-2020-28351.yaml:8e546cf396bd2f0d444452a03ce043012c7830c3 +http/cves/2020/CVE-2020-28871.yaml:13384038886422877fb4084dca46a26757576f5f http/cves/2020/CVE-2020-28976.yaml:708befa5c7928be6194110b0968709922d7f9854 -http/cves/2020/CVE-2020-29164.yaml:6e7dd005328db95776a92df35208d6adc164d972 -http/cves/2020/CVE-2020-29227.yaml:5666949d77bd0b9766ea1c8f3282f82057e4e455 +http/cves/2020/CVE-2020-29164.yaml:f2c3175f451296fb906ae77266999ec287154123 +http/cves/2020/CVE-2020-29227.yaml:cf0a03a7031f9b10c64c41e7c37a338cef6301fb http/cves/2020/CVE-2020-29284.yaml:4475c074e8aeb7d35108d3236e8acb16837ac3ea http/cves/2020/CVE-2020-29395.yaml:439c931d75a6ac279011c7b72c10713eb0b1da11 http/cves/2020/CVE-2020-29453.yaml:025a429fd7d47e809062c65a7e4a6f4b38c80fd3 @@ -1618,113 +1618,113 @@ http/cves/2020/CVE-2020-35234.yaml:a78bfbb19159d5ea54e6ca64bda69b49dbfd8042 http/cves/2020/CVE-2020-35338.yaml:ccf5404d53a46ded6ca06babc8208c9f3d7b4941 http/cves/2020/CVE-2020-35476.yaml:31316ad9d3e65de49d1384f68f48cb0348da001f http/cves/2020/CVE-2020-35489.yaml:0853a5c4aaa37fea84f7381ba072e64f368ebea5 -http/cves/2020/CVE-2020-35580.yaml:89f9ae563adf81585e25e7bd80224e1e5cf5c0be -http/cves/2020/CVE-2020-35598.yaml:a37ffcabcdfef22608a17c54fc33a57e592a61bd +http/cves/2020/CVE-2020-35580.yaml:8ddfd4fac11a536d611697c87a331d97b83c0919 +http/cves/2020/CVE-2020-35598.yaml:8e122d8403866d1d8b7f4ace19a5fc6663e9948d http/cves/2020/CVE-2020-35713.yaml:4f279e54346f738f2db6dbd66542e53cdb0c1792 http/cves/2020/CVE-2020-35729.yaml:01d84312ea3ff15773ad4f3f8d87aed5b53cb7dc -http/cves/2020/CVE-2020-35736.yaml:2f5d199c022167de23062d6c38841064a5351264 -http/cves/2020/CVE-2020-35749.yaml:9e58339aef9873add5fbf997a9fee6b4e9591bd6 -http/cves/2020/CVE-2020-35774.yaml:06bdded6211f45ecf9e5f799dcec9f903b2f8f58 -http/cves/2020/CVE-2020-3580.yaml:50e1de436aca4e279b793e0b440a5ce057d48513 +http/cves/2020/CVE-2020-35736.yaml:8c20558435a437ee3a54ff4fa9a7c9172e5591fd +http/cves/2020/CVE-2020-35749.yaml:dad4a36c0695f05dd0c5779b0e6e6a2c2d2e3ca2 +http/cves/2020/CVE-2020-35774.yaml:ba663a38eef6fe8103cad5d12a6fcda21ded8b3b +http/cves/2020/CVE-2020-3580.yaml:25e7b47bdeac818bf8d15da273f5030be15b5843 http/cves/2020/CVE-2020-35846.yaml:49bba31dc90bae96f00b0ef69ce99c4d785ff2ae -http/cves/2020/CVE-2020-35847.yaml:a2c716a87576edcc03fa12cc7a610ba902d1c4ac +http/cves/2020/CVE-2020-35847.yaml:a6a621540cfe50c98fc1c5ed2b59862c1aa03370 http/cves/2020/CVE-2020-35848.yaml:8d531fd9445ceccb2f4890d924e271faf8a313cc -http/cves/2020/CVE-2020-35951.yaml:075f3e50634628cd4076516e5800920eb7e6fc83 -http/cves/2020/CVE-2020-35984.yaml:406f5b55e23b82366049f2664a81e64d68d37ee1 -http/cves/2020/CVE-2020-35985.yaml:11f803f4844c35a63655366efb60d9be5b15f251 -http/cves/2020/CVE-2020-35986.yaml:0ca6434dcfcfa0400aa404c8c3ba09933aa409a5 -http/cves/2020/CVE-2020-35987.yaml:a84669761778110e74cb699d11dd9addccbc433b +http/cves/2020/CVE-2020-35951.yaml:93f43b19e6d92595bdb3f1e4caa93c385e0d9e4c +http/cves/2020/CVE-2020-35984.yaml:f7f8c00fcd3d7ec90a114cb1d6a68202acce0a14 +http/cves/2020/CVE-2020-35985.yaml:608dffafb398a504fce6ee466199752c52a78456 +http/cves/2020/CVE-2020-35986.yaml:d044d966720bbb342b7b1e6db1a9c276734dd400 +http/cves/2020/CVE-2020-35987.yaml:dbeb9f030901673690ee647e1a2a96ea42e99a50 http/cves/2020/CVE-2020-36112.yaml:ba79462f94625bf488f2ccf150ff7081057a2cf6 http/cves/2020/CVE-2020-36289.yaml:e30c3a62513fd85ec582e9afd7381051982688eb -http/cves/2020/CVE-2020-36365.yaml:add918b6b4b4b14eca00a24a75823089a9932075 -http/cves/2020/CVE-2020-36510.yaml:d3c751cfb50cb6b949a839eef26cba89b8756b14 -http/cves/2020/CVE-2020-4463.yaml:48d93414e3c315851afb883e4941ebdf3b23c1d5 -http/cves/2020/CVE-2020-5191.yaml:a74bfd5e634b69fa8468a3d56ae86fd943385e7c +http/cves/2020/CVE-2020-36365.yaml:f06fa216249642bc20d366d60c3bb187bf41d28c +http/cves/2020/CVE-2020-36510.yaml:9a47873be1c501ab694fc2e4f5887ca74c163f71 +http/cves/2020/CVE-2020-4463.yaml:6f2dcd93f1c5fc9986b1cc46cd5692dc3bccfc43 +http/cves/2020/CVE-2020-5191.yaml:64e4b4f022298705471dfac9a4ad48436443f583 http/cves/2020/CVE-2020-5192.yaml:fd196f46fec8b1b9764a9a5e71b867816afd75cf -http/cves/2020/CVE-2020-5284.yaml:7a849fe8ca03c5063261d6615548e9057c75ad77 -http/cves/2020/CVE-2020-5307.yaml:112d7b4fe2adb33e38007e7febeab44ae5106f55 -http/cves/2020/CVE-2020-5405.yaml:bc62df7e9db0e93365d609f120851d85ecbe8046 -http/cves/2020/CVE-2020-5410.yaml:0c611077f8abde547349492bb51c5d12ae9c2c57 -http/cves/2020/CVE-2020-5412.yaml:dbc763076fa08af02e56a5c9ce905196c666c446 -http/cves/2020/CVE-2020-5775.yaml:f8deebe529d84f95209b534f99f581773a7bc4c5 +http/cves/2020/CVE-2020-5284.yaml:4d07123245e1ef9e306a0e7c25c1bcd6b5312ecb +http/cves/2020/CVE-2020-5307.yaml:70ae88877f969514bdf47ffd7134550c5568ca76 +http/cves/2020/CVE-2020-5405.yaml:3b84f3f45b049598a6491d1cc848cbe43fdfc758 +http/cves/2020/CVE-2020-5410.yaml:ba5ce67438d670bc5b9a4293220d8542a82f4576 +http/cves/2020/CVE-2020-5412.yaml:a221a11825364b1676c08771866f1ac28dc30ea1 +http/cves/2020/CVE-2020-5775.yaml:7e0d481bc5ea64fe60060cf3ef9b2d0caeb10bf3 http/cves/2020/CVE-2020-5776.yaml:2d28f404085391c57e3d55f4ab20f9447314827b http/cves/2020/CVE-2020-5777.yaml:8e5e1f71ed530009696851d36853a656331c0927 -http/cves/2020/CVE-2020-5847.yaml:5615e1f57901135c41210860b97f22d28e2bd287 +http/cves/2020/CVE-2020-5847.yaml:85b3e2c205a27d439992b05fc651c9ed6f5ca453 http/cves/2020/CVE-2020-5902.yaml:8309f9ce21eb0c7d9efd601ed12c1c7e950ac534 -http/cves/2020/CVE-2020-6171.yaml:a4f7d9267bbe12ff0dcaf28aaecd5821c05a27c9 +http/cves/2020/CVE-2020-6171.yaml:ff4319a6da4e9e03d381e4a35fcbc61cf9b346df http/cves/2020/CVE-2020-6207.yaml:384ce7695a4fa9425b28e6aba29d6f76f233c5c9 http/cves/2020/CVE-2020-6287.yaml:cceacbb619c5a48bf394304dae7fb3d8979ec73b http/cves/2020/CVE-2020-6308.yaml:78f13a0870632b9622adf236e3bfd09ff9f7c7be -http/cves/2020/CVE-2020-6637.yaml:27eaab549fd2bc5d7cc4c6f0807f720628902474 -http/cves/2020/CVE-2020-6950.yaml:da5aea0a4818c8ae5aa49ce6efb0a496c62935df -http/cves/2020/CVE-2020-7107.yaml:86747847a2628cc5b9de1041b707879515e91d80 -http/cves/2020/CVE-2020-7136.yaml:62cb91e7d52366cdd6c1141106a44553650cb9a0 +http/cves/2020/CVE-2020-6637.yaml:e39406f49b9c9fa91757f21b721e8c71b6f87f96 +http/cves/2020/CVE-2020-6950.yaml:e4fdc616aa060ea9c05a460d7770cc905a0f0c4a +http/cves/2020/CVE-2020-7107.yaml:fc8aaadbaaa51850607e150a0f315bbea3ab1522 +http/cves/2020/CVE-2020-7136.yaml:26f1bd26227786d25614ea2e36f3cd9e13cfec71 http/cves/2020/CVE-2020-7209.yaml:07f5edf8d4237880f1e6917ba2ff96f4cedcfce3 -http/cves/2020/CVE-2020-7318.yaml:ea864fb3811051a48b88ccfa5e308b36fe560458 -http/cves/2020/CVE-2020-7796.yaml:528ac8ad9986c42d3c329253869b79b5fa9cf66f +http/cves/2020/CVE-2020-7318.yaml:c8001adad7e9f3de852155a2543def9c9d8a3f54 +http/cves/2020/CVE-2020-7796.yaml:82d3d80718a4b4fafdbd8c8c6b9908a1c003a17a http/cves/2020/CVE-2020-7943.yaml:481c0b640803b72018a9d4aacdfa245926a2154c http/cves/2020/CVE-2020-7961.yaml:e2b864277cfeb986445f37830690a07a0cc0a726 -http/cves/2020/CVE-2020-7980.yaml:7ba7ccfe422aa84c5b6da042281fbc6912033c89 -http/cves/2020/CVE-2020-8115.yaml:f1fa2823c4457e54a4afb2c4c0d1c1c5ee204020 +http/cves/2020/CVE-2020-7980.yaml:7dfb0db00d6bf60635ded8598d8d1f73df586185 +http/cves/2020/CVE-2020-8115.yaml:e5b7faa02ef9629caab22dbdcf5f76bec566cf6a http/cves/2020/CVE-2020-8163.yaml:55e13f323edeaf15963cd6cb60010c5665ab7345 -http/cves/2020/CVE-2020-8191.yaml:0804bfa48cf40aa8a3ee976bd67c1c2a4232a0c8 +http/cves/2020/CVE-2020-8191.yaml:198afd6cf58b3d08b9625720107eba19eea946cd http/cves/2020/CVE-2020-8193.yaml:7d8e94566e7ac34a5ef7e9714335818894fdbd09 http/cves/2020/CVE-2020-8194.yaml:303bb7f8ccd32ef66b0604fc1ce1b8c2b6fd4b80 http/cves/2020/CVE-2020-8209.yaml:918bc7091e8632f8cb6243f0ad26b57144900674 http/cves/2020/CVE-2020-8497.yaml:4c8e1a786ca4e4afc809e283c6a11d215be0e37a http/cves/2020/CVE-2020-8512.yaml:98fea7c4a47c22cb416ecaadec689edd1958fe97 -http/cves/2020/CVE-2020-8515.yaml:7296b0cc768ba5b9ac9e758991e4ff31ad7aa359 +http/cves/2020/CVE-2020-8515.yaml:a553440c538a3e4ede4460eb8e2f71008b500f0a http/cves/2020/CVE-2020-8615.yaml:15705b7098c1154d0ced081a606e8f1a20d36b42 http/cves/2020/CVE-2020-8641.yaml:02838d28c707b58b0a4e9607c0c5f090ca587536 http/cves/2020/CVE-2020-8644.yaml:65907f347ef321ec1a9823cabd1b806621eb98fd -http/cves/2020/CVE-2020-8654.yaml:764e7927dbed2548f266ec89643737e46911b592 -http/cves/2020/CVE-2020-8771.yaml:4965a374e91a2df2f77cd1b469df4dd125cb7c29 +http/cves/2020/CVE-2020-8654.yaml:c3ffc8112e69599695577ba2a090212f565b4192 +http/cves/2020/CVE-2020-8771.yaml:9d0f1db6a2ffd580548ed2dd847a420160f466ae http/cves/2020/CVE-2020-8772.yaml:3fd7f2291b2acbdad5d73e31e6719572ff843c16 http/cves/2020/CVE-2020-8813.yaml:a735c47155373656a3923c4361f735d9b1cddb72 http/cves/2020/CVE-2020-8982.yaml:78e8d3425fb78527a6c95ac2bf065410087c3c11 http/cves/2020/CVE-2020-9036.yaml:c182a4121865f1d14d528eb185e7e5b6c807e40a http/cves/2020/CVE-2020-9043.yaml:24b0379633c1415c105065d769ee35a67f50e573 -http/cves/2020/CVE-2020-9047.yaml:43c9801374bfac9534d8bfaf6c0f5e616f9c9b5d -http/cves/2020/CVE-2020-9054.yaml:61833939b941e2c2e3eb33a2a4eb28072b165017 +http/cves/2020/CVE-2020-9047.yaml:628205d55cf15040e290297fd9e352bdcbe9df57 +http/cves/2020/CVE-2020-9054.yaml:98544063e3066a1bf770a2738a94b24bf8255bdc http/cves/2020/CVE-2020-9315.yaml:f80668537bc085f8316f39d95efeed999ae7b0fa -http/cves/2020/CVE-2020-9344.yaml:c029d3d70a59d834827e2034864290379a96abd6 -http/cves/2020/CVE-2020-9376.yaml:acb4ce508161ac7d6afb0ee73148cddca59998b4 +http/cves/2020/CVE-2020-9344.yaml:248951566051598a9158f3fff0e357bccaa313b0 +http/cves/2020/CVE-2020-9376.yaml:836ae299e086182427c673db0e24a811fb68a402 http/cves/2020/CVE-2020-9402.yaml:4f65cec5931661e770203b86ed01266203b0be6d http/cves/2020/CVE-2020-9425.yaml:fc45c58f3fe96e42b1d950ca194e5ec5c30d5fce http/cves/2020/CVE-2020-9483.yaml:f5595bf6c3457b1dce5c18a03a9cef2e05dabaec http/cves/2020/CVE-2020-9484.yaml:060a10852282850e64bafc3b7d03b2e6ba9540c1 http/cves/2020/CVE-2020-9496.yaml:1cb1372f0f5c966a71ea14eb6669abd819766e09 http/cves/2020/CVE-2020-9757.yaml:dcfa598b2246d9d1452e6226f8ffd3e9f6f0fa70 -http/cves/2021/CVE-2021-1472.yaml:cf585b1cddb5272a4bed0e9434cc658015a2b830 +http/cves/2021/CVE-2021-1472.yaml:2ad6cbe8fcfeb6f3b490da3ae8342c564c6eb537 http/cves/2021/CVE-2021-1497.yaml:c3bd9e4721e8b5f453571c3895f2f532e0484e53 http/cves/2021/CVE-2021-1498.yaml:42f2568b141795b209c7d73eb64b541319dc83c0 -http/cves/2021/CVE-2021-1499.yaml:1781c697bd024ee949fcdb152897c6502c23e8ea +http/cves/2021/CVE-2021-1499.yaml:96e47c3b09e1123844a971cfdb78752a8223ae76 http/cves/2021/CVE-2021-20031.yaml:26b79af16b951596e6d4d8ae63b1e24db03d2bf6 http/cves/2021/CVE-2021-20038.yaml:cf837f60aa5b2cc19a1de5b7f20ae4c7b782bfed http/cves/2021/CVE-2021-20090.yaml:8924a81b47b029b29f5568155932b36b42cc271d -http/cves/2021/CVE-2021-20091.yaml:e535d0dd5002cf7439e547d968f77ccdf8abeffa +http/cves/2021/CVE-2021-20091.yaml:3b0db87ff56e3daa1b40305bd2110ce44ca264f0 http/cves/2021/CVE-2021-20092.yaml:b01100032d11fbd2ef60b343c60369f60d4e7193 -http/cves/2021/CVE-2021-20114.yaml:17dcf26abcd5d33b9dbe4731b975592589c137b9 -http/cves/2021/CVE-2021-20123.yaml:f4c886cb75fffad3f2efaae5a35172e7d4996fa5 -http/cves/2021/CVE-2021-20124.yaml:371f20157f964aa96969e254cec4bdaad62f57a1 +http/cves/2021/CVE-2021-20114.yaml:1cf03ec6dd63b77b9293f91f78903d2096b6a5c8 +http/cves/2021/CVE-2021-20123.yaml:41a7547975e3eff7fc244d4eec333adf0da2618b +http/cves/2021/CVE-2021-20124.yaml:084e95d5d0ca4ce2b70b019a9bde9a3497e69bdf http/cves/2021/CVE-2021-20137.yaml:ceedf2daf4b06a72ba885341b2a9a0c600f11ee7 http/cves/2021/CVE-2021-20150.yaml:bb21c83d01e51e0a4e6b69072f1f0a9dfe57fb1a -http/cves/2021/CVE-2021-20158.yaml:02d8c6540933f5ee8816a9535ce0c66e8d648b9b -http/cves/2021/CVE-2021-20167.yaml:ae64fac6212edef796fcfcc4a540aec7f9904c84 -http/cves/2021/CVE-2021-20323.yaml:b30cc05dab3904003bbe18eee59109a7fbe9f3fe +http/cves/2021/CVE-2021-20158.yaml:fdbdfba2c27327bf64981643fa665bb37bfa1b31 +http/cves/2021/CVE-2021-20167.yaml:979a960374378c3bb42795ae96e9e62f2dc6aea5 +http/cves/2021/CVE-2021-20323.yaml:8efacc7d21fbeef6790a78bdad4ae9b008c788f3 http/cves/2021/CVE-2021-20792.yaml:e7b1b19b0a39fa32805338a30c9e91f48cfdb653 -http/cves/2021/CVE-2021-20837.yaml:ec688ff4b3a870fa997b0aad1d881068a008e98a -http/cves/2021/CVE-2021-21087.yaml:7ddf7fe868f132b2e2a37677d93b42990284ca69 +http/cves/2021/CVE-2021-20837.yaml:7b958208d33ed33ae33f6d2ed171411bca13a3e1 +http/cves/2021/CVE-2021-21087.yaml:c2eba2f5080a1b5d74fd7db14ba9c95061f4c608 http/cves/2021/CVE-2021-21234.yaml:213a57d68106015e87f822d5afb0c7e46278415c -http/cves/2021/CVE-2021-21287.yaml:a0f1f44ce90d062a1de70f2c0ad8b2363aee8b4b +http/cves/2021/CVE-2021-21287.yaml:f82a2dca49e11968de4c54d1826be006f15fbbb8 http/cves/2021/CVE-2021-21307.yaml:fac60e0583bba956b6d4429ef8056967340f24f8 -http/cves/2021/CVE-2021-21311.yaml:e4770b0b2eed7cde94b4c10b173a7dcd1b4a8374 -http/cves/2021/CVE-2021-21315.yaml:a9de6a28e4f19a091718a4f5bc944a6e1c6ca0c7 +http/cves/2021/CVE-2021-21311.yaml:6d057a04e8ebad9b738234f133c7ec4b619444ff +http/cves/2021/CVE-2021-21315.yaml:36d981eeb05fab17067aa4d4ff2f65f4298adcfa http/cves/2021/CVE-2021-21345.yaml:199f8e28f0077277bcce402c23c7e0d9b39de620 -http/cves/2021/CVE-2021-21351.yaml:e14b05b4e190a63aa67077748fd3ebeb6c302011 +http/cves/2021/CVE-2021-21351.yaml:a82618ef7ef524d6ebd18ca2d2bcc6e053f5d30f http/cves/2021/CVE-2021-21389.yaml:4ac0f6b6ba5bd693ac01cf56c12969716ab9672b http/cves/2021/CVE-2021-21402.yaml:f7d8937786d3bfe4deb8b08a66df0f672cacf60f -http/cves/2021/CVE-2021-21479.yaml:943075055a8bc149d782c42641f588400cf4d2dc +http/cves/2021/CVE-2021-21479.yaml:226993912bfb9e0dacf9c22ba20ac34fc924c4f3 http/cves/2021/CVE-2021-21745.yaml:3fa72f167ca2e58046e0519335a00defe7832c8e http/cves/2021/CVE-2021-21799.yaml:ddb3d9da45ddd3de2084a5717c30d2943a96a255 http/cves/2021/CVE-2021-21800.yaml:27273707406e986d6002c874d89ead98ad8ca4bf @@ -1735,132 +1735,132 @@ http/cves/2021/CVE-2021-21805.yaml:e241b01e425d029891579b3f94a16afec849fa0e http/cves/2021/CVE-2021-21816.yaml:408eae876827b0bbeabfded1f6daaaf84e679763 http/cves/2021/CVE-2021-21881.yaml:391ceca42b6d28722c8580b095f247911781fc13 http/cves/2021/CVE-2021-21972.yaml:983f4f0bc04e0ebb4a2a78baab589ea67e61d358 -http/cves/2021/CVE-2021-21973.yaml:744435da9d0330b424ba825bacc1fd1e91a6082e +http/cves/2021/CVE-2021-21973.yaml:10e7fc874a74f93d45221c72fc76453cc76c551b http/cves/2021/CVE-2021-21975.yaml:b1227f02bb7167dab7dff7b080a6cbc050a97ccd http/cves/2021/CVE-2021-21978.yaml:bcbf4669c28f2a865f1e0fd498c2d1ff467dd910 http/cves/2021/CVE-2021-21985.yaml:a68b78c7fd45dc4660238403694fc9ca7db1ab5f -http/cves/2021/CVE-2021-22005.yaml:181432ef49b7c35be46770595fd079d932a98c12 +http/cves/2021/CVE-2021-22005.yaml:fb6ffcb027a578e89b4a6426d016f516f60a6513 http/cves/2021/CVE-2021-22053.yaml:bf6056161b2a93f76778c9c67a958e5fdfa4e25c -http/cves/2021/CVE-2021-22054.yaml:8683fa4785726ababc18c424ec7619cf2b03f2b6 -http/cves/2021/CVE-2021-22122.yaml:099ae1bcafa4373e97120aa34e81dfbd717b15ed -http/cves/2021/CVE-2021-22145.yaml:a2ee4786122c7050a9a4d13e48bbf6f37759b7a9 +http/cves/2021/CVE-2021-22054.yaml:ac8c45808b2e6dc9490f56d5e40519678de32513 +http/cves/2021/CVE-2021-22122.yaml:8266bee60b89611aebafd9b3bc2c610535794bfd +http/cves/2021/CVE-2021-22145.yaml:8b733afe464dca3e72301f186ed5a435af7e4b50 http/cves/2021/CVE-2021-22205.yaml:d1135e1af439ab782b891973f384f138dbe58475 -http/cves/2021/CVE-2021-22214.yaml:41c78ed7a4d6d01b9e4136168a69b00cafcfddc4 -http/cves/2021/CVE-2021-22502.yaml:5924e2ae34dac7ee3f0b55068c96329da64b3701 +http/cves/2021/CVE-2021-22214.yaml:06b1d857e8f210d8cdede0e40d7003a1462111b5 +http/cves/2021/CVE-2021-22502.yaml:180d0176372edf45da3810af0574131fe679a4ba http/cves/2021/CVE-2021-22707.yaml:6379d225b05d9ee6038a045f80e84c139b4220c3 -http/cves/2021/CVE-2021-22873.yaml:e3100e32060f9e037b5499e8449ae6eac8803a57 +http/cves/2021/CVE-2021-22873.yaml:4a5be9d109a41200a2c5ebac6ee59c5ed0536837 http/cves/2021/CVE-2021-22911.yaml:0db7ce72f35fc5ee4deb07717c2360e4df701b43 http/cves/2021/CVE-2021-22986.yaml:a72575d9e886e4181478b893776a45e56133da2f -http/cves/2021/CVE-2021-23241.yaml:5a9b0fa614cbe05dda7ca646393f4e37eca60388 +http/cves/2021/CVE-2021-23241.yaml:1d8e5b0d75924ba12a63530db62e722b9eacfee2 http/cves/2021/CVE-2021-24145.yaml:20ef1b99e432fc56531d4151f8f2ac0bd718a2b6 -http/cves/2021/CVE-2021-24146.yaml:72d387549139101e2810132b60aff044aa6e4906 -http/cves/2021/CVE-2021-24150.yaml:48929c31bf4ac442fc4e3abf3c3fb91a64061bc8 +http/cves/2021/CVE-2021-24146.yaml:049af2ed0efa0ce49b325143d696d36142290913 +http/cves/2021/CVE-2021-24150.yaml:83204779fc3428761ee63a6b7da0084d48b8815a http/cves/2021/CVE-2021-24155.yaml:eb4f5f566132d76f8cd4c942a42d1a740225b412 http/cves/2021/CVE-2021-24165.yaml:e38d290f4f38852d78a9a88ce377dad6486b3251 -http/cves/2021/CVE-2021-24169.yaml:ce67a2297d6470e066aa56771ba2bd9efeed45af -http/cves/2021/CVE-2021-24176.yaml:fc6bfa6d1baaa1687430c6ae8c51ded353593894 -http/cves/2021/CVE-2021-24210.yaml:35fabe286fd36e46d9a28a01e43db2ddcf245479 +http/cves/2021/CVE-2021-24169.yaml:92ac6022e1279fce266ad831163d747f73cbfde1 +http/cves/2021/CVE-2021-24176.yaml:cffde820739ae64a8ed181fe0f3436d7e980e8d7 +http/cves/2021/CVE-2021-24210.yaml:eacb1976525af5c47ea0e8dd5401f70a1bf9c6a9 http/cves/2021/CVE-2021-24214.yaml:4d9df64d867907f3c91f87085e086c244d44e3ab -http/cves/2021/CVE-2021-24215.yaml:3a2ab5a410ee48ed9c4545f40a2e88efd4121222 +http/cves/2021/CVE-2021-24215.yaml:e8116accbce4e818718bbba20829cf8d557fda2e http/cves/2021/CVE-2021-24226.yaml:01a87f9f77765f4ef95ccdb03f465e2f002763ce -http/cves/2021/CVE-2021-24227.yaml:77d11c6ce86f2b2b96496be92b4865d357eed229 -http/cves/2021/CVE-2021-24235.yaml:1b5f76f2ae91df4922bb8f59b71bd301af97652b -http/cves/2021/CVE-2021-24236.yaml:c4103df7b6117545df353c37d30061c04fe498ab -http/cves/2021/CVE-2021-24237.yaml:e282de032756045cd4345da905f1065b4d4c039c -http/cves/2021/CVE-2021-24239.yaml:18610cd7382bfe6e05cebedbb7f86a3a628c27fa +http/cves/2021/CVE-2021-24227.yaml:41d9211a4d6cd84d4304c58648057f8a63147457 +http/cves/2021/CVE-2021-24235.yaml:68db2d7f86dc42c31bc37a3df11f70cc8c0ca6f2 +http/cves/2021/CVE-2021-24236.yaml:32c6de95787226cc320e4e2de8179de452931016 +http/cves/2021/CVE-2021-24237.yaml:668778497d51ae6b9de75dd4d4cabdf8d9d6ffe1 +http/cves/2021/CVE-2021-24239.yaml:8ed22023c3578dc4e3cb5a2c0bb9a85cf62f58d5 http/cves/2021/CVE-2021-24245.yaml:2ec6355b790de2ef398b5c43f0340fd89587c9e8 -http/cves/2021/CVE-2021-24274.yaml:caf5aee3624753813cda6ea3b760356e60d0a736 +http/cves/2021/CVE-2021-24274.yaml:f3c27baca9347f47ccf664206a1a5fa3a78783da http/cves/2021/CVE-2021-24275.yaml:c6289782e6b487d6c95a6e1262bcce5aac83afbc -http/cves/2021/CVE-2021-24276.yaml:b53c4a63f95a337006994f5ceb1d319a3b7b80b2 +http/cves/2021/CVE-2021-24276.yaml:ab2a2d269801f80a79d3ba88ff11b4e65de13017 http/cves/2021/CVE-2021-24278.yaml:03e0a82d269eb104181ece9a655b4eb896b08884 http/cves/2021/CVE-2021-24284.yaml:ec61ff15f0260159721899a8a00793daada7c95f http/cves/2021/CVE-2021-24285.yaml:54779d1ddf8d5b25af2c3fcac5d77318f2c48564 -http/cves/2021/CVE-2021-24286.yaml:4743f7b58560e682b5d9802c80b73dfeb9577ac8 -http/cves/2021/CVE-2021-24287.yaml:67676fc490427b96be1bca3daa5fbd4dcb1fc0b7 -http/cves/2021/CVE-2021-24288.yaml:944439ee6d0bfe1e9f800a4f99e981cc2a6a8c06 -http/cves/2021/CVE-2021-24291.yaml:3ae16f5946aa5a43a5ddee5f0b0fb13b8b9bc75f -http/cves/2021/CVE-2021-24298.yaml:f891165ca3c48447f823d8021d6d836c93681296 +http/cves/2021/CVE-2021-24286.yaml:39939323f070da62355d541ea9c1a741998a225d +http/cves/2021/CVE-2021-24287.yaml:476a99bf81657e68c054844c16523a495dbbbede +http/cves/2021/CVE-2021-24288.yaml:f760e074de8d7e3e78335f64243eb60f395779ae +http/cves/2021/CVE-2021-24291.yaml:7c1aa24be4e842df4ce982b1fb9a9149eb3d3f3b +http/cves/2021/CVE-2021-24298.yaml:9c2604a8acf79d00914dc5e8d3199deef8f28ced http/cves/2021/CVE-2021-24300.yaml:42e1f9cd202a84642d078f4e909e39356b5ea5f5 -http/cves/2021/CVE-2021-24316.yaml:323c2f15d96f2e3ceecb2674a6309c4ade078de3 +http/cves/2021/CVE-2021-24316.yaml:17bdde752aab041698163b70150e8bc2f4200dba http/cves/2021/CVE-2021-24320.yaml:c566d57cb4eff290adefec2a89aeed9484f2d5b8 -http/cves/2021/CVE-2021-24335.yaml:b6b9c45ddb1d5ea2fba07f58514760e211bf7831 -http/cves/2021/CVE-2021-24340.yaml:1ce9f7e215f4a8b41e5a83234b28d90dc58f47d1 -http/cves/2021/CVE-2021-24342.yaml:0f27ee15da44dfb474bb87a45deef4e4caca11eb -http/cves/2021/CVE-2021-24347.yaml:18b1ac4464c0a492b7bf2baf466181212dc540a3 -http/cves/2021/CVE-2021-24351.yaml:a65fd6f17513d0bba4721b1cce59004ec8cdaa4d -http/cves/2021/CVE-2021-24358.yaml:743e286e690054b67bbd14fc0929dd8f8f922de0 +http/cves/2021/CVE-2021-24335.yaml:e55e9f0d8cbf44242f239ee96f46a5e068bc964b +http/cves/2021/CVE-2021-24340.yaml:5eb1cc4fa005fba76e0b923104e2e7d8e3064d95 +http/cves/2021/CVE-2021-24342.yaml:f9bc4c12b5a0b283a133b1c28e36501b516c19a7 +http/cves/2021/CVE-2021-24347.yaml:04ed6560ab756f2c9d5b650aadb4ba6d62d8137c +http/cves/2021/CVE-2021-24351.yaml:f0f9cdbe962aba9bc9f5718381b50fae0115a7c0 +http/cves/2021/CVE-2021-24358.yaml:cfae0e66c9a809a6ec567391ce0c7c9750cb87c0 http/cves/2021/CVE-2021-24364.yaml:cd73eba83d8e7a54b7df422cb431af3871c666e4 -http/cves/2021/CVE-2021-24370.yaml:32422d69279f351506cf204bcea67a667607123d -http/cves/2021/CVE-2021-24387.yaml:5121ec513ee170de00dbea2e637854d64ac78f52 -http/cves/2021/CVE-2021-24389.yaml:230860e74044d2a89563dba1ab1b7be7106822db +http/cves/2021/CVE-2021-24370.yaml:dbc24d364efd4a536293381c0606abba9484f8a4 +http/cves/2021/CVE-2021-24387.yaml:a6c5d1608ee5c88c90a45787d32b7cc307697c5d +http/cves/2021/CVE-2021-24389.yaml:57a5ac5f09a5befdf83ac8a68f4e75652beda048 http/cves/2021/CVE-2021-24406.yaml:d48dd317c511a4b28b53028e9bc6a7bd647f2308 -http/cves/2021/CVE-2021-24407.yaml:c9f66ca184a7c490e436c202ee30b946e0d7e70f -http/cves/2021/CVE-2021-24409.yaml:03b30b435bdac5842f2dd68813a1f77289d8c8cd +http/cves/2021/CVE-2021-24407.yaml:035f853130630d185e6a432d409c486341644e82 +http/cves/2021/CVE-2021-24409.yaml:30b8c5f14e03b5e7ea0392e3e978f7e4f9be2818 http/cves/2021/CVE-2021-24435.yaml:fd23f9a67e0bc900a755ed83bc7e1539961eaf5c -http/cves/2021/CVE-2021-24436.yaml:5f9cd7e2808950a63e50574f41c72d5ff15252f9 -http/cves/2021/CVE-2021-24452.yaml:565fb0e4b286bec9b0d163c87be41029a92c0597 -http/cves/2021/CVE-2021-24472.yaml:e4f550359ef50e0b1b7dd825614ac3f077a53b17 +http/cves/2021/CVE-2021-24436.yaml:6a880b73687dd74d4adcf74a53a65cf4ba64025e +http/cves/2021/CVE-2021-24452.yaml:a775c95e86ddc176888d530c42d34618a5144d2d +http/cves/2021/CVE-2021-24472.yaml:4a37f7aa7e7303d39f58f900de27cf7197a0d379 http/cves/2021/CVE-2021-24488.yaml:46eb567632e22f429fde73962e23df298c731367 -http/cves/2021/CVE-2021-24495.yaml:69d37bf3b8b2e8395209dbac2d290aad1fa1b2d9 +http/cves/2021/CVE-2021-24495.yaml:26942ddffdd85b10fd9e5515c46741c174685c50 http/cves/2021/CVE-2021-24498.yaml:fbff56e3891abd295dceb944374dd0127bee0d57 http/cves/2021/CVE-2021-24499.yaml:831cc030766407c460c8a47929549fd9e6ed10f5 -http/cves/2021/CVE-2021-24510.yaml:51b9af4c83f10ad2c55af750ecfdd6d317a5647f -http/cves/2021/CVE-2021-24554.yaml:eb4f1db0bcaadbf47faa4e5e33e80fae7022d54e +http/cves/2021/CVE-2021-24510.yaml:87a23b6cd31c8a63f0a6469e9590a5a7a36ce34b +http/cves/2021/CVE-2021-24554.yaml:56744410d5b067a9f574f9db96290d22643b741f http/cves/2021/CVE-2021-24627.yaml:0ccf3179be4754f2ecc7ebb819ef51ef73e0c21e http/cves/2021/CVE-2021-24647.yaml:97b0ea1a45964e8f1f7d8c753c37742967622fea -http/cves/2021/CVE-2021-24666.yaml:5b93e7b2921b35382e1567c778e5fedb2679e008 +http/cves/2021/CVE-2021-24666.yaml:d394db79ec62cb1484ffda3745407189f64a4eca http/cves/2021/CVE-2021-24731.yaml:9e9814c360d287e7b7d59fa2a63d657c62647eb1 http/cves/2021/CVE-2021-24746.yaml:6db3b7be362e8b4b7ed567e2eaf78dd17f5eda90 -http/cves/2021/CVE-2021-24750.yaml:c8bc69d45f3384d75f4421655dd71d42b5d64ff0 +http/cves/2021/CVE-2021-24750.yaml:14405e4790853d1d4a26374f9a6eb78d9647237a http/cves/2021/CVE-2021-24762.yaml:be86d5e3c96550b576cda7c2aaa872a8eb34cb22 -http/cves/2021/CVE-2021-24791.yaml:d8e8c2708e7b27f880f7247046ace05e71c75a9d -http/cves/2021/CVE-2021-24827.yaml:c9e185ae51e83e4046c07fb0ea397459740e28dc -http/cves/2021/CVE-2021-24838.yaml:a5d2bbf2a60536f04a4b865e95412101c55779aa -http/cves/2021/CVE-2021-24862.yaml:34bbbcf3d5e1dabf10b641da4f79fd3700496b1d -http/cves/2021/CVE-2021-24875.yaml:f848cb9a6d169b5734fd3383f446c926c1b9f240 -http/cves/2021/CVE-2021-24891.yaml:9e85efa72da66a1ee080d6e90c76a465f6efc1bd -http/cves/2021/CVE-2021-24910.yaml:af033303f80efcd8bfe6a72a75ffc90acea964e5 -http/cves/2021/CVE-2021-24915.yaml:b5c5c798b558956a83b888a1d02e1b15fad8e2a8 +http/cves/2021/CVE-2021-24791.yaml:c87e6fe82d0568d2fa8b33215f4512bdc9e6601b +http/cves/2021/CVE-2021-24827.yaml:ce9bf47a81759f7d00b3e1880621177e3fae0715 +http/cves/2021/CVE-2021-24838.yaml:91ded7a5fa2597d25a32c89d842c6631ae08d13e +http/cves/2021/CVE-2021-24862.yaml:e370d58ffc1769b743e0a849d36f45cf234225d4 +http/cves/2021/CVE-2021-24875.yaml:d682f84e64625fe6bb076cd49ce1bf925835ad91 +http/cves/2021/CVE-2021-24891.yaml:ba2f7b4ea937c57a1b76a2bf0551336a5de7e490 +http/cves/2021/CVE-2021-24910.yaml:dfceefc1355075227a4afe0c4965f4f0b680cb83 +http/cves/2021/CVE-2021-24915.yaml:8754b261f19840a032104d812b9b4b3ffa482388 http/cves/2021/CVE-2021-24917.yaml:91807d1423939168a7a3e129be2e5eb570bd701b -http/cves/2021/CVE-2021-24926.yaml:750d850be4d48f8bc2bb9459a2c3e326ab6f35a1 +http/cves/2021/CVE-2021-24926.yaml:7e971821d29f5f53d8506d361431dffd48664e17 http/cves/2021/CVE-2021-24931.yaml:937b8f0845e870e7fdd0aa9cb9f8d97348c5ff82 -http/cves/2021/CVE-2021-24940.yaml:5960ef8464cc4a673439005b733fbffe6f7bdb9c -http/cves/2021/CVE-2021-24946.yaml:76204e6c632af2d8ff6966ff4a9f90fc72ed3704 -http/cves/2021/CVE-2021-24947.yaml:0d2f5a9fe029367942620677561adb94ae98adf4 -http/cves/2021/CVE-2021-24956.yaml:a9d2ed7764293417cff28b4d2b1839dcea9813cb -http/cves/2021/CVE-2021-24970.yaml:8915fb2a644b576f0ae64de1517f387737eaf01d -http/cves/2021/CVE-2021-24979.yaml:73512f0520839350cc2166e7042de2816e34f2f8 -http/cves/2021/CVE-2021-24987.yaml:46e064c2bf066acc7a20dd4eda00159e90f4baf5 -http/cves/2021/CVE-2021-24991.yaml:f29a1343c775552d7ad5af751dfb963f3499db39 +http/cves/2021/CVE-2021-24940.yaml:2f5af8464380692b2786313be684eaa8685ab975 +http/cves/2021/CVE-2021-24946.yaml:953efb1fa63aa6e8ed8d841b833f97ecbe22c3ac +http/cves/2021/CVE-2021-24947.yaml:50a8f3c1b7a1cb2a352dfa1c6e6256e99fa4304f +http/cves/2021/CVE-2021-24956.yaml:e16560188d0d1b1464c6559b4a76d1419f3a3219 +http/cves/2021/CVE-2021-24970.yaml:1d6bed2ef2b872364b86e413814e5db35910c3fc +http/cves/2021/CVE-2021-24979.yaml:8f64d8c8e664c9fa8b03f95088b731bc505d7039 +http/cves/2021/CVE-2021-24987.yaml:a5eb92f857297846e6a4112fe66fb62d55451595 +http/cves/2021/CVE-2021-24991.yaml:771caa271bfc81ddf546073d02f4352b36575059 http/cves/2021/CVE-2021-24997.yaml:b9f857d08a8b01f17311bcde0532821a0122b437 http/cves/2021/CVE-2021-25003.yaml:70b5ba3a19ec728ef248d3b9ce563e809ef4f200 http/cves/2021/CVE-2021-25008.yaml:1dadb9552fb39888e2cc2b6f08eb34c2ea5946bd http/cves/2021/CVE-2021-25016.yaml:11dd311f7b70e22b3b1583cc9715d9027a18f6c5 -http/cves/2021/CVE-2021-25028.yaml:883e16c46556376b8da581ecd373475b586b4da1 -http/cves/2021/CVE-2021-25033.yaml:76fe1d03d687cdceb06c378f59b08b6af6f5a298 +http/cves/2021/CVE-2021-25028.yaml:82e15f12b4ae4eb4f1c6eebed23797fa7f6f56c5 +http/cves/2021/CVE-2021-25033.yaml:ca0be2faafe49b4dccadd5730adafb20f725e747 http/cves/2021/CVE-2021-25052.yaml:38288001159dd96d376f735f9de2a0aa0ddb75ff -http/cves/2021/CVE-2021-25055.yaml:5fc8d6c26dbf424532ea6ec14aed7c6c2c2209af -http/cves/2021/CVE-2021-25063.yaml:04796d820df4cd2977af38198de006f0b42699e5 -http/cves/2021/CVE-2021-25065.yaml:a7f67aec080f2e8a961aea88960d8737d1c5ad8b -http/cves/2021/CVE-2021-25067.yaml:81095dbd23860257695716bc80999c47253c499c -http/cves/2021/CVE-2021-25074.yaml:e22c32ee1cdf921cd3e4c96adead2b0c168655e0 -http/cves/2021/CVE-2021-25075.yaml:55407c753860bb9bb3a6c14552a039b3edca40fe -http/cves/2021/CVE-2021-25078.yaml:5ad97010ccebc67485e01aeb57c034866a88dd3b -http/cves/2021/CVE-2021-25079.yaml:ccc266602fd7f86e5b30eef4bbd9ac3137de1a9e -http/cves/2021/CVE-2021-25085.yaml:1998e855f6fe29f11a1a4fecbe46d98403560f46 +http/cves/2021/CVE-2021-25055.yaml:204115658b5934f54e1eea72f066251607c9dce5 +http/cves/2021/CVE-2021-25063.yaml:530ef3821f5ef0c65b4d912cf9e4854771d544ad +http/cves/2021/CVE-2021-25065.yaml:cc16a1bfa129c97b28ec8373435cd79777bbefc7 +http/cves/2021/CVE-2021-25067.yaml:7a60991efefea6a3ce3756c3af894f2aab580ac4 +http/cves/2021/CVE-2021-25074.yaml:f41f0875984a12ea9a157f30533229637d817fa5 +http/cves/2021/CVE-2021-25075.yaml:e91989bd12969d5a0ed4ff3a324fc59c623cc077 +http/cves/2021/CVE-2021-25078.yaml:20f55f0bdae1eb8070dc9d7ad6d0437c64072726 +http/cves/2021/CVE-2021-25079.yaml:73e6807f020492d5b08f33e9196d2f8cd65c4ddf +http/cves/2021/CVE-2021-25085.yaml:f70f7615bc02daefaf4716e3f5e4dbd6fa22b646 http/cves/2021/CVE-2021-25099.yaml:8766d042026f5f0efcb0b62cf027b3227a10d66d -http/cves/2021/CVE-2021-25104.yaml:7d20e66af531c5b0843a841739901761f7d0588c -http/cves/2021/CVE-2021-25111.yaml:8bc63fb8643d4b1e2aa3e83a0cd7d73956231717 -http/cves/2021/CVE-2021-25112.yaml:36181e17317ad00e53d2bd2f37ec7d9e15bd5fd7 -http/cves/2021/CVE-2021-25114.yaml:7d305a89b8b3a4f9b39fd91c4f31c63aaaeca9bf -http/cves/2021/CVE-2021-25118.yaml:e2bd1581fc7299b35748ce2c06ca2062a740d016 +http/cves/2021/CVE-2021-25104.yaml:2aee702a42e8c0b59334596ce2086491edab046f +http/cves/2021/CVE-2021-25111.yaml:1c1743ca24e07baba06d4b69d421a09e9aa2c036 +http/cves/2021/CVE-2021-25112.yaml:a5c14ef6bbcc67875a0c93272a932ead9407db87 +http/cves/2021/CVE-2021-25114.yaml:0927dd8e14b56ce5e71476455b6d814e191739c8 +http/cves/2021/CVE-2021-25118.yaml:29073cbdecc570609e340076b4bb5d12b4952900 http/cves/2021/CVE-2021-25120.yaml:a191dd4039d8e952a369d4076fafa334c7e5fc60 http/cves/2021/CVE-2021-25281.yaml:01795568a5b5c14a3034cdd2f1b039d532b29de4 -http/cves/2021/CVE-2021-25296.yaml:9536286be7d517b7904361639d1a8201e4af3f11 -http/cves/2021/CVE-2021-25297.yaml:0db477d51820173414e99a10162c2a28bfcf3836 +http/cves/2021/CVE-2021-25296.yaml:05facb32aff50308862e8cf8e4e4977404f745dc +http/cves/2021/CVE-2021-25297.yaml:05daeedfcc856ed121960e66b36d8b73d94ee253 http/cves/2021/CVE-2021-25298.yaml:fba9238a2929f6993a0acfd8d3eab8b5104b920f http/cves/2021/CVE-2021-25299.yaml:6a23a8b3f3ce755ea7384b57d29d9eee3796f898 -http/cves/2021/CVE-2021-25646.yaml:2ab3a9110f32be424eddad866233c82b271db61d +http/cves/2021/CVE-2021-25646.yaml:e3a9457ec09973a1f126fba61045cb6b3ab37f87 http/cves/2021/CVE-2021-25864.yaml:7faf664337114445590bc1e8520b9d1c181b5388 http/cves/2021/CVE-2021-25899.yaml:0af1b8d1fd23ec020428d8ad4cd1d2110309575d http/cves/2021/CVE-2021-26084.yaml:ae23cf1c29fbe68b99c2b93cd45c549ed9cf677f @@ -1868,15 +1868,15 @@ http/cves/2021/CVE-2021-26085.yaml:b50d2d7c6104de0f0d866f32773b40327658d11a http/cves/2021/CVE-2021-26086.yaml:5709bd13a1a3fa98fa0cd16c60b2d84c6a11ae35 http/cves/2021/CVE-2021-26247.yaml:989d0e368e81e3c83c10ae0037d56f5ffdd142cf http/cves/2021/CVE-2021-26295.yaml:c8d7e1476212bc9c7a8a77126ee529883b7ff641 -http/cves/2021/CVE-2021-26475.yaml:411740f2d55a0b2b3a33c2998ccd7d990be58277 -http/cves/2021/CVE-2021-26598.yaml:04ff0d5ed23430adfb36e16ebaedb4b67ebc7652 -http/cves/2021/CVE-2021-26702.yaml:74768c4040f30c6fb5a7649188748eb12b22d041 -http/cves/2021/CVE-2021-26710.yaml:33eb1f1ae0114bc531484e4013fd42af6913fef2 +http/cves/2021/CVE-2021-26475.yaml:5633026565106a62eac02efe59a899c76068a0d3 +http/cves/2021/CVE-2021-26598.yaml:6716928b4f2e8b6676e5f7ea603b28ebfff1a631 +http/cves/2021/CVE-2021-26702.yaml:31157919a03902ee3249e53b2b2fca5a0d65ee70 +http/cves/2021/CVE-2021-26710.yaml:86d6438af78bbbda406a9b2718473d165fdbf4f9 http/cves/2021/CVE-2021-26723.yaml:12727b199d59a1582471ecec4266ea90829d10fd http/cves/2021/CVE-2021-26812.yaml:80bc05ee895819f5399dc5cc00d36b97e182704b http/cves/2021/CVE-2021-26855.yaml:888f79e8303423a1b42bc5dc34793944313b51c4 -http/cves/2021/CVE-2021-27124.yaml:a7507279f796da9645d7743f5be7444656c57ad5 -http/cves/2021/CVE-2021-27132.yaml:972bea4c9edd8d89ea76e1a8292f94d979ac8b69 +http/cves/2021/CVE-2021-27124.yaml:29aa9f057d32439020f7672cac688618899156aa +http/cves/2021/CVE-2021-27132.yaml:649f950f0fddf8cca3ba287cf96bf48411a2069a http/cves/2021/CVE-2021-27309.yaml:47e9208beb8cacb60633177de9a491f7c46b76c3 http/cves/2021/CVE-2021-27310.yaml:5407fa202cb33b9ae19f6d3b368c4c8538508cf3 http/cves/2021/CVE-2021-27314.yaml:e4d6e6a1630323a1e0b9358a20b23f1a0625e2f1 @@ -1884,980 +1884,980 @@ http/cves/2021/CVE-2021-27315.yaml:36f779594a8c1e5e17c264570438f50a4ff01fd4 http/cves/2021/CVE-2021-27316.yaml:4f8110aba27931f41e27287cfa27af75615c0a89 http/cves/2021/CVE-2021-27319.yaml:eb2abb53e913dee6f2dfe635c97a951557beb509 http/cves/2021/CVE-2021-27320.yaml:5120e1126d55bb3c7f3633b3048eb3f6c6531b38 -http/cves/2021/CVE-2021-27330.yaml:77a7238dd95a06c856b54cbdb55ef865f6ccf3fc -http/cves/2021/CVE-2021-27358.yaml:ff3e27162edd4d93c7f5ac62c263e619acb144b0 -http/cves/2021/CVE-2021-27519.yaml:5ffd399fda981817efef2beffc7dbfe234d86bf0 -http/cves/2021/CVE-2021-27520.yaml:fbd86007bf2d5f876d563a97f773be383acffb60 +http/cves/2021/CVE-2021-27330.yaml:2e69424ca9a8328f839d529b38322e7978eeedc2 +http/cves/2021/CVE-2021-27358.yaml:02d1a57321c0e0c8830135018b4799f0387954d8 +http/cves/2021/CVE-2021-27519.yaml:d960f19cf1b723486fb4529a5d0619b46683b48d +http/cves/2021/CVE-2021-27520.yaml:083022057253cf9041b6ee67d4765ec9890f6068 http/cves/2021/CVE-2021-27561.yaml:dafaa076a3ed890e05f62d1fc2dc64b2660840d5 -http/cves/2021/CVE-2021-27651.yaml:d05084f452d1910705eb87021e507ed5db0d0a72 +http/cves/2021/CVE-2021-27651.yaml:eb438306a06f9279bee4ed52dcf66468f08f8f4e http/cves/2021/CVE-2021-27670.yaml:b8d56698d05edc1d55f4b20d66677621407d40f6 http/cves/2021/CVE-2021-27748.yaml:eba210d13902f5a60cff6a0fcabef2449a30459c -http/cves/2021/CVE-2021-27850.yaml:5ff0f60339969cac148b2e2bc02dd5115eaeb451 +http/cves/2021/CVE-2021-27850.yaml:b889c20b4a84ef05043eb3ed98dfc8a5bf9be363 http/cves/2021/CVE-2021-27905.yaml:cab2fae66051d9136b53c61bdfc23cff3c5800f4 -http/cves/2021/CVE-2021-27909.yaml:d7683c6966ad02b55d19190f7bc428fcf7cb936c +http/cves/2021/CVE-2021-27909.yaml:6d317121998465e55aa2cbe13238d42d86d10e26 http/cves/2021/CVE-2021-27931.yaml:63b7c42f16619354693d270154d29256713dde3a http/cves/2021/CVE-2021-28073.yaml:3708c1b88bb493d026117d61d8a0aa9fb020c5a6 http/cves/2021/CVE-2021-28149.yaml:3e3a7519cdbe6f7c851fbefbad8ce5fea0d2f34d -http/cves/2021/CVE-2021-28150.yaml:b0cefbbf02b3e4915d401d8898f80de2bdb47258 -http/cves/2021/CVE-2021-28151.yaml:70ed5ec56fdb706fbfdf522afb9e30242636516d -http/cves/2021/CVE-2021-28164.yaml:3838abd1a49017305bab1622ccf38a4bfc6c247d +http/cves/2021/CVE-2021-28150.yaml:e873a52885a8456ef7c02bbc3d547223b259f88e +http/cves/2021/CVE-2021-28151.yaml:e99145eefc1bb5f859d15ceb73f03ec7f6c4b143 +http/cves/2021/CVE-2021-28164.yaml:ebfc8036cf75a389ec67d441fb1a8c5116cccf8e http/cves/2021/CVE-2021-28169.yaml:a8bf2420e1956754a3aae43c14d35312cd49d128 http/cves/2021/CVE-2021-28377.yaml:5e5aa363ab753a511a9b5ee6f08ddf3dc3610f62 http/cves/2021/CVE-2021-28419.yaml:a07bdb23bdeb9b12ae15226e63508ae7e17f0248 http/cves/2021/CVE-2021-28854.yaml:f642fff6999a311047096aeda3bd595410be28be http/cves/2021/CVE-2021-28918.yaml:d592938ddaad226edbf03cb6ffb56d95f164b582 http/cves/2021/CVE-2021-28937.yaml:d5f382312a34d265cb5700df7d8202ae67f2794c -http/cves/2021/CVE-2021-29006.yaml:e9a9b0aa7f2a3829bacee7a40b69cc2f71e8a0b5 +http/cves/2021/CVE-2021-29006.yaml:5620d8ea42680a34d52670493830481cce752f46 http/cves/2021/CVE-2021-29156.yaml:62717b070b15edac1af480378a88fdd706ff5779 -http/cves/2021/CVE-2021-29203.yaml:04a657497d650c04a0a07cd4b1fd85804ddc672f +http/cves/2021/CVE-2021-29203.yaml:0fb67031d79bd85f66591de492b11801527850d3 http/cves/2021/CVE-2021-29441.yaml:d1894e9dbb6fd6edd02fad9802b6c4d69236573a -http/cves/2021/CVE-2021-29442.yaml:6a796f9a2fe048e3fcc89fca64daeb9713a8743a +http/cves/2021/CVE-2021-29442.yaml:611278ba14367739fdb744ec807b9ebd7a9af0c9 http/cves/2021/CVE-2021-29484.yaml:0939cdfd12d426fd3ac5ba24a7b5c7effbb36f27 -http/cves/2021/CVE-2021-29490.yaml:a5c5e274684ad2e9296b9975c111e62c66721a51 -http/cves/2021/CVE-2021-29505.yaml:7374b82ae1ffd5eec32eb056b7beb55436391fd6 -http/cves/2021/CVE-2021-29622.yaml:75bbc2ec3f48a01d028682cb02875a97b71c831f +http/cves/2021/CVE-2021-29490.yaml:873767111ffbe3e98c6f8a49a5cc639e98e519da +http/cves/2021/CVE-2021-29505.yaml:012a58d35fb66bcd92f09b803bb925eabcd378a1 +http/cves/2021/CVE-2021-29622.yaml:be6dc2e6ba9ab99fa43fdbeb423c5792bf47ae17 http/cves/2021/CVE-2021-29625.yaml:9b6af89a3d20c52b8eacb4143858d13d9bb31f1d http/cves/2021/CVE-2021-3002.yaml:29d4442472d307174f7133b588820ed480dec7a9 -http/cves/2021/CVE-2021-30049.yaml:2517f048352df3a2e6ef6d563133da8f956f5f31 -http/cves/2021/CVE-2021-30128.yaml:c09cddac200b2fdf5c8f558dec4de47eea6509c7 -http/cves/2021/CVE-2021-30134.yaml:6c6abb28041fefe58f536f5839fc482b9b91e2c7 -http/cves/2021/CVE-2021-30151.yaml:82507aae4deabbbf2b592c44d846e1afa283f5a0 +http/cves/2021/CVE-2021-30049.yaml:b98c0e45e441d996a54a35cd9b05d8460fa56759 +http/cves/2021/CVE-2021-30128.yaml:424542418e6619e429b6594b2e338fe86c72454e +http/cves/2021/CVE-2021-30134.yaml:67ea58132a0029536b3161e5ea237974842a10cf +http/cves/2021/CVE-2021-30151.yaml:e42e58a3db4d87e984ad43e67c99cc102e62b314 http/cves/2021/CVE-2021-3017.yaml:aaaf8fce51edcf312d10e6b48167fca1cce1d507 -http/cves/2021/CVE-2021-30175.yaml:aecac3f53578f8dacc1fb5cef60d5dc457cfc6ca +http/cves/2021/CVE-2021-30175.yaml:e00661472a4e0144101b49e79277ac0323d29d7c http/cves/2021/CVE-2021-3019.yaml:b9103b98d4b0a989470ad57c4db6a0e13118ccc5 http/cves/2021/CVE-2021-30213.yaml:66a61c251c31f7f37e72f7f73c75d0678edeb88f -http/cves/2021/CVE-2021-30461.yaml:606942dda16532fcd4a492e4eceb02ad9ae8870c +http/cves/2021/CVE-2021-30461.yaml:720f9ce7a01fc6321f419bad8d5aea38dbba56f2 http/cves/2021/CVE-2021-30497.yaml:0b760a8120737b3c0a15e99e7f8dfc93785dae24 -http/cves/2021/CVE-2021-3110.yaml:82c2671259ad3095b8c9d709e2fb94a7ba610621 +http/cves/2021/CVE-2021-3110.yaml:31ba38c92dea4189ea4130379b21b4b093cb0513 http/cves/2021/CVE-2021-31195.yaml:bb7ff2edd92cc80fe6b691a7b711595ec7eb7bb1 -http/cves/2021/CVE-2021-31249.yaml:d8c55d26bf52ad6786778dabfdeb51eb72da24fe +http/cves/2021/CVE-2021-31249.yaml:c48257b587cc9ad5631d1c71a257e36d7f1fa372 http/cves/2021/CVE-2021-31250.yaml:152e29be2302870e4b12c24f7520b262b1299074 http/cves/2021/CVE-2021-3129.yaml:1eaab4e1e7b4218694876b25831680b5e7341cd0 -http/cves/2021/CVE-2021-31537.yaml:3892972d7eafc105229fe4bc99aeb6bb0e88cf38 -http/cves/2021/CVE-2021-31581.yaml:af1136e5b75fb5048a9be0a479235843b5937561 +http/cves/2021/CVE-2021-31537.yaml:9a6e4e37ad1d220a86830d6c21d64ff56329fba6 +http/cves/2021/CVE-2021-31581.yaml:9242498ce0362ff9ffb295dc7a9cc2c3b98f5338 http/cves/2021/CVE-2021-31589.yaml:470855782a2271fcf09aa48d3f5482bd82c8a845 http/cves/2021/CVE-2021-31602.yaml:d63e2a21c6fc44328b3c7e7e6fb82771744f79c1 -http/cves/2021/CVE-2021-31682.yaml:509166ccb8c8d62bbadbfaf6385d34610e6f4de0 -http/cves/2021/CVE-2021-31755.yaml:019fcaf5984f8053602563db1a0690605a42dbba -http/cves/2021/CVE-2021-31805.yaml:9158f705cfe15c89621634cd40ac60df5bd41ee2 -http/cves/2021/CVE-2021-31856.yaml:0f90b911855d7aa99cc4de1bbf1511e062b98908 +http/cves/2021/CVE-2021-31682.yaml:67205d6821c816a48af4fab693095753b541c92f +http/cves/2021/CVE-2021-31755.yaml:09dd92c03aef5f833527a009ffb160ea5f338293 +http/cves/2021/CVE-2021-31805.yaml:a6853fd5fe412d88b8931106608e59ddb4082aa3 +http/cves/2021/CVE-2021-31856.yaml:a43db060d440748d3de2f14d681b46b55ba8f603 http/cves/2021/CVE-2021-31862.yaml:ad2a5b936b5ab471dac82487ead2b47b1344e76a http/cves/2021/CVE-2021-32030.yaml:2206a689042dc6a741ab98d0308d79aa38b06868 http/cves/2021/CVE-2021-32172.yaml:bbfeeb46ebd26b3309bb08da6eb51cf0ff747a02 -http/cves/2021/CVE-2021-3223.yaml:ee5c2c5202342ef13238f5159a02574e7566e16a -http/cves/2021/CVE-2021-32305.yaml:fd62fd78ccbeeee622c41c1095c202061a13d1e7 +http/cves/2021/CVE-2021-3223.yaml:1db42ca20b8100b89fe62c723b2f46f73d596b46 +http/cves/2021/CVE-2021-32305.yaml:d713ba969540ee9688eff02d76b6c9aad94fdc5c http/cves/2021/CVE-2021-32618.yaml:da9452ff7c0f34aa114240c91bb5c9cdb3de75de -http/cves/2021/CVE-2021-32682.yaml:85dd8999f344e34b384301ec0010206b056cb97a -http/cves/2021/CVE-2021-32789.yaml:5e1a01f1f605c6b083c14ab3baa47414d5f684df +http/cves/2021/CVE-2021-32682.yaml:f37d3b9c6fa5895bb2d1fcb5bde0196bfa07ef5a +http/cves/2021/CVE-2021-32789.yaml:bf2124ce14af33d75f852d6ad0ca1f3232a52682 http/cves/2021/CVE-2021-32819.yaml:13d0e2d5e997e3035adbfa71ad0733a2febf5b29 -http/cves/2021/CVE-2021-32820.yaml:d5c89f10d32d6d6726e0a88ac717f3761cecda81 -http/cves/2021/CVE-2021-32853.yaml:fcfe395c71fa5dc036280335a730898013b0ddb7 -http/cves/2021/CVE-2021-3293.yaml:24d868c4faa7c418b6f53e7745d95075f0dad59e -http/cves/2021/CVE-2021-3297.yaml:d9e279272d336d9ddd7d9f0369c384103d16ab82 +http/cves/2021/CVE-2021-32820.yaml:446d66a8324941356f84f4fce3ee6c4a2b9d2129 +http/cves/2021/CVE-2021-32853.yaml:5fd2428765b00dfcfd1def0653b1ed87fbc04d45 +http/cves/2021/CVE-2021-3293.yaml:3e38d04722c603134b873f8d890cdc182fa6afea +http/cves/2021/CVE-2021-3297.yaml:d64a9fe2e38cb9986adedb57c23cacff21c1eada http/cves/2021/CVE-2021-33044.yaml:d53b332d2c9931b7afeb89a370a23d2880c304d5 -http/cves/2021/CVE-2021-33221.yaml:1263284fb1b05f83946866c731885bc66c2e4613 +http/cves/2021/CVE-2021-33221.yaml:3e025760bae829df7f22f52c6485e886aad2b09c http/cves/2021/CVE-2021-33357.yaml:e3864300b02e0163ac14b1dd79575a5cbeeb3a41 http/cves/2021/CVE-2021-33544.yaml:c7bc756bebeba3d06fd5689dd410420d72518d48 -http/cves/2021/CVE-2021-33564.yaml:6862c546912db59c6c98934f67c5665df7a059cf -http/cves/2021/CVE-2021-33690.yaml:52267b9fdc3574a497bfdb7140249d38a3f4d908 -http/cves/2021/CVE-2021-3374.yaml:4f0ea720d7120498637b46f79b6502de94d9fe53 -http/cves/2021/CVE-2021-3377.yaml:3cca52b70208cd97b171c52a7a24054cee4c9189 -http/cves/2021/CVE-2021-3378.yaml:7a424b218e031882afce16778269ca6e3c471482 +http/cves/2021/CVE-2021-33564.yaml:d094b726c090e4b228ed737298e1f01e49faff08 +http/cves/2021/CVE-2021-33690.yaml:1a7ef2c133630b49c0f29973712812d2735852d9 +http/cves/2021/CVE-2021-3374.yaml:30b18b69e521a95f792797ba78fa92a47c942244 +http/cves/2021/CVE-2021-3377.yaml:68fb336ec42873179fc70b479130395b0f7a55d9 +http/cves/2021/CVE-2021-3378.yaml:9ec710fe1dc7ef8a63650e96a6f72e54330efb2b http/cves/2021/CVE-2021-33807.yaml:78954750bac0baeffa8eaa53c911d7b5691916e9 -http/cves/2021/CVE-2021-33851.yaml:3aa451442c3c02e8458ed87f728240bc58c2af42 +http/cves/2021/CVE-2021-33851.yaml:c7c3394602bc8ef2a881c7b729b4f7e74679b512 http/cves/2021/CVE-2021-33904.yaml:a49a0096daf2c5cf25546abbdae2043205acd90e -http/cves/2021/CVE-2021-34370.yaml:2fa39fca4ffee7953b890a35c28a4a2380697dbc +http/cves/2021/CVE-2021-34370.yaml:70bb2078e257895b7ada5b86fd165555f841483e http/cves/2021/CVE-2021-34429.yaml:38f3f516efb9d13850c87b5c26380ad80747e457 http/cves/2021/CVE-2021-34473.yaml:e1f0282a67b836986c1eddfe2b83aa7e32132621 http/cves/2021/CVE-2021-34621.yaml:ab68b4b4fef58f3e7ef0b0aa294b0066c67c3305 http/cves/2021/CVE-2021-34640.yaml:75ee986781d216d65c29bce24b2b7dff14ed1080 -http/cves/2021/CVE-2021-34643.yaml:388112fd23ffd3b4e604b89fffb93279cea517f6 +http/cves/2021/CVE-2021-34643.yaml:7123df5fb94b141e2f8557496541a350c030c8ca http/cves/2021/CVE-2021-34805.yaml:8cb9911ae7129837eabda7e92163d61e44937430 -http/cves/2021/CVE-2021-35250.yaml:70ffa43ce7ec9d5bd6b2fc7eef29e02f51be58f6 +http/cves/2021/CVE-2021-35250.yaml:242d58ff5ae883c85d1a1cb01f63843394edf29d http/cves/2021/CVE-2021-35265.yaml:444352dfe2f43c0eec7e6b900f139163d41677ad -http/cves/2021/CVE-2021-35323.yaml:60f97b9824687e622c8e1b1c2a007156a64b1ae5 +http/cves/2021/CVE-2021-35323.yaml:8981dc4224de9625bf9cef3b9a98e47ec61bf117 http/cves/2021/CVE-2021-35336.yaml:0f7aff9f063f1a0b4a9fa3ebaa02494271b2bf47 -http/cves/2021/CVE-2021-35380.yaml:c0d6f92995f04fd23cd398bac8dc52b1c36e381a +http/cves/2021/CVE-2021-35380.yaml:d0ecfd1d0824570af15fb6f0d86d6e41bf31fff7 http/cves/2021/CVE-2021-35395.yaml:dd5bab19fe75503bef4bca96224e8cc2fd61d46b http/cves/2021/CVE-2021-35464.yaml:030f5276cdec07ccb643f1ad74fe88888bb1aaef -http/cves/2021/CVE-2021-35488.yaml:146a5d2fc8710bd398c89501fdedb4d246fabd57 +http/cves/2021/CVE-2021-35488.yaml:031fe24fd4bb05ef894765be115658e2b0b59cca http/cves/2021/CVE-2021-35587.yaml:563ac26feb7a861512cc9c3e9e24d0daee14d50d http/cves/2021/CVE-2021-3577.yaml:33a18c04f484b06948cf394a60f411aede7e2af7 http/cves/2021/CVE-2021-36260.yaml:60b8b65f95ef09103c7b1b91d88e8877ff7a9f92 http/cves/2021/CVE-2021-36356.yaml:333743e8bbce6398ff562d6b59670a7b8f86044d -http/cves/2021/CVE-2021-36380.yaml:cf916e1d0ed9985c858b9965bf9bbb96464edff4 +http/cves/2021/CVE-2021-36380.yaml:3c18a034177a55c84d94128bbbb9684734bca73c http/cves/2021/CVE-2021-36450.yaml:653078da8fa5f20db00c14ed2b97bc09f9b1ae87 http/cves/2021/CVE-2021-3654.yaml:7c18086eba1ddab1cd0224fbc7f6fcbde2ee9acf http/cves/2021/CVE-2021-36580.yaml:ba91319bbf8434006e22c1ad09489360922ea809 -http/cves/2021/CVE-2021-36748.yaml:eb60d7b00cfa69edf5f00513922e3336154dc8f3 +http/cves/2021/CVE-2021-36748.yaml:fe7c92c91b3e712f3bdd74e5ddb3abe66f3ca191 http/cves/2021/CVE-2021-36749.yaml:6a9bc5a90b8b381ca63539c6eced56b444e10f17 http/cves/2021/CVE-2021-36873.yaml:7ea3dd16dcd340df3d670ceaac6c1556ea969ffe http/cves/2021/CVE-2021-37216.yaml:5e5f1a5636b10057e02e50231ef4c663448c3817 -http/cves/2021/CVE-2021-37304.yaml:7e7815e99afe6c38df78f980e07ba106e0af6644 -http/cves/2021/CVE-2021-37305.yaml:294141943cdaa0dd4e663d35a83aea872b8bd0cd -http/cves/2021/CVE-2021-37416.yaml:f000aeaddb066bd8f228fc633f319a8306486648 -http/cves/2021/CVE-2021-37538.yaml:1a9ee4ccbf3c639e9887568e9afe5d48394d5fbf +http/cves/2021/CVE-2021-37304.yaml:0f82d2a333ec761b328e58e3525b4b595f63da9d +http/cves/2021/CVE-2021-37305.yaml:f6e439ca2d118bc5007b906dc370f82d10ac15da +http/cves/2021/CVE-2021-37416.yaml:f6baed18347d103b629905bef667ebbaeb03621e +http/cves/2021/CVE-2021-37538.yaml:b441d545f8c2eae974f967275a65be5c77ee56d9 http/cves/2021/CVE-2021-37573.yaml:a0f0b49a848feea2cb70032f724777e63f4f3199 http/cves/2021/CVE-2021-37580.yaml:2baafd2c04f4afc4b21ce6c0e32a7a7d5ca8f4c8 http/cves/2021/CVE-2021-37589.yaml:1c4bc5e2dc835cc6d600ac0904b3f519f6f79088 -http/cves/2021/CVE-2021-37704.yaml:1244bb8b1b03c1c2b594fc292eabf0d05193659e +http/cves/2021/CVE-2021-37704.yaml:e04a551d0f563b93ef50ed52b61cba4446569139 http/cves/2021/CVE-2021-37833.yaml:14f32085b8ac5c248318ec7d9ec20cf7a9c4b616 -http/cves/2021/CVE-2021-38314.yaml:dbc1c9be2659d62f104159dc821d5ddffad11a88 -http/cves/2021/CVE-2021-38540.yaml:7182a36370768e64a7857b39b91c046163951e8f +http/cves/2021/CVE-2021-38314.yaml:0e7855cf0f4d1fc3f155b6d1a3f2981d5c3f93bd +http/cves/2021/CVE-2021-38540.yaml:3cc76bc03abf5ce7c42a4fbbf8adee30e1189aa0 http/cves/2021/CVE-2021-38647.yaml:18680a0c799e5791fed380cff08a994c8d5c4aef -http/cves/2021/CVE-2021-38702.yaml:3348162f09ba4591dd43ebfc18ed289d19af720d +http/cves/2021/CVE-2021-38702.yaml:a181464423fa132f603306beb7629874d70b4520 http/cves/2021/CVE-2021-38704.yaml:e4181c706e806fbdeb72d2d4de45b226f5bc53a7 http/cves/2021/CVE-2021-38751.yaml:03d9b58f193b388c1c5519327ca0d6f7609cadd6 -http/cves/2021/CVE-2021-39141.yaml:9fc867d8455c7404a4ef1b27d18ec5c102ea2ecc +http/cves/2021/CVE-2021-39141.yaml:6bef694f5350517a9ef44eb5b4d7345d33ac7838 http/cves/2021/CVE-2021-39144.yaml:0eca94200f569ec4aae44292c818280475c1ea90 http/cves/2021/CVE-2021-39146.yaml:71c7de7f0786858f2d445bf4732d8a7bc87435d7 -http/cves/2021/CVE-2021-39152.yaml:3e9ed2ad1978358532f795bcca592af27211fb30 -http/cves/2021/CVE-2021-39165.yaml:e64e23565184c658599714a184bbca2766f8a5e2 -http/cves/2021/CVE-2021-39211.yaml:a00bd25a05633c76c05385b46d60bc4581230b1e +http/cves/2021/CVE-2021-39152.yaml:a67c1c2e9e8949db3a165cfc4e28d780ec075bfa +http/cves/2021/CVE-2021-39165.yaml:839cdf9da7d90c0500e947dcff41dabbb71cb009 +http/cves/2021/CVE-2021-39211.yaml:e46e5c895c8636d3d442d30945eb38340b8185fd http/cves/2021/CVE-2021-39226.yaml:2a2161b415be347ca877e325ecefa694471abc3e http/cves/2021/CVE-2021-39312.yaml:f6a54926cc1941c86410425b27cc14741cca5573 -http/cves/2021/CVE-2021-39316.yaml:9d14b0344fae8931809032bce16c8c3be370ba84 +http/cves/2021/CVE-2021-39316.yaml:a19e876cbbab73fc82249c522108ddf3758a370c http/cves/2021/CVE-2021-39320.yaml:f6574b6d68fde72652355e016cfdcc9b5291bc49 http/cves/2021/CVE-2021-39322.yaml:3208efb57828e7fb2ee9ee41a7ef8f15d8dac63d -http/cves/2021/CVE-2021-39327.yaml:20ee12a65134c623989fe40038c01b2a9c9e7c80 -http/cves/2021/CVE-2021-39350.yaml:91fcc6c54c6cadbc26390d4cfb46bc79319e570f -http/cves/2021/CVE-2021-39433.yaml:30eb31b8859ce10572e078f34d15aea7e63ea26f -http/cves/2021/CVE-2021-39501.yaml:cdede2a072543933050facd7aeb45c23f7f24bec -http/cves/2021/CVE-2021-40149.yaml:3ce9de5064ebcd5a37835f5cf4b4604d0d129733 -http/cves/2021/CVE-2021-40150.yaml:128184ad0543101a9e06aaeca832aac5488181c3 -http/cves/2021/CVE-2021-40323.yaml:fd751766ee136e30a8f3fb06480b0dee093f4a5e +http/cves/2021/CVE-2021-39327.yaml:657438b934ce49b80002d4d30593b4ba810aedd6 +http/cves/2021/CVE-2021-39350.yaml:7be943d4707052db447a305e429fa9d185ff18b4 +http/cves/2021/CVE-2021-39433.yaml:a8b7491d7a9889e795f1e64ff92bea7af7658778 +http/cves/2021/CVE-2021-39501.yaml:94a5ffccfa630c38d10bc2013420ca318c0d037c +http/cves/2021/CVE-2021-40149.yaml:793a4198d34d2593f9bc07fa91352e63ee3cad1a +http/cves/2021/CVE-2021-40150.yaml:e592f8608c3a98aa31b0bfd37b6c5a8bf7d9ec62 +http/cves/2021/CVE-2021-40323.yaml:ec41cf1428b4e3f6b88950ed33643d3b807497de http/cves/2021/CVE-2021-40438.yaml:54c7935653a3b4fe8b4adbc7bb9c153099e53a01 http/cves/2021/CVE-2021-40539.yaml:a0951b062d123ca8f570c2c07b22f40078bb41e5 http/cves/2021/CVE-2021-40542.yaml:744313e8a25f948fb0732fdad10fbdf1ca679c46 http/cves/2021/CVE-2021-40661.yaml:e078e560c0a73365e3c0fd96f5ea003eca809395 -http/cves/2021/CVE-2021-40822.yaml:a9e651f03320ce8b1cab0284b99811b1ed0d8dc5 -http/cves/2021/CVE-2021-40856.yaml:f9d4065a611fe2d0fffb893721701541b0ef481b -http/cves/2021/CVE-2021-40859.yaml:594cbb58945f2f45f0429e4e2f2ce5b871654755 -http/cves/2021/CVE-2021-40868.yaml:7e85ad1445d992312ae100feafdbe14b2dae9c96 +http/cves/2021/CVE-2021-40822.yaml:58d4ae9868102ea227d5d4dc6f6557f3ed18b1fa +http/cves/2021/CVE-2021-40856.yaml:882331dc77a40cae1172bf23b784fe271d09adbe +http/cves/2021/CVE-2021-40859.yaml:74d4d1ffbf37f01e0874e3bdb0ef092aa291a026 +http/cves/2021/CVE-2021-40868.yaml:63715224efd1ea80a9be723cdb8a3455e349aa2a http/cves/2021/CVE-2021-40870.yaml:4b324852b398258d7c4e55538fc32bfce0363edb http/cves/2021/CVE-2021-40875.yaml:a8d964554f515368533af3f5422787266ff9ce51 -http/cves/2021/CVE-2021-40908.yaml:7dcc4995fae30b6070ecaaaf0bf75b36a04ad41a -http/cves/2021/CVE-2021-40960.yaml:816f1b73f781f7884797049ef7d78b99a65f687c -http/cves/2021/CVE-2021-40968.yaml:8b8e78a91f0815f2e8a8af34caa93a53d6bdba4f -http/cves/2021/CVE-2021-40969.yaml:77fbaed84d344cc5097ad1be36878c867d475b6f -http/cves/2021/CVE-2021-40970.yaml:ad236fbb3b009154007f3f998f9a330cfe3dbd4e -http/cves/2021/CVE-2021-40971.yaml:68b01f3857daf55af846e28266c645aa7c4d6556 +http/cves/2021/CVE-2021-40908.yaml:1d6ee4ca10a8b9b2746f2b218ce97475834f8891 +http/cves/2021/CVE-2021-40960.yaml:4100dd979e233446dae0c033f2f4a7b8cc89b448 +http/cves/2021/CVE-2021-40968.yaml:157e564474baf5455b15c81d0b7227ca5cbf23bd +http/cves/2021/CVE-2021-40969.yaml:bef47b3b29cf0aaf91dbc80fb1557c0530c2cb3a +http/cves/2021/CVE-2021-40970.yaml:b5b914123466f242f9163060c81b09fffe51ef73 +http/cves/2021/CVE-2021-40971.yaml:ad5fd682b00f654bceb8d254a52572a3816bc478 http/cves/2021/CVE-2021-40972.yaml:18bb4876ff107de7ba2c56a28a869ef3b36d0a8e -http/cves/2021/CVE-2021-40973.yaml:faff137bd441013a326f8bab819a4b59666a9610 -http/cves/2021/CVE-2021-40978.yaml:db3fc815c7bef4141d67c6cc3751366d214cda1c +http/cves/2021/CVE-2021-40973.yaml:4c404ae0972521ff480a6ec915abbba98ceb413b +http/cves/2021/CVE-2021-40978.yaml:22733fe9ae90216ed0fa206b01f6e4dd5849c124 http/cves/2021/CVE-2021-41174.yaml:5551aacc4e2935b0ef0d83e2ea6759ffaab5f337 -http/cves/2021/CVE-2021-41192.yaml:f6c215c1c29ee87cf89b2d7c00cc4d7b38f6e6bd +http/cves/2021/CVE-2021-41192.yaml:c784108d64e3c3b5e46cd6eedb32af7527a0f742 http/cves/2021/CVE-2021-41266.yaml:31cbe48317f08b85b172ff3dada55d192b8f98cc http/cves/2021/CVE-2021-41277.yaml:04ab938e07a03bb664bab40cd6c6111c92d6d16d http/cves/2021/CVE-2021-41282.yaml:0734ffc47ec7307e273ba16625d4ecafbad62b32 -http/cves/2021/CVE-2021-41291.yaml:30b6337a486cf33b2579f0773b574bfdfca3eea0 +http/cves/2021/CVE-2021-41291.yaml:7120c8fbe68e6502b139b06370003d50d1dea80c http/cves/2021/CVE-2021-41293.yaml:858e3cabf1c630332380a5a23486e5238ed96dbd -http/cves/2021/CVE-2021-41349.yaml:9c0d8187c0831b72128abc2b87b1b22f8b195a14 -http/cves/2021/CVE-2021-41381.yaml:50b68b9115e34c0ba72bebc9b32db00a81da1232 +http/cves/2021/CVE-2021-41349.yaml:b579bc044ee92a90f5d8424e0a133039a2740057 +http/cves/2021/CVE-2021-41381.yaml:6090b32ae9f495f8c2a5f92bf276e36f68a3539d http/cves/2021/CVE-2021-41432.yaml:d2109d524ce5715065d560a9d45108e790e0ef51 -http/cves/2021/CVE-2021-41460.yaml:2fb4d143a39c696cccb1f4d32ec97d0d6ead0b83 -http/cves/2021/CVE-2021-41467.yaml:8e8b56a9c33f41ef3b700961e266d272012f73e7 +http/cves/2021/CVE-2021-41460.yaml:290bdec250c2010a0a0abee80ea8964a338220fe +http/cves/2021/CVE-2021-41467.yaml:9063a0128d8b9eada578e9f558db7b356dc6d235 http/cves/2021/CVE-2021-41569.yaml:b633f8e318290910ce706595b92d77d997305bda -http/cves/2021/CVE-2021-41648.yaml:bd02095d1bf9efaa8142ba0199ae28301520553c -http/cves/2021/CVE-2021-41649.yaml:4bc8292af4d21c7872eda3c6288e0c92b47e7c97 -http/cves/2021/CVE-2021-41653.yaml:1e58212ee066278c059b5c9d0651f061bd832b76 +http/cves/2021/CVE-2021-41648.yaml:42a4dcf8f81b29cf9c7264f9775201e9cc7262e0 +http/cves/2021/CVE-2021-41649.yaml:85628f9007e458a82b17e35f141f1b010e41fd08 +http/cves/2021/CVE-2021-41653.yaml:e82c290f016e6f16cfe8ed728f8bdfc39fd5951b http/cves/2021/CVE-2021-41691.yaml:f598a63d2feec552cd0f7a482d63d3cb99b880f2 http/cves/2021/CVE-2021-41749.yaml:f550d0c1fde0dd181179a4f19adcc82841684399 http/cves/2021/CVE-2021-41773.yaml:083223d5c229ad705177945260a5e899c89c6eeb http/cves/2021/CVE-2021-41826.yaml:8f4709b86814f4c8ba106052268efad0bf48a2e6 -http/cves/2021/CVE-2021-41878.yaml:7678b78e289fa12d2f1959ae13afe5f0907cdc30 -http/cves/2021/CVE-2021-4191.yaml:745fdfcd43181c55da3e9a457688c820a960b384 -http/cves/2021/CVE-2021-41951.yaml:df46ffca494a2f97556d381f5b4cb9e11d45f270 +http/cves/2021/CVE-2021-41878.yaml:287c1eda8be1d47195e12129e2c22ad1eec6a940 +http/cves/2021/CVE-2021-4191.yaml:c86631b4df42ed3c7685f9c9aba89d5d4cfe0586 +http/cves/2021/CVE-2021-41951.yaml:34afe70909f8c7a0dff7579dcbd637b5da9ebbf4 http/cves/2021/CVE-2021-42013.yaml:0064bfe25d40fa26a2bbbec5961917570b2d1c5f -http/cves/2021/CVE-2021-42063.yaml:e39937726165cb008cdb41a817456b4377a017ef -http/cves/2021/CVE-2021-42071.yaml:5cbcb81b06498bedfa49ab79a0bafb70d580842b -http/cves/2021/CVE-2021-42192.yaml:d8f7b6626534bb50bbf4f16f9307033732e0cf55 +http/cves/2021/CVE-2021-42063.yaml:b9352b8cc5ce9a03d85a36677d16c0c24c2363bc +http/cves/2021/CVE-2021-42071.yaml:e15e0e470be393ad2ced976ccfb7a4c429078e0c +http/cves/2021/CVE-2021-42192.yaml:c307948d565fd0d3129e480807b172cb82f96855 http/cves/2021/CVE-2021-42237.yaml:84cca546e31df6ae613b825f3a5085886952eb2e -http/cves/2021/CVE-2021-42258.yaml:10ab86e031bf546bb216972b1fe1ae00fe58a39f +http/cves/2021/CVE-2021-42258.yaml:00855df7114ee864cd8290b2636ed742c3fb56ae http/cves/2021/CVE-2021-42551.yaml:533dbbc2659cc87b5d57beeb7cb2711b86b9bf94 http/cves/2021/CVE-2021-42565.yaml:4fadeda721a9a5c2101ac97b9fd8bde17df86eec -http/cves/2021/CVE-2021-42566.yaml:a8e0d32293d40195415130461c4600c000677f8a -http/cves/2021/CVE-2021-42567.yaml:e545a415dbe03650288db3256dc3b460a0853e50 -http/cves/2021/CVE-2021-42627.yaml:fd5fd450b10c77e2752bc88195dfe9441ce262a4 -http/cves/2021/CVE-2021-42663.yaml:6146c306023ff3727080e710480cd7fe452b749c -http/cves/2021/CVE-2021-42667.yaml:156a245763268af674401752a9604a2ec08a48d7 -http/cves/2021/CVE-2021-42887.yaml:6cf46a77f3b8ad7f6f6ef17f37c792b449da2f9f +http/cves/2021/CVE-2021-42566.yaml:4a04b12af8150a3aa38cfe1d41a673d3941576cc +http/cves/2021/CVE-2021-42567.yaml:162418c1542814a82f7fcf97ae39fa415f0db77d +http/cves/2021/CVE-2021-42627.yaml:595e29d9e884f6804cf8fe834f92fc6e50af024f +http/cves/2021/CVE-2021-42663.yaml:10f15e6be13e64b07a34118fa1afe345a17b7ab5 +http/cves/2021/CVE-2021-42667.yaml:4d9e721701d8fd10b7ac2c87b96767bf721192d7 +http/cves/2021/CVE-2021-42887.yaml:8f09ebbffd290f7736001191a2f6d374497e60d1 http/cves/2021/CVE-2021-43062.yaml:db05bcfc7a8df1f2abe8b26d7ead0ac614841668 http/cves/2021/CVE-2021-43287.yaml:e7aaff40c328b11613f0206a88f2f42d48369132 -http/cves/2021/CVE-2021-43421.yaml:293030b26f79060f71d382e4fba4a9ef5af5d7ca -http/cves/2021/CVE-2021-43495.yaml:c0ab9385e5b9dca8397a9cbdf369c33782d31333 -http/cves/2021/CVE-2021-43496.yaml:34d286112b94d0dff6a8c9a903a3bb527de5702d -http/cves/2021/CVE-2021-43510.yaml:fba1eb9599ba5a16167376d0592866900b062289 +http/cves/2021/CVE-2021-43421.yaml:4c6afff05fb3c0de5ec97ccedaf23799f7f636ea +http/cves/2021/CVE-2021-43495.yaml:a99fb01a1a7d8542e460624783f3894336d6025a +http/cves/2021/CVE-2021-43496.yaml:d18e51a0a6a6a1962942ebe41b3754c6114638a6 +http/cves/2021/CVE-2021-43510.yaml:f8178187e4582030bb6e4fa581e59fec05c6845c http/cves/2021/CVE-2021-43574.yaml:722d801ec41c587902ff541f956569a2d9fd001d -http/cves/2021/CVE-2021-43725.yaml:94c397339fe9f2d3b1bf5b096b0d108e0855bed8 -http/cves/2021/CVE-2021-43734.yaml:1ab3305626a3f46542fe1a4b43ecf795ff229f79 -http/cves/2021/CVE-2021-43778.yaml:bbd95bcd427952ca6a00013cbfd0cfb29ff50eb5 +http/cves/2021/CVE-2021-43725.yaml:dd120a08af376d63ba42050d70cf53ebd19d77e6 +http/cves/2021/CVE-2021-43734.yaml:d937784afa8bee517898f4c72c944962036cc973 +http/cves/2021/CVE-2021-43778.yaml:aca877c84a43fdd9d4f43c6279030d11342152d2 http/cves/2021/CVE-2021-43798.yaml:c9e436eeca1525058449909fc309422b21ad43d3 -http/cves/2021/CVE-2021-43810.yaml:b49220c5edf4d36ec68b922144e2fdd4144e0d15 +http/cves/2021/CVE-2021-43810.yaml:dc3a5e093d9e569a914b9f829fbf720434e67c9c http/cves/2021/CVE-2021-44077.yaml:1121da8afb697598678111f4a0df468835f1602a -http/cves/2021/CVE-2021-44138.yaml:f1cc48f6b00d9a1e7e7877e72c93c1d0235a4615 +http/cves/2021/CVE-2021-44138.yaml:be3b5caa642d8a974f6d7acfab293a1b2180c959 http/cves/2021/CVE-2021-44139.yaml:f317332b7b6e47fdda0d45fa4c567f2eebd5bbc8 -http/cves/2021/CVE-2021-44152.yaml:29d6d5f1573808d179a13ccefc1824a58163fd6b +http/cves/2021/CVE-2021-44152.yaml:cde6f7e27490517a7021e22f974082bf7c812d1e http/cves/2021/CVE-2021-44228.yaml:24f5bbfb015b6a233c0919c871f71fd0408af33a -http/cves/2021/CVE-2021-44427.yaml:c54e0200488c20c3d4ac33c5dad644e7dccbb0a4 +http/cves/2021/CVE-2021-44427.yaml:f89f0c9a6c85756fb88d78be06cc766fa7ce39e9 http/cves/2021/CVE-2021-44451.yaml:08306785c89399ab2eec9b1650e0191f188fde43 http/cves/2021/CVE-2021-44515.yaml:e5d255a3cd31b19fb561e3833d752bf81b43a95f -http/cves/2021/CVE-2021-44528.yaml:15c5bdb3ae5892fc8e0d40932dfe0ff45c031d87 -http/cves/2021/CVE-2021-44529.yaml:5c04138aeedc1481408d2f859af5b9befd82c5f8 +http/cves/2021/CVE-2021-44528.yaml:61751ce0cb8aabc25ec81796066cf34abaeda0e0 +http/cves/2021/CVE-2021-44529.yaml:b9b076ad069848e009a5615004b33d680051f3e6 http/cves/2021/CVE-2021-44848.yaml:32d2824d5e0ea61431fb01045ce53184316e9094 http/cves/2021/CVE-2021-45043.yaml:50136e64ba31e508bc31c0d7f395a66e39c7fe27 http/cves/2021/CVE-2021-45046.yaml:7f90dfa4358faf215aeaa87b826d9e48511eb8c0 http/cves/2021/CVE-2021-45092.yaml:e2fb426a08e596be229fe93f9d5ccd93aa6b067b -http/cves/2021/CVE-2021-45232.yaml:172e9486ce812069cceb4e21dc0edbf33ffdd5d3 -http/cves/2021/CVE-2021-45380.yaml:3111449cd3ff544082f1de7f08d115f12e61c384 +http/cves/2021/CVE-2021-45232.yaml:ef422e648a559960cb47fa13592485944bbd8272 +http/cves/2021/CVE-2021-45380.yaml:9f3bbb76bd5369806cba0522cc8429230cf061e0 http/cves/2021/CVE-2021-45382.yaml:79b3544f900c846a92c08d856b8ee81b854d6856 http/cves/2021/CVE-2021-45422.yaml:77241a87a64a5450a17807520212980b1b7f6cdb http/cves/2021/CVE-2021-45428.yaml:ec519bfedced1b6071a2b23a127a9055f53df86a http/cves/2021/CVE-2021-45967.yaml:6aa4aaf6bed7ebdd867e2fd13b5956f362614c4e -http/cves/2021/CVE-2021-45968.yaml:72a91a73ff4529be9efb2c43ba14a2c745f73daa -http/cves/2021/CVE-2021-46005.yaml:e1e52b7702d29c5cbdc8d8dd45ddbe7e2217db10 -http/cves/2021/CVE-2021-46068.yaml:55b404717972934461e16387c959bdc258141e89 -http/cves/2021/CVE-2021-46069.yaml:baacd876cac8976016fb72678faa4c0bd9cc30dc -http/cves/2021/CVE-2021-46071.yaml:1fce25a3d36a1bcea160a92fb9cf69b75002a2d1 +http/cves/2021/CVE-2021-45968.yaml:efc5a8dc19e18162a80c4e955bcf1a5268b80105 +http/cves/2021/CVE-2021-46005.yaml:827a53a2b2ee09864eaee89e56fb348f14c83643 +http/cves/2021/CVE-2021-46068.yaml:2e505fada001a178da5904c4258b4692d48b6839 +http/cves/2021/CVE-2021-46069.yaml:0c046f03d8729e73f2de807faa73149a9662bfe3 +http/cves/2021/CVE-2021-46071.yaml:b77d1d84622c26fe45bd859e3f79b2472c5b8658 http/cves/2021/CVE-2021-46072.yaml:a7aeae2235686fc1a49bfd069a3876afc241df4c -http/cves/2021/CVE-2021-46073.yaml:c1170aa44d8f24385373b5a82bbf6a650abc4c31 -http/cves/2021/CVE-2021-46107.yaml:17e0ab602ccb97c14be71b40a49f433341b0f4b4 +http/cves/2021/CVE-2021-46073.yaml:f85ff08cde98d217f79af2c5f71f4e60977d9293 +http/cves/2021/CVE-2021-46107.yaml:cdba809e263dcf2d18967cb4b64cf1ff812a3001 http/cves/2021/CVE-2021-46379.yaml:9fb225c3e1d3ab0549098e6473dc2816339e06ca -http/cves/2021/CVE-2021-46381.yaml:b848fd1398b0c7b2f6be4531aeb9a1a0c92f5c4c -http/cves/2021/CVE-2021-46387.yaml:9b2180f46fc06979f003a4c9f73dc68e94edc13f +http/cves/2021/CVE-2021-46381.yaml:7469bda196375f5ac8b242ef3ba56db6d8d593a9 +http/cves/2021/CVE-2021-46387.yaml:d526da59ad24bab02cda504a48d9f3bd6fce2041 http/cves/2021/CVE-2021-46417.yaml:45228a470b64df39e7d3b049cbd519b467c58e31 http/cves/2021/CVE-2021-46422.yaml:859651a9469b81e08fc4ff5e2c8c34a983ee9001 -http/cves/2021/CVE-2021-46424.yaml:530107cf3f9431f8b8adf08bb8d1497956015895 -http/cves/2021/CVE-2021-46704.yaml:8f27e5d7da4d6b88d1aad3daba66721efdd7bee7 -http/cves/2022/CVE-2022-0140.yaml:5593e83f865ae00f0b8fda33d9374631ffe03b4d -http/cves/2022/CVE-2022-0147.yaml:4f477f057da8ff37702adede0007e3146f5acad4 +http/cves/2021/CVE-2021-46424.yaml:dbef8bb1b2cd2264063967ca9dbdcb2f8c53ed67 +http/cves/2021/CVE-2021-46704.yaml:72357d7e6f95da18dced49f6816a10e722eb7f08 +http/cves/2022/CVE-2022-0140.yaml:8fc913baa47dbea91f31040a1584baeae81cf168 +http/cves/2022/CVE-2022-0147.yaml:0c45feb539da64786c0a2739622dced36e4271cb http/cves/2022/CVE-2022-0148.yaml:e9c05967076c64eaee4951240acf8931afbc8fbc -http/cves/2022/CVE-2022-0149.yaml:acc364d7a7331e4b4acc9a6ef75775b30ff678f6 +http/cves/2022/CVE-2022-0149.yaml:fad60f57024beb76e4f1f22bc82f76ee08fc2de5 http/cves/2022/CVE-2022-0150.yaml:22a0f2e8cc8ebda4dff1c1bff27ad22e3b9d59f5 -http/cves/2022/CVE-2022-0165.yaml:e6fe0cf0934e2121942d5e9502c132a56f44430a +http/cves/2022/CVE-2022-0165.yaml:58c081bce0ded089ba6a11c9ebd942f5c972bccc http/cves/2022/CVE-2022-0169.yaml:497c38ed2a935dab0d0cd8b64f06be9550cb63f6 http/cves/2022/CVE-2022-0189.yaml:bf8fe7a83d9280e54794bbbea9b5e6b2dca7b7c3 -http/cves/2022/CVE-2022-0201.yaml:0419030094edde7740b832fa2949646721905060 -http/cves/2022/CVE-2022-0206.yaml:ed7fdf05ef1722e839121be77cbd297c8ea0b183 -http/cves/2022/CVE-2022-0208.yaml:6570a46d95d848a26133444cf95de8c245aca305 -http/cves/2022/CVE-2022-0212.yaml:30e67857a2091d326614014f37d701beaeca4564 +http/cves/2022/CVE-2022-0201.yaml:187406f438edc1ba84d58965bf1b2da60b4571d0 +http/cves/2022/CVE-2022-0206.yaml:1430d8fd11b9b74240d8f6b68c8b5fb6980daa0d +http/cves/2022/CVE-2022-0208.yaml:22d5a15512c3c5339b3719588e72953724e5f1fa +http/cves/2022/CVE-2022-0212.yaml:ac5a8ebcaa1a06701506da7b35933f75dda9bfd3 http/cves/2022/CVE-2022-0218.yaml:12a0c09d459acce22a622c2cce33f3308bd758e5 -http/cves/2022/CVE-2022-0220.yaml:5432a5361b3e36bf9dc0fbaa2939eea87f95fd65 -http/cves/2022/CVE-2022-0228.yaml:a85b0ca2f9793e9088ab515b5a623d32dc23f735 -http/cves/2022/CVE-2022-0234.yaml:306f60f0c0427c52d7a90e61b22c48b2c52db52c -http/cves/2022/CVE-2022-0271.yaml:351aaaa95d5ebfdf65fe8341a4a41f56e11a94bc +http/cves/2022/CVE-2022-0220.yaml:231da6949e320b0828c39a13c9ccb1e499f4955a +http/cves/2022/CVE-2022-0228.yaml:d90e8575b0dd8cea8d600790c35c74f780ddd23d +http/cves/2022/CVE-2022-0234.yaml:ced05e0d496cbfa47cd53928fb7bd6f6cec1c770 +http/cves/2022/CVE-2022-0271.yaml:f4ea18df27d1bbe2fb60939571fcf5d0e09cf516 http/cves/2022/CVE-2022-0281.yaml:11f64d82ba86b3bdcf4d74d20eb5d8e8bf60ef98 -http/cves/2022/CVE-2022-0288.yaml:0bc41b9fe8fb6e2ea2ad5d43370a01be2ef1f88d -http/cves/2022/CVE-2022-0342.yaml:098bafc52abc685d852cc03ed8f982dc3083b41f +http/cves/2022/CVE-2022-0288.yaml:ccb2e255d252f865e7b81128b7ae1f4a0c4210e8 +http/cves/2022/CVE-2022-0342.yaml:439d7b406ea613a244984dcffbd4cad810f93b98 http/cves/2022/CVE-2022-0346.yaml:3d5d9c34b936736af41f3aba5214ff8a53af995f -http/cves/2022/CVE-2022-0349.yaml:275e5326ee04bb4f096e768aae3e93b4cf1d5963 -http/cves/2022/CVE-2022-0378.yaml:52c3f8c5c261828ffa1594832aae84f2618b39b0 +http/cves/2022/CVE-2022-0349.yaml:75dc15a5494117f0a92256040a5619dc5f49747b +http/cves/2022/CVE-2022-0378.yaml:cff99013aafecd8ef33688877e36ab700006d6f1 http/cves/2022/CVE-2022-0381.yaml:722e88acf767f23d17a7ddbe7d1d80efb89421ad http/cves/2022/CVE-2022-0412.yaml:d767355233cf4b88f0fd35fcf51cfa8cc7dfba9f -http/cves/2022/CVE-2022-0415.yaml:4d52da76c69e8bd1c65ff014f66f87ba2c7d55d5 -http/cves/2022/CVE-2022-0422.yaml:3bfb850f50275e29711cf7c0a3fae119fba1e49e -http/cves/2022/CVE-2022-0432.yaml:c90557070b03af85d669970b1c90ea8c5ac4ed04 +http/cves/2022/CVE-2022-0415.yaml:92cef165c9ce2673ea43f7ff90bb4ca9c482275c +http/cves/2022/CVE-2022-0422.yaml:6ef794ed1bac68f162b180535a9a281f52b23c4a +http/cves/2022/CVE-2022-0432.yaml:c8a40b5acc47092706d3f0d2232ab89033cf770d http/cves/2022/CVE-2022-0434.yaml:3b7997b33d7106c0a24ef66503de264455adcf85 -http/cves/2022/CVE-2022-0437.yaml:c1f274f4e08526d8ff786c5e8459cbfed8070dd6 +http/cves/2022/CVE-2022-0437.yaml:7279abca5c79e0a4a28fef3d379e00d1347ab788 http/cves/2022/CVE-2022-0441.yaml:68ca82b5af0464e7d223e173a50f245f93792bad -http/cves/2022/CVE-2022-0482.yaml:5d851123e29f541d807b260a9ea9b2a81ef41d58 -http/cves/2022/CVE-2022-0533.yaml:c984acaf052abe86498f9f3490a8e55aa5368e78 +http/cves/2022/CVE-2022-0482.yaml:cf965444c3397e14fa893185edc980ed137f26cc +http/cves/2022/CVE-2022-0533.yaml:05c5092637a45e386cb394c75d1085c16a2e544a http/cves/2022/CVE-2022-0535.yaml:16e1b22bf4d2ac24bac9c2d6ff7f9118a75c5d14 -http/cves/2022/CVE-2022-0540.yaml:d5c5d96565f913d41b347dab1fe8058641e3675f -http/cves/2022/CVE-2022-0591.yaml:ef6118d4f37589fc8aedc7d4edafe9bfa11e3109 -http/cves/2022/CVE-2022-0594.yaml:8c0b08cdfae3c9e93a1be559c76f0a98b50271ef -http/cves/2022/CVE-2022-0595.yaml:3ccffe03b5f64a1eec8494fefc7eac21084e59ae +http/cves/2022/CVE-2022-0540.yaml:0bcc5859fc33b9eb33a5e8216ec01f48f4e6f51d +http/cves/2022/CVE-2022-0591.yaml:fa036e38e702b266568784049ac5c39c516d87ba +http/cves/2022/CVE-2022-0594.yaml:c1375f9675e31869319a72870e425181899f432f +http/cves/2022/CVE-2022-0595.yaml:1b0e7c591fac08c8abf20791b3936a2fa5705e39 http/cves/2022/CVE-2022-0597.yaml:77e0cd44870a648d0cbf5d249b726767fe4dfa7f -http/cves/2022/CVE-2022-0599.yaml:90a5381a2c177e7727004e04f56bb0707402ef41 +http/cves/2022/CVE-2022-0599.yaml:17f6a343d02a0270223b42eff003d47f761fefbb http/cves/2022/CVE-2022-0651.yaml:b3ac54fb990570ccda3161a027b2bb58ddcc75c2 -http/cves/2022/CVE-2022-0653.yaml:036fd71338dd7e1dcf9caacd42eae21000cb5349 -http/cves/2022/CVE-2022-0656.yaml:a94df464cebdb7a9947a18ac9028203838ba4eba -http/cves/2022/CVE-2022-0658.yaml:45b4d04b5c0953a72f9569057f020a9f959abae4 -http/cves/2022/CVE-2022-0660.yaml:49d21c431040372ab048903634f8139e668700b5 -http/cves/2022/CVE-2022-0678.yaml:01568e5758a9dae8285749644852e6f22b03761d -http/cves/2022/CVE-2022-0679.yaml:e6bcf55f361c7a724c227da39e1d051435be5a7a -http/cves/2022/CVE-2022-0692.yaml:2fb2062a884d383639d71b7fdaa90816324c3f08 +http/cves/2022/CVE-2022-0653.yaml:72dfd6cae40cd471b5a161d2025bf48c164dd631 +http/cves/2022/CVE-2022-0656.yaml:4be10850d000a568482f4a91c88e71db6a4b290c +http/cves/2022/CVE-2022-0658.yaml:8542693cfc43d0f10543048135999aac00167b18 +http/cves/2022/CVE-2022-0660.yaml:0d3436790f3dfe9b1a90ed5f0a81548c611701ea +http/cves/2022/CVE-2022-0678.yaml:c4e60bfd4b0e328b188b321f923fdd06f1b3d936 +http/cves/2022/CVE-2022-0679.yaml:6e395009acd41589ba9f4801019bab8e21d5154b +http/cves/2022/CVE-2022-0692.yaml:1164734233930b207df5672ca6e482c1b7c1d0a0 http/cves/2022/CVE-2022-0693.yaml:f15bf8a8451241aecd8485fca1557c632e088cc2 -http/cves/2022/CVE-2022-0735.yaml:9272c739e042bfb8b8804ead0dc7712edf670387 -http/cves/2022/CVE-2022-0747.yaml:a7e139591867b26c5a1363796ea60ba71914a110 -http/cves/2022/CVE-2022-0760.yaml:820100179a54ab07ef826f86d8ce841492f3e355 -http/cves/2022/CVE-2022-0769.yaml:a4f6006b8394ab1e66b967a6927449161a0095ed -http/cves/2022/CVE-2022-0773.yaml:e0cf253f9a4fe0e02a1d4ff497caf73a07b4393d -http/cves/2022/CVE-2022-0776.yaml:d509776675f99a68627a1662daa344eb228129ac -http/cves/2022/CVE-2022-0781.yaml:b48a5e93d48cddac59799ae0ac91e51d547e0c04 -http/cves/2022/CVE-2022-0784.yaml:865db566b35db564cc3eab29555a811dc452c2c7 -http/cves/2022/CVE-2022-0785.yaml:8569e48d9f6a919505231a28a0b35eb0dd8d63ae -http/cves/2022/CVE-2022-0786.yaml:ef1eef04661d7f0e7d4798b95ca29955c79255c4 +http/cves/2022/CVE-2022-0735.yaml:f617c953bc5bcc95ca242e2929651165e18261d8 +http/cves/2022/CVE-2022-0747.yaml:7d10522c36c7989e5445100e5745e6f51beef3d4 +http/cves/2022/CVE-2022-0760.yaml:770f8f6108b651822a4e253fee2bc20bec944ce2 +http/cves/2022/CVE-2022-0769.yaml:55f23a7ae7858c008791adb309552d149b77ac8c +http/cves/2022/CVE-2022-0773.yaml:1e1c4f6317b18f4253fa92468220bed471553f21 +http/cves/2022/CVE-2022-0776.yaml:99a7c78b4ff1fe1a4a09c0cb3658a30f7c61b1b6 +http/cves/2022/CVE-2022-0781.yaml:bee1db9fcf728d4fe40278441d9c12421648408e +http/cves/2022/CVE-2022-0784.yaml:547f76203b7041bee2a1b92e2a2a4a60bec24c41 +http/cves/2022/CVE-2022-0785.yaml:f6ce1440e1d4473f878a81ec4bbabdefee531b59 +http/cves/2022/CVE-2022-0786.yaml:33b40ac058ddcbd2461c4fe7d962871ba0e979db http/cves/2022/CVE-2022-0787.yaml:381b553b7e97c8dcd0b10fea1bd4f3e6325b98b0 -http/cves/2022/CVE-2022-0788.yaml:582e9ec303f51a815d74e80cccf91616df5c1827 -http/cves/2022/CVE-2022-0814.yaml:0011d03049992c68f750decfdc41f48c048be3c7 -http/cves/2022/CVE-2022-0817.yaml:039b1dfebfd086d02134e429eca449926024ce90 +http/cves/2022/CVE-2022-0788.yaml:bda0fb5e8b26b57354ab6aba18d18b3b6ce3ce9a +http/cves/2022/CVE-2022-0814.yaml:75d2ab8c25692767fde543b45acc950f2cd865a5 +http/cves/2022/CVE-2022-0817.yaml:42731d138b09a7676ea1952473beb678f04824c2 http/cves/2022/CVE-2022-0824.yaml:686f14ab78c760c218687c8bb5e1d342925d573c http/cves/2022/CVE-2022-0826.yaml:600d404052aabf085d73f280ea6990fd25a289b3 -http/cves/2022/CVE-2022-0827.yaml:5a58c8b608d26e5170cfc37dfcbeb28915d51db5 -http/cves/2022/CVE-2022-0846.yaml:5c76d68cc824460b6cea8455b0596b0d4c09f47d +http/cves/2022/CVE-2022-0827.yaml:a6ff869deda47a257ec41a6d8f1399baef364bf2 +http/cves/2022/CVE-2022-0846.yaml:b172e4489fe9cb43f6eac94cf95627eac18465f4 http/cves/2022/CVE-2022-0864.yaml:4322380587e1a1a0d62047c91c028fd570d36b3a -http/cves/2022/CVE-2022-0867.yaml:03d55fb28a624aab99969ed2af26a1c12bdddded -http/cves/2022/CVE-2022-0869.yaml:8180d2cf62de2151654a7345adbde0b2887737a2 -http/cves/2022/CVE-2022-0870.yaml:d54919b88ea96e0f0147b49ea211c22959d320b0 -http/cves/2022/CVE-2022-0885.yaml:3c9d4cee872b12fa3ddb7f5ed904c23b2bb0138f -http/cves/2022/CVE-2022-0899.yaml:bf7a8e82c04849a4489cd660111a3d4b1f98556f +http/cves/2022/CVE-2022-0867.yaml:9c64bdc89533345414be3e96a36558558abd09e1 +http/cves/2022/CVE-2022-0869.yaml:ff5a50d70d1f6d5cddc1db3e577d60e307969587 +http/cves/2022/CVE-2022-0870.yaml:31ab8160cb95da756505747aa19a5a3162d6dea6 +http/cves/2022/CVE-2022-0885.yaml:7878a88d0ba2ee68c79ba2ab138b7c1965b15f2d +http/cves/2022/CVE-2022-0899.yaml:4b10371dd886b676ff92b013b2c615a422c0a908 http/cves/2022/CVE-2022-0928.yaml:33be920b902a29e1c3916b7e8b335fa9d6a55f25 -http/cves/2022/CVE-2022-0948.yaml:a1df6a91a734717bbeecc79fcc9b033ee3e0b767 -http/cves/2022/CVE-2022-0949.yaml:c17aac619cc793b6fc2c0198ab59476d1ff61a11 +http/cves/2022/CVE-2022-0948.yaml:52da4e4579452974a58f347058f02c96146f2e35 +http/cves/2022/CVE-2022-0949.yaml:6f89bbb12701b6a6455863c9c2660cb926c9e3b2 http/cves/2022/CVE-2022-0952.yaml:45934416754ba00bd26e45e01a26f64ef5c68e6f -http/cves/2022/CVE-2022-0954.yaml:cdefc235a2679c1aa25b9aaf8f7e918f5b3733a3 +http/cves/2022/CVE-2022-0954.yaml:518c2f8bb1dfcba77cc1c93e5ccbb1161132aee0 http/cves/2022/CVE-2022-0963.yaml:f6abad4c0507d955725ec87f0089f739374211e0 http/cves/2022/CVE-2022-0968.yaml:0019a7ba6e1372c50e172fdcd21eae61b51d577a -http/cves/2022/CVE-2022-1007.yaml:b635277b42a0b323843ea7d900eb603ca1812420 -http/cves/2022/CVE-2022-1013.yaml:a0f9d42df875f8d9dfc93ba7f2a840a33e98d71c -http/cves/2022/CVE-2022-1020.yaml:bd348bce52143afac0d4e5a53f9d351685b1c57c +http/cves/2022/CVE-2022-1007.yaml:d25f80d7777c3694e34f1ec60bb516db9884efea +http/cves/2022/CVE-2022-1013.yaml:82f969c52496a4707ae655974944e8b13e7ff81a +http/cves/2022/CVE-2022-1020.yaml:357e1d28e9c936bda102ced2b9e62a13ad49a20c http/cves/2022/CVE-2022-1040.yaml:5b842d12a84be295a1bf840f13ffb770ad99cc07 -http/cves/2022/CVE-2022-1054.yaml:d512163ad13f6a529d259412734da59c4f50d49b -http/cves/2022/CVE-2022-1057.yaml:a6eb285ee15e861045d0caf556c795d0dfdd0be1 -http/cves/2022/CVE-2022-1058.yaml:4c8906a74d62703aae1305d438da6bc2763a3000 +http/cves/2022/CVE-2022-1054.yaml:f062e3087d35a99718aeaf11d0612c03a7204986 +http/cves/2022/CVE-2022-1057.yaml:309a625336f6bc3950dc89cccee3365151f6f91c +http/cves/2022/CVE-2022-1058.yaml:8014143a23d3ea9612f0f61f8a02a971d6af8eba http/cves/2022/CVE-2022-1119.yaml:e22d9c7503f0997376946177cd20460200ee9f1a -http/cves/2022/CVE-2022-1162.yaml:25e78d3207c3cfc2db5875f650f6c8d583aaf731 -http/cves/2022/CVE-2022-1168.yaml:488a8bc1767abbc59bd1d65ac8ac6f97af480e8f -http/cves/2022/CVE-2022-1170.yaml:e6fa86bdd8f6236ef164276b992f93e00bc2e03e +http/cves/2022/CVE-2022-1162.yaml:6acff60afd29d7617af65d3087b8d1867143b04a +http/cves/2022/CVE-2022-1168.yaml:c0d6414794fddb9fe0ce0ef1f05a0e6489bfffc1 +http/cves/2022/CVE-2022-1170.yaml:1ebaaf64d56fcd3aa86e1c56268d688f502fd335 http/cves/2022/CVE-2022-1221.yaml:7c0c0f3ac317e95402835f01c9db2b89e81109e9 http/cves/2022/CVE-2022-1329.yaml:4175382b123dc1bb2394718097edac1b53868c16 http/cves/2022/CVE-2022-1386.yaml:321e7e3cb005e7492b554d14499aab6e47ed86a7 http/cves/2022/CVE-2022-1388.yaml:38617da5ace129816a22f029e69583b8d65fa33e http/cves/2022/CVE-2022-1390.yaml:7b92e5dc0ae72c18b9aa75b50ea0cb7460eb94eb -http/cves/2022/CVE-2022-1391.yaml:12ba1e78fec24716752a9a921384c8c0aa893b4d -http/cves/2022/CVE-2022-1392.yaml:acb2fc8ad0fb7a4689f28aad004fc0c7ba54f087 -http/cves/2022/CVE-2022-1398.yaml:537258636d2612f91598f416f16f8947c0920bcd +http/cves/2022/CVE-2022-1391.yaml:0a65c970d356b46ba789430cc7d6902876e429c5 +http/cves/2022/CVE-2022-1392.yaml:a12af01e55b56f2900bb11c3c6434639f3a8b034 +http/cves/2022/CVE-2022-1398.yaml:45e754c14a359abf102b55284118dce4a4c8b405 http/cves/2022/CVE-2022-1439.yaml:2a88dea8ce8ef60a3e3c2813c6bc0f84f5defd7e -http/cves/2022/CVE-2022-1442.yaml:fdfeb5be3a5d4726703b6b5f1fa0634c6d070ff2 -http/cves/2022/CVE-2022-1574.yaml:4c6ecd3aa621bc4639bad8e6ee7100e0b9e06614 +http/cves/2022/CVE-2022-1442.yaml:43a7a2667006588ea038b554e923cc305221a873 +http/cves/2022/CVE-2022-1574.yaml:c14887e9ba7156c7dca35a19506bffc95b4abcf3 http/cves/2022/CVE-2022-1595.yaml:bc4fc24222eacd4db3794f16ad3e64dae2df2f10 -http/cves/2022/CVE-2022-1597.yaml:1cda7bbe0a669874e50a5fa5723ca39dad083d24 -http/cves/2022/CVE-2022-1598.yaml:c4db064c01690f8b480dc26fbf419b54544c06b1 +http/cves/2022/CVE-2022-1597.yaml:db16599900080f39bc86e536d6f54f5c47dce13b +http/cves/2022/CVE-2022-1598.yaml:f0c0595db6008d79b1f272756d53a8b1b99a3b6f http/cves/2022/CVE-2022-1609.yaml:dc87f85d148b12b7a53cce475c80a1800806c01a http/cves/2022/CVE-2022-1713.yaml:668b8047e72be55a3b266dcdb6f745e46cbf9f26 -http/cves/2022/CVE-2022-1724.yaml:82e988dd7617b72dff57e54792775553da469aec -http/cves/2022/CVE-2022-1756.yaml:3de767e0a782873a06ed2dc605798f20c06920fe -http/cves/2022/CVE-2022-1768.yaml:11b05e4d5466b62a9b08beeaeac09c4c1b6bea7b -http/cves/2022/CVE-2022-1815.yaml:39197fbaa9ff0060f1dd86c1fceef9f501b50d71 +http/cves/2022/CVE-2022-1724.yaml:020285165fca467527329b800d79e31c73cd8491 +http/cves/2022/CVE-2022-1756.yaml:3ffe0af428bd6924049ce73fa2b5cfbd46d7cfa7 +http/cves/2022/CVE-2022-1768.yaml:0babd4b37d879fba52e1746e472fb6cd15ff7f72 +http/cves/2022/CVE-2022-1815.yaml:b9d0955b4bd83718b1ac331e490124e77efded55 http/cves/2022/CVE-2022-1883.yaml:e36bca39f962a084aa12dfd393f5a5d4ed393af3 http/cves/2022/CVE-2022-1903.yaml:8266a278ef78449ba9f37da5ddd0387d89089201 -http/cves/2022/CVE-2022-1904.yaml:8421aca3333624a936a2450837832ef0b00773b2 -http/cves/2022/CVE-2022-1906.yaml:51c4cca269f509e90c0b50fe0852a129fad8ae92 +http/cves/2022/CVE-2022-1904.yaml:ec4b1b22e373094e9c53c9bd8cda3bafbf169820 +http/cves/2022/CVE-2022-1906.yaml:c98f48ce0ec2475294434532fd49c9b9c201fb03 http/cves/2022/CVE-2022-1910.yaml:2aa74a96d620eceb18c408ccf3c989602b5701f1 -http/cves/2022/CVE-2022-1916.yaml:9ee88cb1a85af61e2b54a75e6d335144030d4655 +http/cves/2022/CVE-2022-1916.yaml:a8c7c65ff2f50cf7934810b2188150f282cf6d15 http/cves/2022/CVE-2022-1933.yaml:efd446f48b14b5bd5b2638ac9464095b9a0ccdc1 -http/cves/2022/CVE-2022-1937.yaml:69c45ad3345758edca9b9c902666ea4489b2a89c +http/cves/2022/CVE-2022-1937.yaml:9acdd815dd1da3bb9cb4f749457e58b6436056c6 http/cves/2022/CVE-2022-1946.yaml:594105798470a4bf9bf45ce7d7f37529a926890c -http/cves/2022/CVE-2022-1952.yaml:884a91f3a99cc1154ffb0687f45f7aa219082e00 -http/cves/2022/CVE-2022-2034.yaml:63487e3dec8ae7e46bf02938889dc2856fe6dc4c +http/cves/2022/CVE-2022-1952.yaml:89d66c08d4a66b8c4c1c6a4acf575bf306323c17 +http/cves/2022/CVE-2022-2034.yaml:ac47fb1ed9c843973ecfdbf9de63150b13329007 http/cves/2022/CVE-2022-21371.yaml:2615fbdf60875941ea788b6e7bd22ac4efd2f4cf http/cves/2022/CVE-2022-21500.yaml:7fa1fc1660bc12fe7a7eb028d6a5def73d716627 http/cves/2022/CVE-2022-21587.yaml:d6fc4537d6d7efbf50bb67ed27791918ac3e1871 http/cves/2022/CVE-2022-21661.yaml:27a64a0396360f99f2db4d2846e0b836b6e5afc9 -http/cves/2022/CVE-2022-21705.yaml:719c97db9b76470078347851df4c30dc5ba00d21 -http/cves/2022/CVE-2022-2174.yaml:de0d422b4b355be108407b1ef4d8491161c9dd6e +http/cves/2022/CVE-2022-21705.yaml:46a00260ae7ab5a0430d1aae2e2704638c1b10cf +http/cves/2022/CVE-2022-2174.yaml:f762e1ff4dc2e44167ad452b7927a7fa191738d3 http/cves/2022/CVE-2022-2185.yaml:94f29411692103d249667e648dc14f8a402ffa09 http/cves/2022/CVE-2022-2187.yaml:3ccc8ccb2c2fc65325e167d81ce2e4d9cc18ac39 http/cves/2022/CVE-2022-2219.yaml:60e3c53863f296ef75b283a6ca3998603e17ecea -http/cves/2022/CVE-2022-22242.yaml:0464d481a9a17a2d2ca8021b33222e10530a54f0 -http/cves/2022/CVE-2022-22536.yaml:7b093e7c0107578703e8e64f58bf15ae2d5189dd -http/cves/2022/CVE-2022-22733.yaml:b15c0d6748026f88e4fbbaf93ea93c03a1978547 -http/cves/2022/CVE-2022-22897.yaml:ed1cf6d95adbe19a52452f5c92d93b5428ecbdfe +http/cves/2022/CVE-2022-22242.yaml:2f4c1c66c8cb7290ddecffca35b17ad29764dbc7 +http/cves/2022/CVE-2022-22536.yaml:8a42ec513ba963c034cc0761778b3e35aad7aca4 +http/cves/2022/CVE-2022-22733.yaml:ed8ed7299f7b0b56e6d628e71ff937560dc3f5a1 +http/cves/2022/CVE-2022-22897.yaml:ec4b61132e5f0d6ae1f6b5bf2b914d571ec71cf2 http/cves/2022/CVE-2022-2290.yaml:1ffd766095c19c490e47fe0b84a82963fab4bb63 http/cves/2022/CVE-2022-22947.yaml:d340b56dfc93e975db196afe5e83752a0848f70f http/cves/2022/CVE-2022-22954.yaml:e13dadeaeef068e8408955cfbc9df6dbc664d6aa http/cves/2022/CVE-2022-22963.yaml:72b59a2f42e337619721c469690a9d9e2269a76f http/cves/2022/CVE-2022-22965.yaml:2daa357a18f737cbc4349daf55fbdd4e3d4ca16d -http/cves/2022/CVE-2022-22972.yaml:d6c6c942e7bd79909cfba87565f6fa6542580be8 -http/cves/2022/CVE-2022-23102.yaml:a7add0802eaddfc9f8b1b959369a952c8891ef8f -http/cves/2022/CVE-2022-23131.yaml:bd36fc11109ae0bb395ac9d329c5ac346a961846 -http/cves/2022/CVE-2022-23134.yaml:01ce3b992f9d06aa26d6c50a40d8249e52541e15 -http/cves/2022/CVE-2022-2314.yaml:d1459f98f0a97918f5ca918154664d701efc80ff -http/cves/2022/CVE-2022-23178.yaml:9032113eb10b4d74b8cc9844c476f55d13ccd0c4 +http/cves/2022/CVE-2022-22972.yaml:b3c4136b4a87ffe7e5751cc961c40a8490519d85 +http/cves/2022/CVE-2022-23102.yaml:0af3a8394cd214ab0411230827bebd7f9020f4fa +http/cves/2022/CVE-2022-23131.yaml:0faf7d42cdedbbea9671df891d7fd345a22dea21 +http/cves/2022/CVE-2022-23134.yaml:1271f0b5a2fe70011702d795761572c7ee75294c +http/cves/2022/CVE-2022-2314.yaml:039a1dd0772608f199bc30506f2235b6db0321b4 +http/cves/2022/CVE-2022-23178.yaml:522c4f8590129c90b06a520b8216858de8c496c5 http/cves/2022/CVE-2022-23347.yaml:f4f50b4d9589e41ea7de0b9fab6a2bdd8cbef76c -http/cves/2022/CVE-2022-23348.yaml:77f213f32db7daae82ee386f39fe776a2882d5d9 +http/cves/2022/CVE-2022-23348.yaml:ee2ac9359a9c4942c40c156f148ba18475866824 http/cves/2022/CVE-2022-23544.yaml:b952b96397f7dfcfe6c20609cbe3b245d29a3d8d -http/cves/2022/CVE-2022-2373.yaml:e99f9ac25c5224b347a68d99fe3ba6ddc0740399 +http/cves/2022/CVE-2022-2373.yaml:3e2d739ec391670939a9d162246a6f6534c71707 http/cves/2022/CVE-2022-2376.yaml:60fe1b6a94360440f5692f1767a1706aa968d6d8 -http/cves/2022/CVE-2022-23779.yaml:6071ebdba87644098c7e8badd1c081fbdccde5a3 -http/cves/2022/CVE-2022-2379.yaml:6968e8258cc0cf9105070ba96ef89b97903162b9 +http/cves/2022/CVE-2022-23779.yaml:76ade255f0f7a30d863308a22ce0a5ade77f963b +http/cves/2022/CVE-2022-2379.yaml:61637bd23b820eeb383043139eb7b0747d8dc0ee http/cves/2022/CVE-2022-23808.yaml:340141d4775ce463c3ba7ff11195aec522745c42 -http/cves/2022/CVE-2022-2383.yaml:e1a9e9e9c3bbe32f28694e33fd56fb146c036403 -http/cves/2022/CVE-2022-23854.yaml:1b632f489c7cb3224a8c5b40d9e36c2b3b2e4418 +http/cves/2022/CVE-2022-2383.yaml:6ee355a8168f1b15df824dee1ffffb939dbb5cf2 +http/cves/2022/CVE-2022-23854.yaml:1fbdcc3aa0abea3f071b13ccec7016782f9a37f4 http/cves/2022/CVE-2022-23881.yaml:7c347d114eaa850b7f07267432336eb5b327d042 http/cves/2022/CVE-2022-23898.yaml:25447e6bebb48bd497c14730336677c976c04eff http/cves/2022/CVE-2022-23944.yaml:a13cabb108a548f0eb1abd63818045f6f25521c0 http/cves/2022/CVE-2022-24112.yaml:d88895dcccdd4a0205c6bbdec964a3f8c8905c31 http/cves/2022/CVE-2022-24124.yaml:85391f13d5bc304ee96371c64e66171e7deb0852 -http/cves/2022/CVE-2022-24129.yaml:e63d6e570f505c9ce93b888daa0c05cd9de96ec2 -http/cves/2022/CVE-2022-2414.yaml:73f9114c854004164e90bd32cfe68f2357057a26 -http/cves/2022/CVE-2022-24181.yaml:3e409fce9db362bbc178a763322421cae3cdf0d3 -http/cves/2022/CVE-2022-24223.yaml:17bc1d92145f98a8c6694fccb2b2be318df582f0 +http/cves/2022/CVE-2022-24129.yaml:b002f95d04374f1c30f5e3e40a1bf69a4394df7c +http/cves/2022/CVE-2022-2414.yaml:18b296b89ec926eaea45e335ba64ef43437c15dd +http/cves/2022/CVE-2022-24181.yaml:008d3e54ee26ead1b8aa913e063b5350f52c584b +http/cves/2022/CVE-2022-24223.yaml:c8cd076fd3d66d0e82f4e2b61791523dfeda7512 http/cves/2022/CVE-2022-24260.yaml:a88fa61d3e20a7a4802fbf9dd792f7bc8c958c85 -http/cves/2022/CVE-2022-24264.yaml:10687df67ab6627556810d5eb3c2bbc831d02593 -http/cves/2022/CVE-2022-24265.yaml:46bd885fb22fc36e8c0364dd9035c6be3793ebdf +http/cves/2022/CVE-2022-24264.yaml:8ffec19f3c15c5f8ad32c53f4b79f74fc5f38017 +http/cves/2022/CVE-2022-24265.yaml:b4f8a19753fb5ba8dc9d36c6c0a2848e730d6111 http/cves/2022/CVE-2022-24266.yaml:0ec2e95b8d9f6135cd6dbd277bef141d0dd73811 http/cves/2022/CVE-2022-24288.yaml:886e90e7a313808da0eb81e9b8e48c52b3083b50 -http/cves/2022/CVE-2022-24384.yaml:62eb5e7d99718e1657d4119b37249b1281e6a938 +http/cves/2022/CVE-2022-24384.yaml:2e49fbd900cfbd4e7150a3c4e606e7940e28babb http/cves/2022/CVE-2022-2462.yaml:0df440f8031f57ae35d9a2e05b4631969aee3ef8 -http/cves/2022/CVE-2022-2467.yaml:a41ff15b87032fa3f9081f1c4f4d166045050fc8 -http/cves/2022/CVE-2022-24681.yaml:e3e6d180bfa1438119d3ea189212443fd4eb4192 -http/cves/2022/CVE-2022-24716.yaml:8a837cc2dd6a1e7dc400de89a191fc1dbf2533e1 -http/cves/2022/CVE-2022-24816.yaml:752efff30cb3103fe873e3635724b8d434887c71 +http/cves/2022/CVE-2022-2467.yaml:9c57a5a043771b3ff81b8af4c098a10e1cdf9cd2 +http/cves/2022/CVE-2022-24681.yaml:6dafd4b690da2b952aa40ea27de762690ab7976e +http/cves/2022/CVE-2022-24716.yaml:0f96f4d6c52b50fe4fc68b83a729d6c94097303a +http/cves/2022/CVE-2022-24816.yaml:9b55f9f9aa12803d7d8a00a93d795c80d054ac61 http/cves/2022/CVE-2022-24856.yaml:3cb57e37aaf6bd6726a35bb624c13d15bf924d5b http/cves/2022/CVE-2022-2486.yaml:3cc359ec6b95f6804330b40ffb4e2be2d80542c4 http/cves/2022/CVE-2022-2487.yaml:98a4953634be719376abf25d3e06085041d95ba4 -http/cves/2022/CVE-2022-2488.yaml:1140a0d40f5961072358b889acd26080cc615110 -http/cves/2022/CVE-2022-24899.yaml:f41f64af188595b72a5a26a577b38cea2cbcb70f -http/cves/2022/CVE-2022-24900.yaml:0aa071009869c2e9a8afbbfc868b1319dc3e5cf8 +http/cves/2022/CVE-2022-2488.yaml:dead3cbc90fbe2598e817ee747b421a4faaf7365 +http/cves/2022/CVE-2022-24899.yaml:e2699771ff140ef96cd51bab442b3d7a87e27af3 +http/cves/2022/CVE-2022-24900.yaml:2085cc896182ba6e1737a99ee84e57135cf00ab6 http/cves/2022/CVE-2022-24990.yaml:fa878b248fe5af789ec55694af9a95b48e27a2fa http/cves/2022/CVE-2022-25082.yaml:7dfcb885c1a9f9439f49553dcce3210d03047f30 -http/cves/2022/CVE-2022-25125.yaml:3d1a57395a62cdcebe29a9501cad0c0dee51b127 -http/cves/2022/CVE-2022-25148.yaml:b38b0b79918cc25f9a5d0ca921db35b060643b82 +http/cves/2022/CVE-2022-25125.yaml:2954acca6429b53b57b81c6566b7328613069120 +http/cves/2022/CVE-2022-25148.yaml:140de05e1929a196cdf4bc3ebdf43a5031a5eaf7 http/cves/2022/CVE-2022-25149.yaml:a20d1fbb14a8c8e8ef5b3c17a9409a6deb7053f4 http/cves/2022/CVE-2022-25216.yaml:c4fd23cfabb1d5d301c65a43a8e5acfc7c0cf7ff -http/cves/2022/CVE-2022-25323.yaml:60981faf4400472a50344e0256cb005240aa5944 +http/cves/2022/CVE-2022-25323.yaml:88e13f8fef0ee651e4eaea6509acb29e4e39f638 http/cves/2022/CVE-2022-2535.yaml:35215895e560e9fb1df684e1f8daf8ac781e6229 -http/cves/2022/CVE-2022-25356.yaml:67782d70f431558f783a0ada44c22d6372f01fb1 +http/cves/2022/CVE-2022-25356.yaml:0eb907eb5188598c13deedc98489b7fe73c0ed79 http/cves/2022/CVE-2022-25369.yaml:122baf7f94b5d6155221c1dee0a86308f7ce4df9 http/cves/2022/CVE-2022-2544.yaml:717cae8d627f3977492a625a5c21337062e1d4db http/cves/2022/CVE-2022-2546.yaml:f5f5b87eb951abe89c7119de4d71657563b4b2be -http/cves/2022/CVE-2022-25481.yaml:11e08d8c0d443edcb2bba5366ca1d72b04fd73e9 +http/cves/2022/CVE-2022-25481.yaml:1289f31bc4491fb03842fda6c086d1552f1578d4 http/cves/2022/CVE-2022-25485.yaml:42dfa499615a304012e7d7de7539297b39d36621 -http/cves/2022/CVE-2022-25486.yaml:c7456cad43814c454fe9ae47c1bfd9b8e9005848 -http/cves/2022/CVE-2022-25487.yaml:6b3ec85412e983efe1478f8d4786f9e89e257f04 -http/cves/2022/CVE-2022-25488.yaml:0ea76c73823a0db8b07a6c290b19c730633431bb -http/cves/2022/CVE-2022-25489.yaml:c23bcf4fb6c18f005a7bd7e801740c7867d8fb40 -http/cves/2022/CVE-2022-25497.yaml:e80a1aef99e2ec6abe9eec7f9eba6fbc4619d273 +http/cves/2022/CVE-2022-25486.yaml:9ba1b62d20b08609efa9246bd405ae428ecc1422 +http/cves/2022/CVE-2022-25487.yaml:5c2b8c894b1b67fc343a0aeed626eb8fa142f4a2 +http/cves/2022/CVE-2022-25488.yaml:3aa1da33af2037bce8262fc0483872da6a9bba96 +http/cves/2022/CVE-2022-25489.yaml:ff7af72a9d4927ef689292523fc681a8e28a7cde +http/cves/2022/CVE-2022-25497.yaml:8a57a3437f9567f6baa42865d3733322cb9ead5c http/cves/2022/CVE-2022-2551.yaml:c1b4f1242fdff52554fb74f9a9ce5ca7b9204673 http/cves/2022/CVE-2022-25568.yaml:03092d2d3a6e76abaffb19d9b503d7f0535d9f90 -http/cves/2022/CVE-2022-2599.yaml:6ae0f5ff05cccc9339fd14b15bd26bbbb8208aee +http/cves/2022/CVE-2022-2599.yaml:e6a1b798c4cc1483bbb8c2f3c9876cd162189594 http/cves/2022/CVE-2022-26134.yaml:6c074ea2931880391204caf22ae68420df89e6d9 http/cves/2022/CVE-2022-26138.yaml:3d00d240416890261419d1dd5181925e0fe1a9db http/cves/2022/CVE-2022-26148.yaml:ce5fda0bbee8a191f4b2d793e8de0129fef43342 -http/cves/2022/CVE-2022-26159.yaml:7fd28f05df062a965709e4617302caf7415d5ea9 +http/cves/2022/CVE-2022-26159.yaml:4e357257e49b9bb7a9655fbda1206f0bbf0be8f7 http/cves/2022/CVE-2022-26233.yaml:6a8fd59463f46b43794def0a45bf97e58267fd3e -http/cves/2022/CVE-2022-26263.yaml:fc95b930f366e2da3034c0b2f608f48e77fa9f70 -http/cves/2022/CVE-2022-2627.yaml:7fe52e9a1635c776f2536ad9796878df2ed55ba9 -http/cves/2022/CVE-2022-2633.yaml:0f0b281f51bab4a62dc1139aff51b5abf55ea5cc +http/cves/2022/CVE-2022-26263.yaml:2d0ff4fab95d32cee3f462cffea7f3a20c8df473 +http/cves/2022/CVE-2022-2627.yaml:830be2f5cd56b9d2623b7e71293e1cb0e64d8faf +http/cves/2022/CVE-2022-2633.yaml:265176a8437d43bc4d2cf163af1bdbf5862568f6 http/cves/2022/CVE-2022-26352.yaml:8068310b14037fbd81e27cd488b67ca46b8387c4 -http/cves/2022/CVE-2022-26564.yaml:d419b447240dc85cecde021491d8f1f2a43d5f87 +http/cves/2022/CVE-2022-26564.yaml:9adaf7968b28875f727c37378f1dfc7877a5606b http/cves/2022/CVE-2022-26833.yaml:26590f3eda2be98190abe5a0a015d122f67f6242 -http/cves/2022/CVE-2022-26960.yaml:8b88af9104bcd40b915dfa01cb24c08c94587324 -http/cves/2022/CVE-2022-2733.yaml:727885e2ca0352f694db3612a245cd6d0ddf6420 -http/cves/2022/CVE-2022-2756.yaml:9093dc713e937091471849ff6d4fdcd6c4ba7780 -http/cves/2022/CVE-2022-27593.yaml:4c230b453c02f8c34dff9381b4627e53b3293420 -http/cves/2022/CVE-2022-27849.yaml:d886a6738813b361b4a22008255fd8b1f81870e7 -http/cves/2022/CVE-2022-27926.yaml:4cdd9e3b15b3fda532d51d98d7937bcf3d77a9b8 -http/cves/2022/CVE-2022-27927.yaml:9d13f5ec5facf8c9f3328671506a92bab351091b -http/cves/2022/CVE-2022-27984.yaml:bca9ecda87bb2da9d0f5d2b213f55fd62eca9514 -http/cves/2022/CVE-2022-27985.yaml:9c6bba9800706b4c424ade6743bf35914d63cb94 -http/cves/2022/CVE-2022-28022.yaml:87731112c8ba16bece79e621cba185698bc01d94 +http/cves/2022/CVE-2022-26960.yaml:b8180fccb7259cece7b514324735b733ef24b51d +http/cves/2022/CVE-2022-2733.yaml:5c9daee5a35f02f5bb29a018bbba81629823f724 +http/cves/2022/CVE-2022-2756.yaml:998387be58f6a01cea88f71fa6ff53dcd1918f80 +http/cves/2022/CVE-2022-27593.yaml:75656416d8b007a1b9fb7fd0e8d3a3e2a1d59510 +http/cves/2022/CVE-2022-27849.yaml:824a53a5574883acc98bcbdf4def4da1bbdfeed3 +http/cves/2022/CVE-2022-27926.yaml:96cba62c83ce39df1c467ce096bef68ad1e80cd8 +http/cves/2022/CVE-2022-27927.yaml:cdfee362d8c3b3c22399a501d392cdc86491730e +http/cves/2022/CVE-2022-27984.yaml:81957ad112ece8f3eb072ddaa6aac73ef12eaf6e +http/cves/2022/CVE-2022-27985.yaml:b9f537611048e91fdf7d00fb590e688a126fe791 +http/cves/2022/CVE-2022-28022.yaml:40e481fd0b5a7a66233bdb5e866b73897512a534 http/cves/2022/CVE-2022-28023.yaml:66df7ed24b40bfa8943aab7e8842148d3a444ed7 http/cves/2022/CVE-2022-28032.yaml:196f477373d244ad7fef75f1a24b2237c614afd8 http/cves/2022/CVE-2022-28079.yaml:6995731e5703e6940abb19571051bf4520fb3c65 http/cves/2022/CVE-2022-28080.yaml:bfe3175eb75caa1cf2a046010689b1a15ee5cfb0 -http/cves/2022/CVE-2022-28117.yaml:b1ba9977361dcbfb97d5c055d06bab09b0257f1b +http/cves/2022/CVE-2022-28117.yaml:8082f8ccb85a68e756ec8deb7a3ad245f542428d http/cves/2022/CVE-2022-28219.yaml:9484c92c7179312ea9aa0b6f3d8a3e5f5b31ca3a -http/cves/2022/CVE-2022-28290.yaml:ccf515d80b185e564c9213ba176d2a60e6c01f1f +http/cves/2022/CVE-2022-28290.yaml:804dd05fcee21667c3e6f4122a080ba48664e01e http/cves/2022/CVE-2022-28363.yaml:75eefd84c17fa9a42823ef23a5c88e9eb57d0e18 -http/cves/2022/CVE-2022-28365.yaml:d01708d7c54da04939912f8d070777f54e3e70c8 +http/cves/2022/CVE-2022-28365.yaml:7b11d57432afd9398dcff809b08a97f1bd07986d http/cves/2022/CVE-2022-2863.yaml:3c55a686d48f4a6efdf91379417697a96f0ca529 -http/cves/2022/CVE-2022-28923.yaml:02afd588a7c09c4c092ea9c6e6e3a8611113e97a -http/cves/2022/CVE-2022-28955.yaml:953bebd69c9da6e99d337c58c7414fd87aa99165 -http/cves/2022/CVE-2022-29004.yaml:4c0b2d37543636993ae3e64ce9ec8450fe355c79 +http/cves/2022/CVE-2022-28923.yaml:ddb7f6b6cc25b1018b1797dc89d340d5211b4d59 +http/cves/2022/CVE-2022-28955.yaml:2ca1ae7d18d8586a58348037404ddeaab4041803 +http/cves/2022/CVE-2022-29004.yaml:45898190da56a7767aae21095194c764b86ee061 http/cves/2022/CVE-2022-29005.yaml:e4fbe260a2425595d592c663a1437bc1314aab97 http/cves/2022/CVE-2022-29006.yaml:17f106abd16c0cacd3818e2f48bfa83c3275aa94 http/cves/2022/CVE-2022-29007.yaml:4b22aa871357ca71f3734b2e92242a09cc1f0df9 -http/cves/2022/CVE-2022-29009.yaml:21ca0e16062699d10809f3ab969930f075e2694d +http/cves/2022/CVE-2022-29009.yaml:eb748ed5a062df3e5ba51386a6792bc38d0e1090 http/cves/2022/CVE-2022-29014.yaml:48c5a1b31a7e6d67df43833911b5a4eeeb2c74ee http/cves/2022/CVE-2022-29078.yaml:90ce880fcf6282de4eecc1970356d699cb895e0d -http/cves/2022/CVE-2022-29153.yaml:155d05a085d6dff8c7c44e7a204c8beac4fb9607 -http/cves/2022/CVE-2022-29272.yaml:a5b6647affd458be1afb4d8314a181d9772aac71 +http/cves/2022/CVE-2022-29153.yaml:8d46b005ddd081f65d2575f2e6ad855e66ab899b +http/cves/2022/CVE-2022-29272.yaml:ee7462b4aaa080b95be60ec1d9e60773bcd2da98 http/cves/2022/CVE-2022-29298.yaml:05382409e3012f2035c1ded23b0d0b9cdbc2e102 http/cves/2022/CVE-2022-29299.yaml:76530b9dc484a6ed8eda21fe82bda162db2add24 http/cves/2022/CVE-2022-29301.yaml:c8739c3d8be5329a646842fcc7cceef9de2b74e6 -http/cves/2022/CVE-2022-29303.yaml:52b0c085267d68cb456aa804a222d548a48890ba -http/cves/2022/CVE-2022-29349.yaml:8d48a2c309186dd382dd28fbf4e798dd58e3dfa7 -http/cves/2022/CVE-2022-29383.yaml:15f7bc709a382a66904f7b3ff0554e28f91a3a5a +http/cves/2022/CVE-2022-29303.yaml:430025574756fc7e67b6488e9a6675038535cac0 +http/cves/2022/CVE-2022-29349.yaml:0d3b5f64780dbc0a923b081fecc77af135b4be51 +http/cves/2022/CVE-2022-29383.yaml:7bc85c36a0a4299da4ba3499561bf62e24305a3b http/cves/2022/CVE-2022-29455.yaml:161c1f4ac128f978bd3a54fa1132bcdfb780f291 http/cves/2022/CVE-2022-29464.yaml:2a08f5ff05061d45999d63acaa5c17b8ba43b381 -http/cves/2022/CVE-2022-29548.yaml:a7e2f4fce295d18d281fff35c2842cd422c5fee3 -http/cves/2022/CVE-2022-29775.yaml:417fa696c39d9f87678fede94714aed9f96eed51 -http/cves/2022/CVE-2022-30073.yaml:6e88fc9c3e11fd6a5a6040025862f47a96d9d293 -http/cves/2022/CVE-2022-30489.yaml:b67424bfe55e8b20f399e5ad344bd2335495ff79 -http/cves/2022/CVE-2022-30512.yaml:316397b8c52c2be4e2c2f5fba85cd6db148290e9 -http/cves/2022/CVE-2022-30513.yaml:18c9963e1c031f3bce07d9a6a833cde3a1c49769 -http/cves/2022/CVE-2022-30514.yaml:702e0c8f70eeab9ca7861f8862a790fd8146170e +http/cves/2022/CVE-2022-29548.yaml:4d5b389c2b4305160a3b20bd499e1f59d6f33085 +http/cves/2022/CVE-2022-29775.yaml:81feb61c9d005f58bf1d9e7a75c95479f72c49e1 +http/cves/2022/CVE-2022-30073.yaml:5fe8186f0baff582ac83403177f71ec375237a2c +http/cves/2022/CVE-2022-30489.yaml:a7b2339d1b89b5aa646e497b9b61f7b96c9d3476 +http/cves/2022/CVE-2022-30512.yaml:49583c7cde789b0e2758afe248bb6e6a8d0c4f68 +http/cves/2022/CVE-2022-30513.yaml:e1ffc0a2c1a46cc9d76265b0e52a25ec67d0d652 +http/cves/2022/CVE-2022-30514.yaml:1cd6ea9ef19f9517924866111fc24dc8cedcb866 http/cves/2022/CVE-2022-30525.yaml:732b0cc25d6b61d95b21c7f42a6793a6d64d06ab -http/cves/2022/CVE-2022-3062.yaml:1d59c1e5b7d8d4acddaae50120beddb504354e73 -http/cves/2022/CVE-2022-30776.yaml:4bbcb4cd8f86128d7b385f3fe370a16d282b851b -http/cves/2022/CVE-2022-30777.yaml:72472b066df038309401c1bcdeb67bc3205876f5 +http/cves/2022/CVE-2022-3062.yaml:90eb8733bef7ea09e6f9cbd55758ad7798339efb +http/cves/2022/CVE-2022-30776.yaml:fb3fa9646ffef46f0114f444ecdf06500be1690a +http/cves/2022/CVE-2022-30777.yaml:b95af3e664ed9e4978ff8f7ad609a6659d7278cc http/cves/2022/CVE-2022-31126.yaml:68d09c1dfdfbcc2c4f466f1e9ebc0afa2409f4da -http/cves/2022/CVE-2022-31268.yaml:92d127aba322fbed8aacee93328432bac41a66c8 -http/cves/2022/CVE-2022-31269.yaml:887b33ec2cd8dd2be2b27da88a8d685b12a4f143 +http/cves/2022/CVE-2022-31268.yaml:b2e65a9adc74b62d87c557578e290157aa838900 +http/cves/2022/CVE-2022-31269.yaml:7432f0af2c0fc30b45971250232f31afef94c0e7 http/cves/2022/CVE-2022-31299.yaml:c9681dd5c1bfdb9558bdad08e429f33a4815a27b http/cves/2022/CVE-2022-31373.yaml:e4878816a11dac7f1674e54d5872f2b3cea3bebf -http/cves/2022/CVE-2022-3142.yaml:b54359ab60f0f9c5140fdcbeedcfecd1c9040fd7 +http/cves/2022/CVE-2022-3142.yaml:7bb4d1550dfe9ad5e2e0408cc91d618da36bea0e http/cves/2022/CVE-2022-31474.yaml:fa9c6515df790dd2e6187b456d62ca809a3e05c2 -http/cves/2022/CVE-2022-31499.yaml:11f9fb3197548e06c7936c703a7a652235d40a3d +http/cves/2022/CVE-2022-31499.yaml:3b07d90b8f9674b04d847b4017e2a41caf815e84 http/cves/2022/CVE-2022-31656.yaml:737778c295d7ee937f99e5f6ace4b777740edc5c -http/cves/2022/CVE-2022-31798.yaml:b28f3d64d47e37f208a0b4ce4b871c1886936805 -http/cves/2022/CVE-2022-31814.yaml:aae74515c118b5831037d0620f23077af53efb97 +http/cves/2022/CVE-2022-31798.yaml:5f539b3e05811e1470fe0f0fb9f4d7dfc30af232 +http/cves/2022/CVE-2022-31814.yaml:2ac7923cf764435b042c4403464f942269921a9e http/cves/2022/CVE-2022-31845.yaml:2ed1efdcf2c63dcc29da767e2ed9fa8deca826a7 -http/cves/2022/CVE-2022-31846.yaml:79f90562142c43abe4b034c30da68cd986231f53 +http/cves/2022/CVE-2022-31846.yaml:221af9c1389faa25732c78dcaf403c78995fe237 http/cves/2022/CVE-2022-31847.yaml:fd7bcaa15681a5e13cc9bd4f043f661e24562430 -http/cves/2022/CVE-2022-31854.yaml:ae273f25d60cc11fda6971e1c0cf6ed395464dc0 +http/cves/2022/CVE-2022-31854.yaml:b4f26994de508f49d8d703c674bab5633f465542 http/cves/2022/CVE-2022-31879.yaml:2c19638b6350d0cd77a031a8fb3dd92247e0e3c3 -http/cves/2022/CVE-2022-31974.yaml:d3f2ab8c0ad7102529a9346ed21233aeaada4597 -http/cves/2022/CVE-2022-31975.yaml:e421230b4787588cd787f65a4310c1967cfd2632 +http/cves/2022/CVE-2022-31974.yaml:488d44920127ca80a2a78a70ab9a72950cef72ab +http/cves/2022/CVE-2022-31975.yaml:eccc2b335c9141d669f7d03b3f16e2b583319b70 http/cves/2022/CVE-2022-31976.yaml:d18e651ccee124c6c9cc4ff00696b2b34917815a -http/cves/2022/CVE-2022-31977.yaml:83c3875599a1c892f24dfd96116a0bd4f0e80ce9 +http/cves/2022/CVE-2022-31977.yaml:fd7d5941424ecdb18feaf567c06d6ff81f2fd1ae http/cves/2022/CVE-2022-31978.yaml:2bf51bd7dd5e6ca340ee129d76fa377e547cd29d http/cves/2022/CVE-2022-31980.yaml:7a2f5add99c0224ee015981227d39c6b0793226f -http/cves/2022/CVE-2022-31981.yaml:fee31d25e2aa8818076c5c0977ae14f2a44b22d5 -http/cves/2022/CVE-2022-31982.yaml:2033642c49975e5cba2242d3818fda6edcaa3505 -http/cves/2022/CVE-2022-31983.yaml:3eb43591837d24f4626f6a9aaa8073143c1bf956 -http/cves/2022/CVE-2022-31984.yaml:ad4ae5ff730886f34431a373260fb431a6104c34 -http/cves/2022/CVE-2022-32007.yaml:7d04fc6b3b1c38d2261181a3d2ab9d12ca93b0e5 -http/cves/2022/CVE-2022-32015.yaml:ebbfc59797600f93c6882e4499e811beac485221 -http/cves/2022/CVE-2022-32018.yaml:e00a690e5508d0e3cb0a23f780055abfe57cd1f2 +http/cves/2022/CVE-2022-31981.yaml:e7bc0dff1080ce76fcd41377731fc14c10bca3fb +http/cves/2022/CVE-2022-31982.yaml:f6b8e7aa8af4bd0843c158793fda2d0023092745 +http/cves/2022/CVE-2022-31983.yaml:b873379b19c7f10371225646ca5879702b4e6e7e +http/cves/2022/CVE-2022-31984.yaml:18a8d875fee0026ffdf96a8327e0568f16cd0652 +http/cves/2022/CVE-2022-32007.yaml:f14ccf3f05ef7b7c5470107554a109e80d8f2e35 +http/cves/2022/CVE-2022-32015.yaml:3bcb7e306489cfaa221b629cd1668d3c4af74680 +http/cves/2022/CVE-2022-32018.yaml:0225dab8443094fbf89c4b4a6524edf68b8120d3 http/cves/2022/CVE-2022-32022.yaml:8807867575031aa693a96642330ea58fc268548f -http/cves/2022/CVE-2022-32024.yaml:24c4958a9c70e4aec97b9c9b3b2b5ad193d4a7b0 +http/cves/2022/CVE-2022-32024.yaml:d025ec45c0df2830ad4bf7c7211f22d7971ad2e6 http/cves/2022/CVE-2022-32025.yaml:5fcd4be7ff9b4529b961e6541f7660b637cc12d3 http/cves/2022/CVE-2022-32026.yaml:a3dbfbc182c79526a811d7477a4d95dcfc603714 -http/cves/2022/CVE-2022-32028.yaml:92a7a96d80dcfd29e98321f0fc6b9906aa4531ef +http/cves/2022/CVE-2022-32028.yaml:0e31333a0a256822b7c8fa70cd0a8998ef1febe4 http/cves/2022/CVE-2022-32094.yaml:1fc001931b9b00ea72dcadf27ec59bcbad36aff8 -http/cves/2022/CVE-2022-32195.yaml:55ab37ed5eb731b01c54069a6267aba49174a7fd +http/cves/2022/CVE-2022-32195.yaml:eadef93aa1a596caea375c9e1d93b0fd9f31f78c http/cves/2022/CVE-2022-32409.yaml:64ad26d543e9317cafe7e3aa0ab688d7f8a3994c -http/cves/2022/CVE-2022-3242.yaml:8b083ad87c14c42d0b57f4244547eaee1c7d5a59 +http/cves/2022/CVE-2022-3242.yaml:6395ff71af50fc02b7aca4a7907dde2dcef5da21 http/cves/2022/CVE-2022-32429.yaml:cce7fc9409e46645f83197993520d3c8fcc5900c -http/cves/2022/CVE-2022-32444.yaml:61e9c5a2dc81eb6550a19490de1790ae8632b6a0 +http/cves/2022/CVE-2022-32444.yaml:bc7a295957774fe919f4a75e0a9085a9e87b33d1 http/cves/2022/CVE-2022-32770.yaml:932040e18ac9b45d0a565f86b64d84367cf8d5aa -http/cves/2022/CVE-2022-32771.yaml:540df0ba7e2e3ceaba1f2a26dd91ce6b9161edc6 -http/cves/2022/CVE-2022-32772.yaml:1dc70415c06092ecf98b23db71bd0778783f743f -http/cves/2022/CVE-2022-33119.yaml:b7757f4d34d154b76346757129a9443406872297 -http/cves/2022/CVE-2022-33174.yaml:3dd720d84d52ae42ebf2a5f5a73fa36c72d3a345 -http/cves/2022/CVE-2022-33891.yaml:2c71ba19f8008f3515eb5bb315806219a619cf53 -http/cves/2022/CVE-2022-33901.yaml:5c61d527b6b3ebdf994316bc7c68a4309770ed3b +http/cves/2022/CVE-2022-32771.yaml:054c65517603b12a64cb39e72f2cd5582dbd263e +http/cves/2022/CVE-2022-32772.yaml:e1f98ebba8add9e66fb2eb7650396eb169b583ca +http/cves/2022/CVE-2022-33119.yaml:3faacb7ef1f6b81f4a3d071aecea325bdbcc2008 +http/cves/2022/CVE-2022-33174.yaml:4600d393b7ff9055a8cc2e4e3c2b5789a02534e6 +http/cves/2022/CVE-2022-33891.yaml:04cf35557c072073582f0d6a330ee91900bd2ea5 +http/cves/2022/CVE-2022-33901.yaml:5b97da20d12b390aaea9b04a50193947c6b31ab5 http/cves/2022/CVE-2022-33965.yaml:be214dcbf486df2486282f07d48e50771019b252 -http/cves/2022/CVE-2022-34045.yaml:821d78d97d25d9e1aad8adb5059c2928635a6991 -http/cves/2022/CVE-2022-34046.yaml:2c0b187b2cfb7a885363f8a57825ee0721c0445e -http/cves/2022/CVE-2022-34047.yaml:1559e12287b2e4d59460ce4319feae376e34ffb0 -http/cves/2022/CVE-2022-34048.yaml:89df4f22fb23d7df084bcba6091b5c9e696cda1c -http/cves/2022/CVE-2022-34049.yaml:94d8be3e8511abe06ad03ac0280199b96d35f3ab -http/cves/2022/CVE-2022-34093.yaml:f30968b9c8fc6f0ea2795ac40bde0c4fc74fbbfb -http/cves/2022/CVE-2022-34094.yaml:3fb194658188007e9c86f6851cb1b7f9eb1cb88e +http/cves/2022/CVE-2022-34045.yaml:6ef53d6036323bc3f73de1c1ebb49b6376187791 +http/cves/2022/CVE-2022-34046.yaml:2dea14218da11d921a0de29d4a8e1fd1f32d320d +http/cves/2022/CVE-2022-34047.yaml:04bbc6245cf9a3ccd473d97725df6d1209c73897 +http/cves/2022/CVE-2022-34048.yaml:34954cb3559ecbc4b4760afdcd10cf3a07785966 +http/cves/2022/CVE-2022-34049.yaml:0f0aaf1c82842d37aa0200694a74a74156014f91 +http/cves/2022/CVE-2022-34093.yaml:a235ab6b6e40c45ab516b6a65a53a2c912159a28 +http/cves/2022/CVE-2022-34094.yaml:867c0612fdf01162633ef7ae315b20c033fa57e0 http/cves/2022/CVE-2022-34121.yaml:b3e4dbea1ea50855cfe87c6791a62715a3058285 -http/cves/2022/CVE-2022-34328.yaml:68f2f95d9acd6eacc82b3bfdf7568a9041651050 +http/cves/2022/CVE-2022-34328.yaml:37f47539688f72545856cd221fbb7ad40244fc07 http/cves/2022/CVE-2022-34576.yaml:b261eee9ec92c938f67c46b19982127c5fb326c6 -http/cves/2022/CVE-2022-34590.yaml:98c77baf4816854e01b855ccc8151f16c9ad1d85 +http/cves/2022/CVE-2022-34590.yaml:01c7acc8a34a2a030eb2da0b2aaa297a368769a1 http/cves/2022/CVE-2022-34753.yaml:526f3e3f0654f5c935c092dff968dbe61e24ac00 http/cves/2022/CVE-2022-3484.yaml:c9236a1df036be0bf869456ada48b20ca0649a95 http/cves/2022/CVE-2022-3506.yaml:689bcb711261a5a13eaa7d276aee39595227a50d http/cves/2022/CVE-2022-35151.yaml:ea19cfd4a3cd6d10a4f27e2d237a300e919dc740 -http/cves/2022/CVE-2022-35405.yaml:84115578f83d9fbebec15379f44ca5d6f3fae625 +http/cves/2022/CVE-2022-35405.yaml:05f629d28327aef8ed7af091a4d517c62f7405e9 http/cves/2022/CVE-2022-35413.yaml:fce9ffd0e62d07ea4d8793c7f627f6a6ac77a78d -http/cves/2022/CVE-2022-35416.yaml:fdef8c1b341011f15ee7d9c3cf5e3521325b43d0 +http/cves/2022/CVE-2022-35416.yaml:fc0d5f228d05579cc923b0713901bdd5c16dd29e http/cves/2022/CVE-2022-35493.yaml:194a9122ef06617db654a0fca2780436234ec262 -http/cves/2022/CVE-2022-35653.yaml:8d7bfd60a8143e2822573c003606626cc55f9097 +http/cves/2022/CVE-2022-35653.yaml:576b4a95eee7b459ebaa6b0252efdfaf90bea558 http/cves/2022/CVE-2022-3578.yaml:c200a7e49e84093ff788c4299638258af1f4fe66 -http/cves/2022/CVE-2022-35914.yaml:180ba41c4f23534d9aff144d4681eb891b987916 -http/cves/2022/CVE-2022-36446.yaml:a66f235bec1d3eca737091d17609b2d24e1e6512 +http/cves/2022/CVE-2022-35914.yaml:0764841dfaf748c1c503e7a0c37bfe0b5c429f77 +http/cves/2022/CVE-2022-36446.yaml:359fb3f3025710c23e606b3d7ede973650086e6d http/cves/2022/CVE-2022-36537.yaml:ef180235bdd9af33b91b9d94fe2a19c6fe8bdead http/cves/2022/CVE-2022-36553.yaml:a55f7d6dc10c590f6a170df5d6dbc4d53bc33c3f -http/cves/2022/CVE-2022-36642.yaml:b0e909fd5bd4f82e40775e6768a8b388a2b6f4e3 -http/cves/2022/CVE-2022-36804.yaml:320e27431d8a55078b0a416955fbad45f662c470 +http/cves/2022/CVE-2022-36642.yaml:184a0fc762dc2f7d849caa9932b8f60fbf6b5bcc +http/cves/2022/CVE-2022-36804.yaml:9d8f094dc6c2a5e0903450eb5d86c3519bfbb2ae http/cves/2022/CVE-2022-36883.yaml:d48e1b93c1cdae09549690b4f1b38717a4f8eeee http/cves/2022/CVE-2022-37042.yaml:4fe136d0ba43afefe3d2a14695aa8bded1257b8d -http/cves/2022/CVE-2022-37153.yaml:2fc592c60f41ea921804d29b1be67ee87801ab16 -http/cves/2022/CVE-2022-37190.yaml:d52d253e15afe08eb9e5d83aeac1be8e44b017c3 +http/cves/2022/CVE-2022-37153.yaml:798e86886cc7f8d3a0fb918f49b0aa5f89bfe9f6 +http/cves/2022/CVE-2022-37190.yaml:ac2e243b51ce2e90935195140b597283675c6c57 http/cves/2022/CVE-2022-37191.yaml:ec7f5169291fab59b73e8b73475d4a273a38fc3c -http/cves/2022/CVE-2022-37299.yaml:7838cb5363943ed3c535d0387d4f9c9f9c353e48 -http/cves/2022/CVE-2022-3768.yaml:a86e881b0294fc932b15188694a2d875dbebc12c +http/cves/2022/CVE-2022-37299.yaml:3f2242688324ae354f13ec950acebb7fe0187ee5 +http/cves/2022/CVE-2022-3768.yaml:db514be5a480df5b1926e67829e2a981323394b8 http/cves/2022/CVE-2022-3800.yaml:faaad9124bf756264cf3d6a952a8c8bbf57a5f87 http/cves/2022/CVE-2022-38295.yaml:30313a567d452260be53928eefcd79b37da6a8d0 http/cves/2022/CVE-2022-38296.yaml:6a5ec2878abc3ab8697db0a340b9383a33b7ca3e http/cves/2022/CVE-2022-38463.yaml:06bd11fd4611a3d55f753113a3bc4fcc3e445f6f -http/cves/2022/CVE-2022-38467.yaml:0059e8cb3f76fac3d65ce5cc569a4d1da5bb811d -http/cves/2022/CVE-2022-38553.yaml:a5090f579f67579c4516c95542c17b3905d32923 -http/cves/2022/CVE-2022-38637.yaml:5662d6ece9f328418f210dd78a0f61721a448610 -http/cves/2022/CVE-2022-38794.yaml:1e97e192e645ea8a66b0d27c259064729c92613f -http/cves/2022/CVE-2022-38817.yaml:f750b74412a4aa2a18d73116d2e2cbff485bec6c -http/cves/2022/CVE-2022-38870.yaml:47ded55770a5c7d58578b6b544584ce51b1bda2b -http/cves/2022/CVE-2022-39048.yaml:621b4d736b54cbbef742b8f3e4634518aca724f1 -http/cves/2022/CVE-2022-3908.yaml:7e68eb0f1838a024af0a444b7a9e4e08bf2fa17a -http/cves/2022/CVE-2022-39195.yaml:6ed08333789faffc459cf0afb3dc77d8cd87c2e8 -http/cves/2022/CVE-2022-3933.yaml:8642b91a8c8dc81b8ea5e29da1be2bfb59cf330b -http/cves/2022/CVE-2022-3934.yaml:70e4351a2c32bde0b05e9c9a4619140b9c15a416 +http/cves/2022/CVE-2022-38467.yaml:5d9c0ec5ee8fd897443dfcdf27dcecebe83b0987 +http/cves/2022/CVE-2022-38553.yaml:1a609d1d798ab4a295ffbdb6b811d51402f99471 +http/cves/2022/CVE-2022-38637.yaml:7baffee52597574c6692c8612d5e53e56a87b218 +http/cves/2022/CVE-2022-38794.yaml:c0f907e1dad4b4f00dab0393a7d2867b5c2d0703 +http/cves/2022/CVE-2022-38817.yaml:79c30cccfe4bf4ab8c975c89441d54a20d6f058a +http/cves/2022/CVE-2022-38870.yaml:d6bbfd25d6479cbe056ad1df7a47c435bb642b7a +http/cves/2022/CVE-2022-39048.yaml:e0eaa87c8192f65320fb5bb7ef3ed24465cf89c7 +http/cves/2022/CVE-2022-3908.yaml:0fc720d39fdfe588cd2675ac56b52b25cfe186de +http/cves/2022/CVE-2022-39195.yaml:4cc916b6f1000d7b261202a65dc4d8e6d2086c6d +http/cves/2022/CVE-2022-3933.yaml:c04e17b900c3b78af6a9238f366b40f98184afd5 +http/cves/2022/CVE-2022-3934.yaml:c450e73191dcce8c67f20f0c39964300e4f1468d http/cves/2022/CVE-2022-3980.yaml:c71b1870963fa476505c6c81cda1273078fad546 -http/cves/2022/CVE-2022-3982.yaml:06001cded76d912df37de69be4045ca142ecb7bc -http/cves/2022/CVE-2022-39952.yaml:226932770dabc82bd90cb1e7978fe1f4c8c51e7c +http/cves/2022/CVE-2022-3982.yaml:e7f2a09dbe032190858331740899eaaa66110fb4 +http/cves/2022/CVE-2022-39952.yaml:6129b759425037540084a5be1c8020ceb9ca0553 http/cves/2022/CVE-2022-39960.yaml:bd6771584293e5f25d5cb23dad577fcf93a15641 -http/cves/2022/CVE-2022-39986.yaml:450f647060d29e037a1b3cf0712b3e385e64fc86 +http/cves/2022/CVE-2022-39986.yaml:dffd1cc9f4602b6477c0f957f13b1cfaa03a1a1c http/cves/2022/CVE-2022-40022.yaml:382a413805d246131b1246e0fffa698068b90016 -http/cves/2022/CVE-2022-40032.yaml:9584cacdbf06a6468f2d970d03538721fc4fdcea -http/cves/2022/CVE-2022-40047.yaml:6d6e3ae4b09523fe83848190149a930f9eaebc6f +http/cves/2022/CVE-2022-40032.yaml:ac36670911780ae2a0762bbe0ae73d5a083023a1 +http/cves/2022/CVE-2022-40047.yaml:904344a08d15ec8c9331bed4fe312fc92a110675 http/cves/2022/CVE-2022-40083.yaml:365b01b708c0dac5be912cf2d2c1ad0d70e17b7a http/cves/2022/CVE-2022-40127.yaml:fa2ea89f083a6fa0761d6a48636afabbbf8522f4 -http/cves/2022/CVE-2022-40359.yaml:e648a3b7a9ee7ff9009d58b419eac85470b825ef +http/cves/2022/CVE-2022-40359.yaml:487826ed338784ab5c36bd137899d2cd28c65ba1 http/cves/2022/CVE-2022-4049.yaml:e308ad82867dc9d91da67b5fecdc28ae8499470d -http/cves/2022/CVE-2022-4050.yaml:8bb0f58ba873cb68a56c5303e30ed5379fee755d +http/cves/2022/CVE-2022-4050.yaml:916a77df37d3eeea514373f8c407b9827328f980 http/cves/2022/CVE-2022-4057.yaml:3103ca0d819429b01eb2fc983d7d6649bb4fdc3a http/cves/2022/CVE-2022-4059.yaml:80cab79a21205dd83cbbc9c364fa7e28085f759d -http/cves/2022/CVE-2022-4060.yaml:6d26071895a5b46d8f1dc6636c68942b0a2aeb43 -http/cves/2022/CVE-2022-4063.yaml:ae89560db2adc36a2059619685a9db3d48e55935 -http/cves/2022/CVE-2022-40684.yaml:23b563ae6fb79612bfe4305dcf698eacee95d0a9 -http/cves/2022/CVE-2022-40734.yaml:f7c375643ee97af4e901664ff56a3a230390d6f7 +http/cves/2022/CVE-2022-4060.yaml:b075793c0bb6eeb09746263d91c5bf0b58170296 +http/cves/2022/CVE-2022-4063.yaml:2afb9f4c3958a5821dd7d7492eaaea7b6ed4a120 +http/cves/2022/CVE-2022-40684.yaml:a1f01a11a54ffcd055d854b1c172ba8be8c3303c +http/cves/2022/CVE-2022-40734.yaml:eb3d0c5dfcef0918ed726493f0790cce4ef62a3b http/cves/2022/CVE-2022-40843.yaml:eb8a4ce623ab1e08a663cbea7f0863542a1998df -http/cves/2022/CVE-2022-40879.yaml:33a9f88e8e3244269f1c7bd64db6b7155af19f1d +http/cves/2022/CVE-2022-40879.yaml:bf24ab6c3a5f1fae7d3b94b452c9edac2f0ee186 http/cves/2022/CVE-2022-40881.yaml:284ae24c77a41a1db61f2521ea195324e30a1e81 http/cves/2022/CVE-2022-4117.yaml:98f5ab7fa5ea973af6cf06d43468759a6827d695 -http/cves/2022/CVE-2022-4140.yaml:2f06dc6ab82c5d87d50a4c16d792d9110b01c5b5 -http/cves/2022/CVE-2022-41441.yaml:7447c16d1e5ffd58f75341db2bc7ca0904e47bdd -http/cves/2022/CVE-2022-41473.yaml:b504b75bb188d7a4e542f9ca3beee15b59aeb7a8 +http/cves/2022/CVE-2022-4140.yaml:8072771f1671593a4f5ba80456b2624a85584a7e +http/cves/2022/CVE-2022-41441.yaml:b8f043d09dd2c2384a177114445be71484d40b3f +http/cves/2022/CVE-2022-41473.yaml:4b7c504f045bb1793854e58669fcb02a97ca4fdf http/cves/2022/CVE-2022-41840.yaml:641e5820783d4407ac16efd35413cd4144988f9d -http/cves/2022/CVE-2022-42094.yaml:95ccbb6ebee39efc3662b24d9f3f81d614e26ffe -http/cves/2022/CVE-2022-42095.yaml:67479c5608a134adbf5c26b781901bc99ec81401 -http/cves/2022/CVE-2022-42096.yaml:0d495dfdfdc2aa1487f433399d8d14364a8bea42 +http/cves/2022/CVE-2022-42094.yaml:0200c4c45e1710930b3820874785671a625d1bdc +http/cves/2022/CVE-2022-42095.yaml:489d6a1e64fdf63ff3bb46754b71bc7961f84db8 +http/cves/2022/CVE-2022-42096.yaml:bb8e22c487da35d4bd08b258951ade64166f7856 http/cves/2022/CVE-2022-42233.yaml:3f67edf09c323a3d3116dfa70cf98c09233839fa http/cves/2022/CVE-2022-4260.yaml:5f9f6a639c8ac8b0e86ced0169b256044224c53d -http/cves/2022/CVE-2022-42746.yaml:7661b148da6cced0a1328a3506b593b90dbd078b -http/cves/2022/CVE-2022-42747.yaml:80652a68d3b89cb082de304aef9b991133806243 -http/cves/2022/CVE-2022-42748.yaml:3ba49e3e5b2cbd4270f763d9ab2b7f33a963c0dd +http/cves/2022/CVE-2022-42746.yaml:62d01d3ff6eaeb745ec88690491e25e8203252aa +http/cves/2022/CVE-2022-42747.yaml:cfdfd42a81a620098036cff015829de0ab447d58 +http/cves/2022/CVE-2022-42748.yaml:aceba4bd450aabbde6324e17e421fd061d507d89 http/cves/2022/CVE-2022-42749.yaml:b13539a2e5305b7af770964bfad69171d7d786ad -http/cves/2022/CVE-2022-4295.yaml:9f69b32b18efe688545ca5ed09b564847ebff239 -http/cves/2022/CVE-2022-4301.yaml:5b1526e73a076706a0e97c42c39183eebe2c5b7c -http/cves/2022/CVE-2022-43014.yaml:eff1857dd5712c8e2d4f31004e62ad625ef38964 +http/cves/2022/CVE-2022-4295.yaml:c2f71e0d009b7e2759ca06e24830115ebcf6cd00 +http/cves/2022/CVE-2022-4301.yaml:ff3115fa82af94ca95a193162c701108a3c6b425 +http/cves/2022/CVE-2022-43014.yaml:c816e06d1386d7a27519ccd3cf3a7153358091e3 http/cves/2022/CVE-2022-43015.yaml:be3ade90d03bffd66efcd5ca1b74bac3d1b18812 -http/cves/2022/CVE-2022-43016.yaml:57a248080539cf7b14680ba48dfe64e65a519dd3 -http/cves/2022/CVE-2022-43017.yaml:b4c6d68e57aa694f4e992f4fa2c4dbefa8a36687 -http/cves/2022/CVE-2022-43018.yaml:65987b6bacb95f51ede99472e87b92fda703e8a6 -http/cves/2022/CVE-2022-4305.yaml:7a9c5ad5b40cdcdd34d561da54061a28dda9c049 -http/cves/2022/CVE-2022-4306.yaml:1d0ae927cb1fd6b275049377065f82cb3b62da25 -http/cves/2022/CVE-2022-43140.yaml:8533f749bd4c55dfe592f3b7298f8116d46ee65d -http/cves/2022/CVE-2022-43164.yaml:6334414f3ddb4bb753d48d12e696f0d904f67187 -http/cves/2022/CVE-2022-43165.yaml:41452a96398231582ea62a68ca43d3986779c8b0 -http/cves/2022/CVE-2022-43166.yaml:80b474d78848ec974e9c6dabb2cce875bbe9cae2 -http/cves/2022/CVE-2022-43167.yaml:2aeb96a0a3a0356568980ba0d927bd3e5390a3e9 +http/cves/2022/CVE-2022-43016.yaml:71107d89de4f33f3427747d46839c1a73e21f8cb +http/cves/2022/CVE-2022-43017.yaml:f3a2eb8fb233f11343bb598885f39b6d29d55220 +http/cves/2022/CVE-2022-43018.yaml:cd20fac7eb00fe776e5919b206d6cb6f05fab68f +http/cves/2022/CVE-2022-4305.yaml:3ba1a082b61ddaeb31f81bce8c609c220f97fca5 +http/cves/2022/CVE-2022-4306.yaml:3790d57233cc9b37430b92a26f6e474e8c94df38 +http/cves/2022/CVE-2022-43140.yaml:61c4e915374ab105c1bf70d78d65ef35b20b3917 +http/cves/2022/CVE-2022-43164.yaml:4abeac4338dc20560d20a65f744efc43b4dcf86e +http/cves/2022/CVE-2022-43165.yaml:10f62e3198abb8a281587ba5952f73c30936d784 +http/cves/2022/CVE-2022-43166.yaml:8064f82ddcf8566fd6acd988df841318a5877a38 +http/cves/2022/CVE-2022-43167.yaml:f0dc65286b210debc9cc07adb534de34e6e5b391 http/cves/2022/CVE-2022-43169.yaml:7a6ef00fed0216cb6dce3458a24ef1a219a7f445 http/cves/2022/CVE-2022-43170.yaml:78487655513161ef9d44c1d3ccb3c1473d6fb999 http/cves/2022/CVE-2022-43185.yaml:9864488ae6c04f3928ae6cfd5f19895f6bd7c92c -http/cves/2022/CVE-2022-4320.yaml:f52f5dafdbcc946037d5941f65a33f9490c2c7c9 +http/cves/2022/CVE-2022-4320.yaml:8f05a42e0bb33b4dad49dadcb4d5244e600a7429 http/cves/2022/CVE-2022-4321.yaml:db034674b9710c92d8bf04e788b3680d9752931c http/cves/2022/CVE-2022-4325.yaml:a3f6d125c857569df181b4da146420fdb8325822 http/cves/2022/CVE-2022-4328.yaml:570c5536824a5375b3d2698c69d3347c57fdb3ed -http/cves/2022/CVE-2022-43769.yaml:6ad436a4e0a723978b365a71f722bd38820e66e2 +http/cves/2022/CVE-2022-43769.yaml:c52aab40ca1085450c0a615d597c25ba58856c23 http/cves/2022/CVE-2022-44290.yaml:c87969aebe32e3c41df082a90c2e993b730cc5ae -http/cves/2022/CVE-2022-44291.yaml:7d5b0645824d27cd19d8388a2a45fc13c5998589 +http/cves/2022/CVE-2022-44291.yaml:06203e3aec1b5fecb48be84bcb05d3e21254ffdf http/cves/2022/CVE-2022-4447.yaml:8fbce61be5897000c78aeeee3dcea8c544b4c94c http/cves/2022/CVE-2022-44877.yaml:7a56b131069bb361ae3f80990f13206307f91a6b -http/cves/2022/CVE-2022-44944.yaml:d95591009bd0394ad80260ed09d1a62ac25da687 +http/cves/2022/CVE-2022-44944.yaml:5c4a773fd05f9b6a29e296ca94d19f0d513d356e http/cves/2022/CVE-2022-44946.yaml:8a289c9e28d25ac0c0dbd5c16de8aa74b5e19f9d -http/cves/2022/CVE-2022-44947.yaml:85be9f020954c1bd38e7368fb9ab2c83f525095c -http/cves/2022/CVE-2022-44948.yaml:92055b5c18a953b1c4e8451a7894a7112486c626 -http/cves/2022/CVE-2022-44949.yaml:ab8499fabd942ffe3ab86519a4d07e425c09535d -http/cves/2022/CVE-2022-44950.yaml:43bb23e4077282ee9e4bee06bf743e1a0551862a +http/cves/2022/CVE-2022-44947.yaml:fbfb64686c977dbb4c73c2e0fc51f38c7d3e4532 +http/cves/2022/CVE-2022-44948.yaml:5a7968ffce39f6969efcd240b845e3724059694d +http/cves/2022/CVE-2022-44949.yaml:6a4b60e5892c998b156c31edcc695819296e9c4d +http/cves/2022/CVE-2022-44950.yaml:dd9f85ae05a595fdad8d792a3dab18255fb76ae0 http/cves/2022/CVE-2022-44951.yaml:6cb7b6127cb69b1e6e0382d2e1271ea094b0415e -http/cves/2022/CVE-2022-44952.yaml:5182ba99cb8b30ca70ebbb0d9e7572d2cce2d9e5 -http/cves/2022/CVE-2022-44957.yaml:661c13401d5048f4fc31ac68bf285f516d031510 +http/cves/2022/CVE-2022-44952.yaml:9d734a03fbd853ecdd0bd15692f417e1a00386b9 +http/cves/2022/CVE-2022-44957.yaml:67425170368ef2ab8bbff744a2cfc08392102aaf http/cves/2022/CVE-2022-45037.yaml:ec825acc6c072e87b9af0b732d70cdc705b728cf -http/cves/2022/CVE-2022-45038.yaml:c84226a9a071701ced8ca078f34d9018c1208c5d +http/cves/2022/CVE-2022-45038.yaml:73e8816949bce1b198cc5062792ee0dd8e67a2bd http/cves/2022/CVE-2022-45354.yaml:74b3e516dafb8498fc37736a5c504dec4325bca5 http/cves/2022/CVE-2022-45362.yaml:8b38771a9d554ed3e0813063295cc0113aaf3beb http/cves/2022/CVE-2022-45365.yaml:bc6d4127eb5583316f2ee30607f2c57f6a348daa -http/cves/2022/CVE-2022-45805.yaml:f23e2b97b51846218dd58da2161e1754586965aa -http/cves/2022/CVE-2022-45835.yaml:fa98aa8fd3f05555bca0e11c8af44392dda527c1 -http/cves/2022/CVE-2022-45917.yaml:6fc54ed1f8ed8b03480533a289a03aa91af37b10 -http/cves/2022/CVE-2022-45933.yaml:cda1f790fa9dcf99e8e09fb5da0f07921675b8b8 -http/cves/2022/CVE-2022-46020.yaml:4f8420f0fdaeadbd8af47db14fc3f8acacc7a451 -http/cves/2022/CVE-2022-46071.yaml:33c338e604966b006f7257ed14cfc5462c1de0fb +http/cves/2022/CVE-2022-45805.yaml:d35d5ff33b7f15d4e207a73e81ab8b7458e807ea +http/cves/2022/CVE-2022-45835.yaml:06ff568885b58d60a69cc3a811ce687f618709ca +http/cves/2022/CVE-2022-45917.yaml:0690e0e096efdfa13800da66e81ad0ddc373d521 +http/cves/2022/CVE-2022-45933.yaml:497152d5355f09d0f78f998c6b99e01a9573b5b8 +http/cves/2022/CVE-2022-46020.yaml:87584bc5691b32618127528a4bf8bad034cf0491 +http/cves/2022/CVE-2022-46071.yaml:49b4c76187916184fbbd38a4563f57b9f8797bf1 http/cves/2022/CVE-2022-46073.yaml:2c4db4b42b0447f3286fd5e4b07e6d8f339d74fc http/cves/2022/CVE-2022-46169.yaml:23eb06ab92df1696c6721b3394a988c4e415a5bf -http/cves/2022/CVE-2022-46381.yaml:7ea7de8f5a6a0e86df9cbfbdfac4c96e2b709e47 -http/cves/2022/CVE-2022-46443.yaml:320018ac3dd333fa34495e6668115d02fba9c831 -http/cves/2022/CVE-2022-46463.yaml:b8718519880ea8662e434362a7ebb811952945c4 -http/cves/2022/CVE-2022-46888.yaml:793c1fa863e913275b29b70dd6db4f6342bb0ed6 -http/cves/2022/CVE-2022-46934.yaml:ca13f76159bdb9a13d97d4459ab76098fef441ea -http/cves/2022/CVE-2022-47002.yaml:b388150dd0cb08ed11b8871998e15dda0f8e237a +http/cves/2022/CVE-2022-46381.yaml:d2b6366d254a4dee36e0c1d042b3ce3675d14b5a +http/cves/2022/CVE-2022-46443.yaml:9a9ffdd5880ca129566b4544a50ef51d7f539c34 +http/cves/2022/CVE-2022-46463.yaml:f79db8d0367aebc677a628c89b59b7c3e194d231 +http/cves/2022/CVE-2022-46888.yaml:eab00571b65bfe6a2c5a89468dc0423172a35d81 +http/cves/2022/CVE-2022-46934.yaml:faa0970867939daacf4487bfa1410258edfacc23 +http/cves/2022/CVE-2022-47002.yaml:6d1540bcdd8d3f67e237af3206e495e686c77e9e http/cves/2022/CVE-2022-47003.yaml:51450f8a2761212089dc8a5fe41e0d1e3618e53a http/cves/2022/CVE-2022-47075.yaml:38a9d8e23d9e978c9ba3f12e8d0d4ae682a33d6b -http/cves/2022/CVE-2022-47615.yaml:ccc91cd16323e34e83b28d960c1658ffc67a19e0 +http/cves/2022/CVE-2022-47615.yaml:ae2403f323875a4c4181e05a2e5451ee5d0600d3 http/cves/2022/CVE-2022-47945.yaml:86835e2fe86222458008b5612ec4b0bf143a7baa http/cves/2022/CVE-2022-47966.yaml:26412c0674cb4a0c0483273154f7bddf54ac8502 http/cves/2022/CVE-2022-47986.yaml:5293897e475fe16ee6340ff1a855b1acb7096731 -http/cves/2022/CVE-2022-48012.yaml:f2c07e92991efc7293691c3b34db59f2e1f47789 -http/cves/2022/CVE-2022-48165.yaml:2b94f8d9ca5e441207970c3fd6fb8ffb7b496799 +http/cves/2022/CVE-2022-48012.yaml:54e1a67d7ed7d5887a0cb4e2f8cad15d62b0829b +http/cves/2022/CVE-2022-48165.yaml:69e09ae08eb6c557a708ab3112ddb164cb0af282 http/cves/2022/CVE-2022-48197.yaml:a123bf49ac116938e006cc25397600e1f7d1ca38 http/cves/2022/CVE-2022-4897.yaml:19c55fb6cdfb6c221e40f674b2497e8c62977509 http/cves/2023/CVE-2023-0099.yaml:a99f1538163834a219025101b76738f4895d722f -http/cves/2023/CVE-2023-0126.yaml:b70c04d3ad3cdebe8b72da6af1543a3118bae0cf -http/cves/2023/CVE-2023-0236.yaml:51d83117958e57d57a7f68092c8ce799dff5cf3d -http/cves/2023/CVE-2023-0261.yaml:e572e082d84cd283e8bbb8e6264ffb20eca26d08 +http/cves/2023/CVE-2023-0126.yaml:d2ba92244b050782fc4e682bde200fcc377eb73d +http/cves/2023/CVE-2023-0236.yaml:0e2479e7a33c2b0530dc934b016c288a2f157465 +http/cves/2023/CVE-2023-0261.yaml:9864fbb9fcf5d9410097e0d018f12e1cd2cb0ce0 http/cves/2023/CVE-2023-0297.yaml:32f813f125a535e3c5328fb827fc453f4e006d9b -http/cves/2023/CVE-2023-0334.yaml:27acaca291d93b7c7c8d34b19627fb2adad22673 -http/cves/2023/CVE-2023-0448.yaml:4773dcb4437c5d19403d8ec5e32ad6309f7fff37 -http/cves/2023/CVE-2023-0514.yaml:265ef61ceaea4ad1b8768343ef1237e8c5791585 +http/cves/2023/CVE-2023-0334.yaml:1138294d67047fdb4a62a027c03b6469ab62dc61 +http/cves/2023/CVE-2023-0448.yaml:5df7a29ea17db94b6cfca67be9a94eff5d94096f +http/cves/2023/CVE-2023-0514.yaml:a3176bea6102d8a3b5c292f34c50c8972aff2ead http/cves/2023/CVE-2023-0527.yaml:96ee486454cb015e23ad56849a2b808a71e41455 -http/cves/2023/CVE-2023-0552.yaml:1ed838d68f84d4f5f1a90e1e3d8cdce95dc896a9 -http/cves/2023/CVE-2023-0562.yaml:96095d97251bb4d7ab019a823861881d8970765c +http/cves/2023/CVE-2023-0552.yaml:8753723c54480f2376d20e2ab6de7aae473984b2 +http/cves/2023/CVE-2023-0562.yaml:f35a1ffcd5c552d7a5def2ce051be76694d3dc89 http/cves/2023/CVE-2023-0563.yaml:01f24c5ae7400649e04bedf943ee21ddacba576f -http/cves/2023/CVE-2023-0600.yaml:1c5a03c4fb40a086e19e9b90155941bbbba1891f +http/cves/2023/CVE-2023-0600.yaml:7b3425d8873c259015edd2899f116e9f1c90b6c4 http/cves/2023/CVE-2023-0602.yaml:4f624b39650a52b45def9c320b39556453af0916 -http/cves/2023/CVE-2023-0630.yaml:50a2031ca84b9007c370230b7599811b9f8a8f8a -http/cves/2023/CVE-2023-0669.yaml:83d7ae015882b5d3f076a0a31f52c838d2887f18 +http/cves/2023/CVE-2023-0630.yaml:61a2887379c6349fa32bd9b9f460721f65a31656 +http/cves/2023/CVE-2023-0669.yaml:25c4ad6af0fa8eb108db21b3c355ab51924eefe7 http/cves/2023/CVE-2023-0777.yaml:e051c94c0e5f68e31d40905a811e873a98075f82 http/cves/2023/CVE-2023-0900.yaml:46a1c4c38b0304e5b2bdc7b62d1908df5f27804c -http/cves/2023/CVE-2023-0942.yaml:66a98a6101b8ada63ac4cad324f53eb25a174d6a -http/cves/2023/CVE-2023-0947.yaml:79556df7b48b3c575cca43c54e23e3aa61f2ebfd +http/cves/2023/CVE-2023-0942.yaml:4dab69efe417450d2be99cf392cd76bbe3d6a612 +http/cves/2023/CVE-2023-0947.yaml:78b9fa7c594b8fcfcf9f10bd04a0cdff95c01b11 http/cves/2023/CVE-2023-0948.yaml:32ef440fa1f58203519e27b9bcc0bebf959e57fa -http/cves/2023/CVE-2023-0968.yaml:dcef0add658b2393d6d9876a6833b085f5243b50 +http/cves/2023/CVE-2023-0968.yaml:7992b3380d73577af75bdeafe0bc66eaba5b1e62 http/cves/2023/CVE-2023-1020.yaml:8a798d11c2de2edb4c0275b72d0239cb88f19a2f -http/cves/2023/CVE-2023-1080.yaml:55a89158cd5a301f8e4201d145ff9f70b51e63f3 -http/cves/2023/CVE-2023-1177.yaml:d7b2ff8125b1251bc7fcf2124330457ac103a425 -http/cves/2023/CVE-2023-1263.yaml:51e5d2f611483bb2ec21f1cd6d86381c16918e50 -http/cves/2023/CVE-2023-1362.yaml:283947051d0517a2006bc77c9e42027014d16a4b -http/cves/2023/CVE-2023-1408.yaml:30427be49e77cb67beb8899348b8855eebe300f3 +http/cves/2023/CVE-2023-1080.yaml:2a7709371c7b8161b1cc75a28ade1aa52bdc4d96 +http/cves/2023/CVE-2023-1177.yaml:c7cc4cbdec0fe4340aa7bdf90d2c1e4d1a81d2fa +http/cves/2023/CVE-2023-1263.yaml:e462bdff6cd72c8bb86ef90bad69d2f6c7168b1e +http/cves/2023/CVE-2023-1362.yaml:283c469fe5c7b5185284e755febd565664493d57 +http/cves/2023/CVE-2023-1408.yaml:cff78fe5777c2d4d5123145a01a6783730089cae http/cves/2023/CVE-2023-1434.yaml:8d9ea6102d27ff45261b9622412d4a1ab23b96b1 -http/cves/2023/CVE-2023-1454.yaml:3e698744a0441bc467ca523be59cd798ad29a1e8 +http/cves/2023/CVE-2023-1454.yaml:da5d5dac67acf7741216f32de1bc782e6d919ee1 http/cves/2023/CVE-2023-1496.yaml:b676f4e75317295c881773370f1028fd8f757d75 -http/cves/2023/CVE-2023-1546.yaml:fdedd7a096f74f0aa204591be5e936f32d6e9fee +http/cves/2023/CVE-2023-1546.yaml:a7733047d0a7c0844c822f93736fa0f6d397c239 http/cves/2023/CVE-2023-1671.yaml:a3b154cd25aa82ff7fad113855741763f4ff927d http/cves/2023/CVE-2023-1698.yaml:7ae15a498a958d74c23db433cb4c683155a62494 http/cves/2023/CVE-2023-1719.yaml:8fa76202e895ed26eb4298c1cf4bda4086e35711 http/cves/2023/CVE-2023-1730.yaml:d27c1a81d8e03c2ada3e856cdfe760aa312bbc8d -http/cves/2023/CVE-2023-1780.yaml:36aa78f731669d1cf69b0ab3de842ae2687cf527 -http/cves/2023/CVE-2023-1835.yaml:be9a5a5b794579197af82f44ff683eeffd70e0db -http/cves/2023/CVE-2023-1880.yaml:b5652f0453e1c11c18de837e03b68109a8f87622 -http/cves/2023/CVE-2023-1890.yaml:a3ac6c6d49c3815df0a4ec3eec864e832cb978d6 +http/cves/2023/CVE-2023-1780.yaml:c2505d2b57a292f55ed99e060309fc8a207d3b8a +http/cves/2023/CVE-2023-1835.yaml:1d669667484df211e221884e31e3300ad9aa3e8d +http/cves/2023/CVE-2023-1880.yaml:2f61f1e81b8dd0adc8250de5b3afa0586e330d5c +http/cves/2023/CVE-2023-1890.yaml:a35a0fb9b8ab1bd03d27d320b7a8f6a6a32c997a http/cves/2023/CVE-2023-20073.yaml:dcf9603e426635ad873ee7b7ca2e2692e9836c28 http/cves/2023/CVE-2023-2009.yaml:f99b3fc40a11e68fe14acae596e94d7a7eb97db2 http/cves/2023/CVE-2023-20198.yaml:67512a6ca70bf313e3f9ebab4184edb48722858b -http/cves/2023/CVE-2023-2023.yaml:0676330b923f5cc28bcb91e87ed0a8c669f92faa -http/cves/2023/CVE-2023-20864.yaml:fbf69972ddc548eda3cbe00785df415b8ff06f02 +http/cves/2023/CVE-2023-2023.yaml:04d7014bf3b26dbe38c4da416c447b98edc422b6 +http/cves/2023/CVE-2023-20864.yaml:7859e3e39261c2cf33a75bf7932706521c30bb58 http/cves/2023/CVE-2023-20887.yaml:5d6de58d483ccf734f6fa3dba4ba1124979928ab -http/cves/2023/CVE-2023-20888.yaml:3f0c0ad29ec8ec04556b83f4e3dc6654c506f8dc -http/cves/2023/CVE-2023-20889.yaml:0f46aa559b69556e290323be0bee6e44efb69d39 +http/cves/2023/CVE-2023-20888.yaml:f6fe8b7e47bd1ae7f913abd47941a9241c1e5687 +http/cves/2023/CVE-2023-20889.yaml:bfacbc4b7d0041c9c92aff4a9e24df93020e8b7c http/cves/2023/CVE-2023-2122.yaml:32dd06758522c7f129e7bce74a4613f01e926649 -http/cves/2023/CVE-2023-2130.yaml:4838fa744e45b4d044c725b92719da123893d999 -http/cves/2023/CVE-2023-2178.yaml:9b0d8f113be66416dc23d6906851a4ed5764bf7f -http/cves/2023/CVE-2023-2224.yaml:9195263af8182f36661017cf6812c9304f9c77d0 +http/cves/2023/CVE-2023-2130.yaml:0d3c243151b412eaf95afbf74d500aa195ad84ad +http/cves/2023/CVE-2023-2178.yaml:c00c24ba86f07753cdf50040dd9bc833ee1aeab9 +http/cves/2023/CVE-2023-2224.yaml:52d904aedcb2012bae1c9721f3b2b7280a253524 http/cves/2023/CVE-2023-22432.yaml:40ed7dd9e1f8ac7073dabd77dc1b39bcd542103f -http/cves/2023/CVE-2023-22463.yaml:dfb8683c55221bc12f9a4bd63ffd499f58551a3f -http/cves/2023/CVE-2023-22478.yaml:d128b45796dc8c95aa136fd8d9ce345d0e285c4b -http/cves/2023/CVE-2023-22480.yaml:0978505536f0fdafe0b4be396984d37a49b4c1d5 +http/cves/2023/CVE-2023-22463.yaml:97caff9ad43e5e0ad7c9b7707840611bfc2db33c +http/cves/2023/CVE-2023-22478.yaml:c7c3a1510e739f1819a24d6b26eed7634ef1a438 +http/cves/2023/CVE-2023-22480.yaml:790e75466687c5e027f02228261e4f9816dad661 http/cves/2023/CVE-2023-22515.yaml:2ad91130a9993c4670a782d8edebb6a1fc14cb8d -http/cves/2023/CVE-2023-22518.yaml:34e3c9422d3bbe59583888a12ab2fbee91179761 +http/cves/2023/CVE-2023-22518.yaml:1f39fcb2b0ccbfdfb31cb424734a795e7b2ea4d8 http/cves/2023/CVE-2023-2252.yaml:bb02189bc936b107119e8db698983075c295bb78 -http/cves/2023/CVE-2023-22620.yaml:cbf71a2a90550a35b25fd49839faaf0bc92f697a +http/cves/2023/CVE-2023-22620.yaml:6839f7bd529514c18304d54eef3275cdf0b35716 http/cves/2023/CVE-2023-2272.yaml:8151be7c84c255cca681035c9ee57feb2c0af1fe -http/cves/2023/CVE-2023-22897.yaml:c83c905c14279e1bae47bc46e6b21847a7de5652 +http/cves/2023/CVE-2023-22897.yaml:18d1a8e92201e14027f7f459eff83ac3a5861c62 http/cves/2023/CVE-2023-23161.yaml:756772379a2e364dbd2d5dfa88992beece82c181 http/cves/2023/CVE-2023-23333.yaml:866671f1d4e179b03002cf382c0a68ca574f41e2 http/cves/2023/CVE-2023-23488.yaml:4e5d0b7db8986c223987d62fbd6fdecee252f3e2 http/cves/2023/CVE-2023-23489.yaml:b5b54203c517f05194e74f2b1601f475b1728e71 http/cves/2023/CVE-2023-23491.yaml:f299be80b27dfca2b272d3870d9adce77a01a9dd http/cves/2023/CVE-2023-23492.yaml:da694056094a4e2ee8424cbb7fdd83e3712b12fe -http/cves/2023/CVE-2023-2356.yaml:637f6bc800cb9b4bde132676b45a9c31d36f89ba -http/cves/2023/CVE-2023-23752.yaml:2930c28a73bcaf2fab4817349b65de0214cc494c -http/cves/2023/CVE-2023-24044.yaml:f10895cb00be85b347acaec8fb70562cd5831bca -http/cves/2023/CVE-2023-24243.yaml:778647942510d7f487914db4bac54d29de9b2b08 -http/cves/2023/CVE-2023-24278.yaml:b6c3d071a852fb56570eb20f3644d2346d494892 +http/cves/2023/CVE-2023-2356.yaml:8c04ae362f21907ad12a56b9d40f03329640ffd2 +http/cves/2023/CVE-2023-23752.yaml:038dd2e2e8ccc7fccca74d991153774f7e5857ed +http/cves/2023/CVE-2023-24044.yaml:faeeb082f03bc51cb4405c1994b075fff771c2b7 +http/cves/2023/CVE-2023-24243.yaml:f5325cc64c7c9ba5a8b4d5093ec0ed5227677c81 +http/cves/2023/CVE-2023-24278.yaml:eaed9aac9e0e454e16bf9b227818fda3607210cc http/cves/2023/CVE-2023-24322.yaml:b78ade64d06514afe61280381e2ef7d8f8e156d3 http/cves/2023/CVE-2023-24367.yaml:00eec3f3fabe9bd20f29ec7c09425ba7d6223c2c -http/cves/2023/CVE-2023-24488.yaml:1ee42ac04e82321dd3648061a1fda871c6f56a26 -http/cves/2023/CVE-2023-24489.yaml:19c3449ae4085f437277b4c5cff973928f3cae9d -http/cves/2023/CVE-2023-24657.yaml:115f94653acbb696da9a000467c260a89c124326 +http/cves/2023/CVE-2023-24488.yaml:fb1a8c16468a9be9b86729d297a8b1034388f877 +http/cves/2023/CVE-2023-24489.yaml:1261412d218e52247dac9d4324edd9d0a6f71884 +http/cves/2023/CVE-2023-24657.yaml:492ebb4d7cce0e1895c6ef3da7a06944d77a1c5b http/cves/2023/CVE-2023-24733.yaml:0bec7599ad281e67aa7d79ace3765fe52dd4b020 -http/cves/2023/CVE-2023-24735.yaml:251e3d685f8684018eea8aaed56300568fe5f6cb -http/cves/2023/CVE-2023-24737.yaml:54f7217ebcfa1c58b306d24986c7952875b7b82c +http/cves/2023/CVE-2023-24735.yaml:d9432a5a2660a2ec35915e067e927b3eedb835f7 +http/cves/2023/CVE-2023-24737.yaml:366799cba4ef13a7155adac10e6ab82bbc39bb23 http/cves/2023/CVE-2023-2479.yaml:425059aeaecc4be07d540245ed0ac885f96dbdee http/cves/2023/CVE-2023-25135.yaml:90f9a20ce44fe654a551afce56cb56812fefcb6b http/cves/2023/CVE-2023-25157.yaml:25c1478eab1b836b765e4a2eaa68f5c0ca1908b8 -http/cves/2023/CVE-2023-25346.yaml:155552aff07303c54d418b0cb1280d84fad93c33 -http/cves/2023/CVE-2023-25573.yaml:f3f7a2ce3aaf43b6fe353128850e0f2af29eb4ea +http/cves/2023/CVE-2023-25346.yaml:8b4c7db68b1970ea64db63436f2d335d7f4893c9 +http/cves/2023/CVE-2023-25573.yaml:5d3e2e91c0c29ac4416ef1537b12a80e0dbf6c2f http/cves/2023/CVE-2023-25717.yaml:1147292aaa00f124b4635b1f891a1957e91dc6f0 -http/cves/2023/CVE-2023-26067.yaml:b541bbb222e697f02be45d77c382443348091ae3 -http/cves/2023/CVE-2023-26255.yaml:1209c391aedc008484e596d6f9a0c3b2591ee52a -http/cves/2023/CVE-2023-26256.yaml:2297daf183d875d58cae04387484dc6ed2a25a63 -http/cves/2023/CVE-2023-26360.yaml:34074d10eaa3d036ad403370f37a329e8441a758 +http/cves/2023/CVE-2023-26067.yaml:1b8fc04e4c5570bd24042df58bb9c4404a7d8914 +http/cves/2023/CVE-2023-26255.yaml:a22cf6aa7f473edcb1a71b03309ba9a08051eb64 +http/cves/2023/CVE-2023-26256.yaml:0a6eff74c02e2ebe26edce2e1641fa210ce06f03 +http/cves/2023/CVE-2023-26360.yaml:eab7ab724b7a881abe66fe79fa30ed4bbc71d348 http/cves/2023/CVE-2023-26469.yaml:488fbc9940f191504fa60a62e1d6d1e6cb23eb51 -http/cves/2023/CVE-2023-2648.yaml:dd82fae48256635396b5468454ea633fbd53de58 -http/cves/2023/CVE-2023-26842.yaml:513dda10fb91313606e61a2392569af1719db5f2 +http/cves/2023/CVE-2023-2648.yaml:83f278332443c5d3c91738b85227bf5a4e004d2b +http/cves/2023/CVE-2023-26842.yaml:9bccedc886621b300d9eef15c5c3957c55bcb5b4 http/cves/2023/CVE-2023-26843.yaml:47f43e1f6191c08827cb61d0c061c40cd4c4e17e -http/cves/2023/CVE-2023-27008.yaml:a2a96bb07c41e4f7febbe50d53d80e7f9985abe8 +http/cves/2023/CVE-2023-27008.yaml:c4941caabfe991e6e5c747a2887706f3552a47f0 http/cves/2023/CVE-2023-27034.yaml:a8c614c2287cd9696962c0e7a4345986d019784b -http/cves/2023/CVE-2023-27159.yaml:da7361de68f61428aca7df70c1e3cb1a3ed74c6e -http/cves/2023/CVE-2023-27179.yaml:bd6b5ba9752c18c83170f917ffc895449fd9a179 -http/cves/2023/CVE-2023-27292.yaml:1cea19f02772f6082e5b0070f9798c5ddfb7c45c -http/cves/2023/CVE-2023-2732.yaml:f99eb3b7d801cf80685639d4b9711d0aec87b626 +http/cves/2023/CVE-2023-27159.yaml:1bc9bb8bf672973b30d64fd9f990d581cf379eae +http/cves/2023/CVE-2023-27179.yaml:78d71276488d3ad4a129c3181a4ff5c93f115114 +http/cves/2023/CVE-2023-27292.yaml:421c7d51805cde12686ef0cca96b982a764144f7 +http/cves/2023/CVE-2023-2732.yaml:89973411bdbf7549e3bed1ffd8798b4c8926b80a http/cves/2023/CVE-2023-27350.yaml:c4175d945f99668f6084a811c7d3cda7d4527563 http/cves/2023/CVE-2023-27372.yaml:fa7f4772d7695f04831af0c05df8cc946c9d79f0 -http/cves/2023/CVE-2023-27482.yaml:71d3f9a60cb98d72e60679bbf493d04959e542a5 -http/cves/2023/CVE-2023-27524.yaml:1492535880395165fce0713f600eb1cc075345ab +http/cves/2023/CVE-2023-27482.yaml:7d91b22e7555b9a4db4fee292e1430267f128da5 +http/cves/2023/CVE-2023-27524.yaml:df90aaac394b747db8bee321546865370d2a1f31 http/cves/2023/CVE-2023-27587.yaml:f8a2d4f998524a298603a8b13d0ab9ebcb5130b8 -http/cves/2023/CVE-2023-2766.yaml:748ff40b6ec5d2a96e664ddbd42998a8bebf000c +http/cves/2023/CVE-2023-2766.yaml:3e7c72845d8744602e6a40c9d2e36a57ba210d83 http/cves/2023/CVE-2023-2779.yaml:39bb3fb843bcdbeac19ef12e7f39d7938772b455 -http/cves/2023/CVE-2023-2780.yaml:855f0f79e263add4acbad520bc492d72ac0dab9b -http/cves/2023/CVE-2023-27922.yaml:14bb483675bd1ece242e1524838b252a7248e9a0 -http/cves/2023/CVE-2023-2796.yaml:7752327ef49f04a96e7932d408cee8d96ac5f2f3 +http/cves/2023/CVE-2023-2780.yaml:f6062df5400f84572a2eebd307666a165d19cefa +http/cves/2023/CVE-2023-27922.yaml:e9f4f9b9f56e35750d5ba3e2c243c03941e871eb +http/cves/2023/CVE-2023-2796.yaml:2f780486ccfac4322ff5653a648a9a7c5126f898 http/cves/2023/CVE-2023-28121.yaml:f75bb6647d8faef1664d1270a08ed23cdf38f5ca -http/cves/2023/CVE-2023-2813.yaml:0bb0943668dc1c089cfd586d8a7687d5377b8017 -http/cves/2023/CVE-2023-2822.yaml:07c85399f738d40d62511922fc4d386becfd35f1 -http/cves/2023/CVE-2023-2825.yaml:ac57061a663652e97f34a1d1bd264a43015b4697 +http/cves/2023/CVE-2023-2813.yaml:7aefaba6cbf7333e7ff413ee872f763278cc2622 +http/cves/2023/CVE-2023-2822.yaml:e8a161582331f06d4832e8c9b2f56e7dffc63880 +http/cves/2023/CVE-2023-2825.yaml:e68eb21844c291dfc8fff62d24c3cea34a8e128b http/cves/2023/CVE-2023-28343.yaml:14b659371c7e58ed203f59dfaf35dea4ac3748db http/cves/2023/CVE-2023-28432.yaml:02208f8f40b5bf315514a3d18e9e1ab726c6a18e -http/cves/2023/CVE-2023-28665.yaml:78934145d881d25cb419f0bac765bedc44503ece -http/cves/2023/CVE-2023-29084.yaml:859b7d9bcd8dd3a8b739ec81a775e0d2711b18c8 -http/cves/2023/CVE-2023-29298.yaml:4e225091a56627f6c599cfe911c4f09d3253d634 +http/cves/2023/CVE-2023-28665.yaml:8a50d54512bf1bb0331c64f72f1dcdb3f001e47d +http/cves/2023/CVE-2023-29084.yaml:6ab13c4c2404227260013dab29c785d7c3433256 +http/cves/2023/CVE-2023-29298.yaml:6eecab1378f888827b8c20597d8cc03649a166c4 http/cves/2023/CVE-2023-29300.yaml:e2eb006a8500786bb93fb4061547ae326fc6e0ec -http/cves/2023/CVE-2023-29357.yaml:ad70ed75c639500cf80c73deda8c0fcde344cada -http/cves/2023/CVE-2023-29439.yaml:ceb49a867c4aa0c85677c26adb0c01a96d05f7cc +http/cves/2023/CVE-2023-29357.yaml:5a7710a7e09ac7e8f4a8ea7a49976c51ffc5e973 +http/cves/2023/CVE-2023-29439.yaml:54f82192fcf71464144dc7b1906719d7534c8688 http/cves/2023/CVE-2023-29489.yaml:bfc65adb45845b3964fa94a0de4c7e34ce99e663 -http/cves/2023/CVE-2023-29622.yaml:1d4fe8f2eb564e209959a4fe9e89779bbd4bbc2d -http/cves/2023/CVE-2023-29623.yaml:97b707e0235cca0705bebb336085b54d5173db7f -http/cves/2023/CVE-2023-2982.yaml:9bbe0ca25a74f723b0ee57a90749ad574639bd85 +http/cves/2023/CVE-2023-29622.yaml:24b89cef00286e8cd6aa41ea07491d834b155b07 +http/cves/2023/CVE-2023-29623.yaml:15ca2e3d8f1d45c4f4cdf2d83b3d96b5c4151067 +http/cves/2023/CVE-2023-2982.yaml:36a1527461b92a3607c50fa932ee9328564caa4d http/cves/2023/CVE-2023-29887.yaml:4c752df3193f373050252b854fea50733a2770c0 http/cves/2023/CVE-2023-29919.yaml:11c0a2c12f0318d06e1b7567b679b268423dc14f -http/cves/2023/CVE-2023-29922.yaml:64d05146c1f54b1baf68e11838bbf50c65106c13 +http/cves/2023/CVE-2023-29922.yaml:780160e378520a64b24bf5fc30654fbff3c1fd8c http/cves/2023/CVE-2023-29923.yaml:a8990f5c7c165f96db9f4d2b8b53537cb9873f19 http/cves/2023/CVE-2023-30013.yaml:7e302ae83e32a2a4df5fd525789f4e1194cbcefb http/cves/2023/CVE-2023-30019.yaml:aa7cc8951ad26b32c920cc964c370ea39463be02 http/cves/2023/CVE-2023-30150.yaml:5003a569c44b340098690cf7b0937cd78d757f32 -http/cves/2023/CVE-2023-30210.yaml:ade0770576383dca0e67c2495bf7272465b4e03a +http/cves/2023/CVE-2023-30210.yaml:24a600d1d4178fc278b551e615ce68c44620319e http/cves/2023/CVE-2023-30212.yaml:3c166597964271fbdd72974396bcb8e1b31bcd78 http/cves/2023/CVE-2023-30256.yaml:8745c771a8510ea5c1d924642942ddb1a76a98a0 http/cves/2023/CVE-2023-30625.yaml:fdfc8629acd991e6c5a9689ecbebe6fb606a5dcb http/cves/2023/CVE-2023-30777.yaml:be29a0c67b55e5b89bf03b0849aaedbc5ab341e6 -http/cves/2023/CVE-2023-30868.yaml:08dfee8fe1d9ca7040cd703affd8b4a708bf0f27 -http/cves/2023/CVE-2023-30943.yaml:743eeea8da1faca58daf4f7d5927b5bad25e8c88 -http/cves/2023/CVE-2023-31059.yaml:6359589019e12fb4894a5477a0b894a2eb1095cc -http/cves/2023/CVE-2023-31465.yaml:f48ed80bc1ce9b4573312eda514690377cfb12af -http/cves/2023/CVE-2023-31548.yaml:03d5df5836df20041388d3f4de5d2e990f36066f +http/cves/2023/CVE-2023-30868.yaml:f3a148df1ad9314f1a8932bb8cf8c66262e092fc +http/cves/2023/CVE-2023-30943.yaml:a260fa2c02850aeafc5aad30352e85cb3358bcdc +http/cves/2023/CVE-2023-31059.yaml:d5cc64727a1d26334c174188eeec8a756d3a4a17 +http/cves/2023/CVE-2023-31465.yaml:81126acd0cc17c5a857ca819c92693b8538ce579 +http/cves/2023/CVE-2023-31548.yaml:fa4c61acbbf867aa0d902b7914ca4a649aef584e http/cves/2023/CVE-2023-32117.yaml:d607de0b2e6561a6f63c504cd7a24a9fbedd78e6 -http/cves/2023/CVE-2023-3219.yaml:e1fb29243183b69220a9a59354034b95ebd6cc10 +http/cves/2023/CVE-2023-3219.yaml:11226ea01e403dfaeeb9053d9210f647e122f623 http/cves/2023/CVE-2023-32235.yaml:0d199a6f5a560e998bfaabe0fb7a4abb381812d5 -http/cves/2023/CVE-2023-32243.yaml:1eacbc6079361a1388c13cc151b7460775984a78 +http/cves/2023/CVE-2023-32243.yaml:03cf07fe205cf9f5bdf49a8c3f645c1517212e41 http/cves/2023/CVE-2023-32315.yaml:3538c4e9f35b2127237e2f8b2f65384e2b75fea7 http/cves/2023/CVE-2023-32563.yaml:4323f33dbb2b2cc96f52b28d701ec534d15cf38b http/cves/2023/CVE-2023-33338.yaml:c6d24204cc6b5ca98e5f3fd3a1bd85d80325659f -http/cves/2023/CVE-2023-33405.yaml:3730493324a02f0964479b7d8e45cd83980c65dc -http/cves/2023/CVE-2023-33439.yaml:b137cb294a5985b71bc87891647d13304b89b564 -http/cves/2023/CVE-2023-33440.yaml:83ec2deabea8b0c821125f031392e392eddbe7b7 -http/cves/2023/CVE-2023-3345.yaml:c06e9678f0cfd0c6b7c6d92a4a416b4e11a9a2e7 -http/cves/2023/CVE-2023-33510.yaml:f2db7def11b69f6968243f73764b80e86a08010d +http/cves/2023/CVE-2023-33405.yaml:3eb97a6ffa0154283232ad412e807671f3066b53 +http/cves/2023/CVE-2023-33439.yaml:5222e570c5d8b4e931c802d34d24c7c2eb450c71 +http/cves/2023/CVE-2023-33440.yaml:a3ca1d07c4c6c634c9b4ae252cdd7e031a316e82 +http/cves/2023/CVE-2023-3345.yaml:7fd9b74643306bf95f24d65e05e1ad638bf286e2 +http/cves/2023/CVE-2023-33510.yaml:ba80501a5ff0e69874580da243252c3bb69708af http/cves/2023/CVE-2023-33568.yaml:1b23808a8f6376273b0c0fb374364d07cf971eb7 http/cves/2023/CVE-2023-33584.yaml:b1dc9c15ddd4190bcad5275e13b58c8e647c72ef -http/cves/2023/CVE-2023-33629.yaml:8a6c1c4dedf01196fea64a5e53b28914ed975ab7 -http/cves/2023/CVE-2023-33831.yaml:4512eb9eb81e61d82b13dd881e0f5948d46c7603 +http/cves/2023/CVE-2023-33629.yaml:bbfeec1e46aa299e792fed64617fa55122e3215e +http/cves/2023/CVE-2023-33831.yaml:75da08212abbb9987a835e17b221d468a7f478ef http/cves/2023/CVE-2023-34020.yaml:f66a950a102d54d43cd9bbc3e692cfd911be724b http/cves/2023/CVE-2023-34124.yaml:2012e2b9e978c2cdf1d54ce7dca976548ed113e3 http/cves/2023/CVE-2023-34192.yaml:7e70ef7798dded877de22ef740e2c5574c30e045 -http/cves/2023/CVE-2023-34259.yaml:af095e81bb7762c992a2afd64c4c32a7c6aaae86 +http/cves/2023/CVE-2023-34259.yaml:db9fafd2b7e4153e463c11ff13ad1013c60e7099 http/cves/2023/CVE-2023-34362.yaml:96ead6de4aef88c733031acc8766cb4a650f5ee2 -http/cves/2023/CVE-2023-34537.yaml:5298d4803f143283b5a97c331d6bd1945357d8d4 -http/cves/2023/CVE-2023-34598.yaml:428b17865ef20819d35a0850ce71113b8d87bcd6 -http/cves/2023/CVE-2023-34599.yaml:daefb6d443336f3f319e41ef42f5a82f3c3d1231 +http/cves/2023/CVE-2023-34537.yaml:feb0970969555a8cf7bafb133f08d50dd09e1d9c +http/cves/2023/CVE-2023-34598.yaml:d3bfcaa83e8c186043682ded7b3639cc1e3b02c2 +http/cves/2023/CVE-2023-34599.yaml:e5e50810c52df4aead578ee29b6b2250fe0230ce http/cves/2023/CVE-2023-3460.yaml:8147e18b140f698491d19068af46f3911fab6413 -http/cves/2023/CVE-2023-34659.yaml:6311f2f9d6dc16622147d08c9023456d7292e93b -http/cves/2023/CVE-2023-34751.yaml:b32e3e28da37ef0ec8a32a8a54142a5a7f477087 -http/cves/2023/CVE-2023-34752.yaml:5985a54b79a43d73bf13aaab2dfafcef79ec5b55 -http/cves/2023/CVE-2023-34753.yaml:2c249aa283fd1a468bc0a79e6156dc394872d605 -http/cves/2023/CVE-2023-34755.yaml:1fb6155af3467494d72821f00d093f2eaacd2fc2 +http/cves/2023/CVE-2023-34659.yaml:36fe813359112ad5190f6d91d878159df57b6826 +http/cves/2023/CVE-2023-34751.yaml:683ea3c757de58c15abd5abc1712c88085f0d46b +http/cves/2023/CVE-2023-34752.yaml:95ecb70f9e7299ae29c6664fef4071c5365725bb +http/cves/2023/CVE-2023-34753.yaml:ba222f01ac131865ee95ef5703b2ba59453feed5 +http/cves/2023/CVE-2023-34755.yaml:abf2fbf0500b91789b5f980f1c0fefaf9344a678 http/cves/2023/CVE-2023-34756.yaml:c8d0abfa7fdf4566ee01acd163b22b63be8ef339 -http/cves/2023/CVE-2023-3479.yaml:b027645feda6ec60be06915ab620c7e9817e5692 -http/cves/2023/CVE-2023-34843.yaml:85e2f23109875d7a1df77e6eeb554e5d5e6d75c0 -http/cves/2023/CVE-2023-34960.yaml:e1058c7bf8ebe21737222e2878a48347589d04e5 +http/cves/2023/CVE-2023-3479.yaml:d825c11a7f75713b2f0bb7ab73141326c810f3e0 +http/cves/2023/CVE-2023-34843.yaml:f88c99300034de4710977ef618f61e498487bf81 +http/cves/2023/CVE-2023-34960.yaml:3d0592a7ea67e09de172b1a6c3b4690e8638973f http/cves/2023/CVE-2023-35078.yaml:8f990ceffbd707473f74a21d3e643bfd285da19e -http/cves/2023/CVE-2023-35082.yaml:6a7e37d0e9108d34ced8095ebc0c9247f0216fde -http/cves/2023/CVE-2023-35813.yaml:716f45a9f8f65b7078f867d37f6907021df1c113 +http/cves/2023/CVE-2023-35082.yaml:3e861856edb845ccb440983018500597471880a8 +http/cves/2023/CVE-2023-35813.yaml:3032a5234a6c32c7dddb395a0c3b5fb37c604bb6 http/cves/2023/CVE-2023-35843.yaml:d06144a5ff0872b18ed32620c3dc4d286c2bca3a -http/cves/2023/CVE-2023-35844.yaml:3ef741b23d0b89efb72d527852ee83f3c2b3d56e +http/cves/2023/CVE-2023-35844.yaml:40846b68e61746d38bd1f4346607c165df933347 http/cves/2023/CVE-2023-35885.yaml:92f4a3089c7649df4787b8bae8909ad863a38e74 http/cves/2023/CVE-2023-36287.yaml:4b0fbc385c49df580bf3633669b8efa70624f3a2 http/cves/2023/CVE-2023-36289.yaml:8073db855fdff9acd634f72075a951702c236838 http/cves/2023/CVE-2023-36306.yaml:fa715aad7e18e97b5322be60af986930e41974bb http/cves/2023/CVE-2023-36346.yaml:91048eb0ca2ca66ea2f6ed4257bc33ca082bbbf7 -http/cves/2023/CVE-2023-36844.yaml:0be8b62e27d20b234700ac646210c9a28fb1a4c1 -http/cves/2023/CVE-2023-36845.yaml:f6ff3fd0c9cc4ca7bc39c7f8ba62470307c002b9 -http/cves/2023/CVE-2023-36934.yaml:2a915f06317862d4cee3d86cc61315e113ddd673 -http/cves/2023/CVE-2023-3710.yaml:d7e8ac18958cee92bb94b1430a66f75aad0ed932 -http/cves/2023/CVE-2023-37265.yaml:c007bfba389d103dd6d1c6ab6cf75d57d72784ab -http/cves/2023/CVE-2023-37266.yaml:aab612fda082cca843bdad80fef397bc8d868d9f +http/cves/2023/CVE-2023-36844.yaml:73e1fe8fd6ab02cd3d0fe216b331d2fab7b7c533 +http/cves/2023/CVE-2023-36845.yaml:23f7a42fffb76220bb10136f99f7c654724400ee +http/cves/2023/CVE-2023-36934.yaml:6a1ca488556235bb76108a8e833d7680ea2668dc +http/cves/2023/CVE-2023-3710.yaml:abbf321f315997cf735649f0c2d049f6d91923b4 +http/cves/2023/CVE-2023-37265.yaml:c313bfd5df1cd94eb435f22892702880a38e5358 +http/cves/2023/CVE-2023-37266.yaml:92749805586939218aaa3d96cbec04455fb6786e http/cves/2023/CVE-2023-37270.yaml:ad092669fb179ebfdc0fa0ab498f27b54a7e40e6 http/cves/2023/CVE-2023-37462.yaml:467c17f0cec840ad26d7056144c2746ed9794851 http/cves/2023/CVE-2023-37474.yaml:658dcc4b0f146e93494edfefb33b5aac952b9871 http/cves/2023/CVE-2023-37580.yaml:54f2c1151c225cd32da3b4fe8bfa21e9eca06f3b http/cves/2023/CVE-2023-37629.yaml:4e17942a6a24c801646e9f4a633619a51aee22ca -http/cves/2023/CVE-2023-3765.yaml:00802bc905e1475f460a29e1b573f797c9fa4e7c +http/cves/2023/CVE-2023-3765.yaml:94ec5971ce71d7326cb023180d9e7fd7febbe4e7 http/cves/2023/CVE-2023-37679.yaml:8aa0e15b40fe4bf8cb42a7bf74126c2e31c30296 -http/cves/2023/CVE-2023-37728.yaml:033f53a802ae8a1ad4c46be123ad8f8fd900ffee -http/cves/2023/CVE-2023-37979.yaml:64b4dac876c20e3ce42f94ff4588fa8e10cd0d38 -http/cves/2023/CVE-2023-38035.yaml:691f29b9ebbae2f1a77fb3dfccb69c7f461d273c +http/cves/2023/CVE-2023-37728.yaml:cda19f756c2a2a57ce2d913eaae4b9f290c41afe +http/cves/2023/CVE-2023-37979.yaml:bd1ca5dbbbeed0d05d39e0298114a576b84a9ede +http/cves/2023/CVE-2023-38035.yaml:e9a01698528a0ac7a9c80c67f8fe7504acc74a4e http/cves/2023/CVE-2023-38205.yaml:0d3655511bbf7459c77ea9d2d27279a66b098746 http/cves/2023/CVE-2023-3836.yaml:1de0d7d5fec4e6101464b2df3b35c04266274fe8 http/cves/2023/CVE-2023-3843.yaml:5e100aa4ee76a42afe08c5c96647960978aff6ad -http/cves/2023/CVE-2023-38433.yaml:fe3652664841d7c204e60ed0f027786d99d5909b -http/cves/2023/CVE-2023-3844.yaml:3adb9fb8d50fde5a579592f85cd00f812c096daf -http/cves/2023/CVE-2023-3845.yaml:47651192a2c8947d46761054f11735e5ddc9d8f7 -http/cves/2023/CVE-2023-3846.yaml:81e7fd4843d5337303f16bc1a4381a1e19ad400b -http/cves/2023/CVE-2023-3847.yaml:06e358444ef9a5a8759995e1fd928814139c1791 +http/cves/2023/CVE-2023-38433.yaml:1990396a4a425e41316c8ba2f248936e8d1a6349 +http/cves/2023/CVE-2023-3844.yaml:65436cb4d280c6cd1809810843ecdb87c6164d96 +http/cves/2023/CVE-2023-3845.yaml:178021a659b9ed7aacf0fbcdf522da454441ddd2 +http/cves/2023/CVE-2023-3846.yaml:bd16038432cf7f4a421607bcb656a4b1520c9708 +http/cves/2023/CVE-2023-3847.yaml:8fac0d9bee4d68ae59f7eeb85e6ba96578f7147d http/cves/2023/CVE-2023-3848.yaml:9a7e1fb2dfe514c1241ae320bb93f964eca6e764 http/cves/2023/CVE-2023-3849.yaml:abb6a1cd51cd58699213d0e6d6698a5eeab9731e -http/cves/2023/CVE-2023-38501.yaml:3920f3810d72cbd86ee07efe892b0e73707df290 -http/cves/2023/CVE-2023-38646.yaml:e61b94c002219f045aed74aa71c9f5a7a49f3f68 -http/cves/2023/CVE-2023-39026.yaml:78d807a456e5cc02c6a20067d0af3c839d494391 +http/cves/2023/CVE-2023-38501.yaml:015e13b8aa9307a8504644abc92994d1b983ea1b +http/cves/2023/CVE-2023-38646.yaml:18f6c66f23ca418680d9ce7efa8823b83bedc71a +http/cves/2023/CVE-2023-39026.yaml:44dba2df3564cdc274341a0cd2079b55b8c87b7b http/cves/2023/CVE-2023-39108.yaml:c106f9337014e5e37e6bb6aaef8ca7ad735cc9af -http/cves/2023/CVE-2023-39109.yaml:b7737a8750e0d1d1f27219ec34418b480ed4903a +http/cves/2023/CVE-2023-39109.yaml:70ea12f1caf11b3436ae9b55e30d7b5e7e43c23f http/cves/2023/CVE-2023-39110.yaml:d5a6635d58bef83e269baa4545c9a2ca775eed71 http/cves/2023/CVE-2023-39120.yaml:9462c57e65e4d5929c6b9f1a18a31a7c9a3eb2db -http/cves/2023/CVE-2023-39141.yaml:ae025686726390e5f73cbdf262f1270b3b912f32 +http/cves/2023/CVE-2023-39141.yaml:cfe47d6753cf3100f7f2d9c0a8f7924b2d17b1e4 http/cves/2023/CVE-2023-39143.yaml:2727de9904547d7d0e882c705aff28d00482822e http/cves/2023/CVE-2023-3936.yaml:b32055efd15c4ef41c9fb776804e58d0286aa47e http/cves/2023/CVE-2023-39361.yaml:7144a7941472486f27ab42aaad98af997cb176cb -http/cves/2023/CVE-2023-39598.yaml:ad7a316b5b79a9d3823c1908c7d9bed53a66844d -http/cves/2023/CVE-2023-39600.yaml:869451754c8a2450533d345049015b22d932c085 +http/cves/2023/CVE-2023-39598.yaml:89d9f3cdfcbfc1ebe9e3654da9a645e85192ddd3 +http/cves/2023/CVE-2023-39600.yaml:a0043c5329f36438b0d19ff0564211caed2e9631 http/cves/2023/CVE-2023-39676.yaml:877a078d09532d7e34f362b174816b7786cf2a5f http/cves/2023/CVE-2023-39677.yaml:ee8b242ffc6f1c0992c9fb34181d70377bcfa07e -http/cves/2023/CVE-2023-39700.yaml:3ee8c1c297934f7dc38e249074937a6bd79e7692 -http/cves/2023/CVE-2023-40208.yaml:7610a8e8b31368022d14ca1fe6621b6de6746ef0 -http/cves/2023/CVE-2023-40779.yaml:a6382e65d32a22aa47399a815da80f352eb7530b -http/cves/2023/CVE-2023-4110.yaml:652ffa021667ad1db641e778701371a5bf7b256f -http/cves/2023/CVE-2023-4111.yaml:84ae77623197cecd7238ddbf9d18aa4e9acc9603 +http/cves/2023/CVE-2023-39700.yaml:f03af9e75125bc410579d858f170e3279c43e995 +http/cves/2023/CVE-2023-40208.yaml:e6f39b4d60ba694091d351daa737d14e2aa989cf +http/cves/2023/CVE-2023-40779.yaml:3b733d03782447bdb12033b200020cf148a77e8e +http/cves/2023/CVE-2023-4110.yaml:8dbdc0915cfba278aa8e5f162e09aeecb3a6dc03 +http/cves/2023/CVE-2023-4111.yaml:3675353f3a0384946f858cf16b39cd39b6008790 http/cves/2023/CVE-2023-4112.yaml:7ddb08fd24f87c8817a6561011159707e2f06086 http/cves/2023/CVE-2023-4113.yaml:6c3b24b57543cccc4c922c3830658b4e1c39cb8c http/cves/2023/CVE-2023-4114.yaml:b5e0f8695616948b9e709c1477eecc74bb9f3dd9 http/cves/2023/CVE-2023-4115.yaml:e269da4722682944de96e7440aec989d2303cfc3 http/cves/2023/CVE-2023-4116.yaml:f7a9f9d905ab2e6b0e8a681aafdd8eddd35e882a http/cves/2023/CVE-2023-4148.yaml:318e4f4c81696c9fdadff01d3f1d57664688f572 -http/cves/2023/CVE-2023-41538.yaml:3879981e7bd817de3d2e4fc2539bd7ad49b10aa2 +http/cves/2023/CVE-2023-41538.yaml:0026604e2a1608438c045f7846f7e7e832c7ee9a http/cves/2023/CVE-2023-41642.yaml:d96cdefbc797e3e0a271a52f9ad55f4e8185d134 http/cves/2023/CVE-2023-4168.yaml:e06f85e5c882a66a8a20f8129602af2a001dd801 http/cves/2023/CVE-2023-4169.yaml:72f9cd1d88af6d97ebf43e65a094ece175fbd603 http/cves/2023/CVE-2023-4173.yaml:088ff9d3d4255efa72ef985d32c5d26553d8dd8d http/cves/2023/CVE-2023-4174.yaml:8792e89c7dea2105d804182d5397dd5c7d46e836 http/cves/2023/CVE-2023-41892.yaml:ecc7e4910d8c61fdb60fee61b08a4d00e1182b11 -http/cves/2023/CVE-2023-42442.yaml:a3d0c223168ea90713c82aa7e955bf9582fd55b3 +http/cves/2023/CVE-2023-42442.yaml:b4f9d43f8fd102eb653c334150a341de1ce0e480 http/cves/2023/CVE-2023-42793.yaml:13eecab0f4f4c21eeb7dc79a2c21f8a3ba5b8e3d -http/cves/2023/CVE-2023-43261.yaml:6119ef1a4b165a0eb2344273272d4b60a957e973 +http/cves/2023/CVE-2023-43261.yaml:97578387488b9cca75f7a896575cb417d3ed43e0 http/cves/2023/CVE-2023-43795.yaml:9b66e508bd1bea9764169eb1e474c9e14e651ec2 -http/cves/2023/CVE-2023-4415.yaml:1d0a550325fedd7295fe6fa642f8bdc1ebc53a30 -http/cves/2023/CVE-2023-4451.yaml:83cbb8f93785783b2a2f64679893ac222aec692c -http/cves/2023/CVE-2023-4547.yaml:a7c60782ddbc6c27d9e56189bd93c689155dc2f8 -http/cves/2023/CVE-2023-4568.yaml:4bc094e78fdbe1e7ae2f86052fd5151bff7c1a11 +http/cves/2023/CVE-2023-4415.yaml:36492de9a792a0d17f36fa6ee7eee59fffb2088f +http/cves/2023/CVE-2023-4451.yaml:cd633ce6a5842ac95cc49b39a8fa2621c58b60bf +http/cves/2023/CVE-2023-4547.yaml:ffbc5b8a7d2c6ae05a094606ec72890dfd2081cf +http/cves/2023/CVE-2023-4568.yaml:a65cf95aa705448041538e70cb977aea6870c7c1 http/cves/2023/CVE-2023-45852.yaml:04ce9b5a9027d70df571e79e8ea702e77edec98b http/cves/2023/CVE-2023-4596.yaml:b7591170adaccd0983ef0315d50b2095f0befa4b -http/cves/2023/CVE-2023-4634.yaml:1790f8b6fbd194ed31a0a1080c72388c0659035a +http/cves/2023/CVE-2023-4634.yaml:ccec267ef8e62d7fa7e69a2cd642bb69a3214b59 http/cves/2023/CVE-2023-46747.yaml:51c43f180cd91245d64458f5561bc62d9edd59ea -http/cves/2023/CVE-2023-4714.yaml:200fb0e2954219fd210c71e68bcc00bc3320b6f6 +http/cves/2023/CVE-2023-4714.yaml:cc0555247a0515cd8ad6de6269ffc0911ffca77d http/cves/2023/CVE-2023-47246.yaml:c0f05a79a5f740b7629ef7914f2ec57a71955606 http/cves/2023/CVE-2023-4966.yaml:d9ce23d166f51f49e3780229ad22ad4866bf5243 -http/cves/2023/CVE-2023-4974.yaml:1782122a8971e7a44743e81dcea230a3732ad094 -http/cves/2023/CVE-2023-5074.yaml:0fc9c81746b0dc95ceff34eaa06c82f9ec3ee03d -http/cves/2023/CVE-2023-5244.yaml:0c05ec6cf5a546308335da1c615d564b146716c8 -http/cves/2023/CVE-2023-5360.yaml:a1407c328dde03c4ad324da65c0852425cf1336a -http/cves/2023/CVE-2023-5375.yaml:c5ed9f312aae4898731a2c404b85573fb8eba3fc +http/cves/2023/CVE-2023-4974.yaml:a6965bea13f3f09cb97aaf9d0a5585616e0f8b20 +http/cves/2023/CVE-2023-5074.yaml:87620ec35cbb52b716e1d59ba03cb7982835a0af +http/cves/2023/CVE-2023-5244.yaml:555527ee5bf8ca4795526d2f11d2aea92c3361a5 +http/cves/2023/CVE-2023-5360.yaml:7bb1686634563c90b4fc94f217a52c85728a425f +http/cves/2023/CVE-2023-5375.yaml:b8deb792f5df3b83440bffc41e1584ca45fb8ebb http/default-logins/3com/3com-nj2000-default-login.yaml:3c260ca4c2ee7809221fc4b9330a540795c081ce http/default-logins/UCMDB/ucmdb-default-login.yaml:627864b8eb2c47b7c717e1ed1800ba39eee5410c http/default-logins/abb/cs141-default-login.yaml:a5902dd34ba373c6f4e2cba15adbd9bf1e75e9c7 @@ -4066,7 +4066,7 @@ http/exposures/configs/detect-drone-config.yaml:8dcfc65408172b76a554d1f5970d2c3c http/exposures/configs/django-variables-exposed.yaml:30ad3076e779010142f49d0a27c4bffee7e40743 http/exposures/configs/docker-compose-config.yaml:c09c54ae8ef8b7eb9d1afea7fe19ef6b2b0169d3 http/exposures/configs/dockerfile-hidden-disclosure.yaml:7903af835aa7fa826d2d98642299e996bb701a50 -http/exposures/configs/editor-exposure.yaml:9bec4c56c6e84cb6f88b85039c930aa2e9dcb0cc +http/exposures/configs/editor-exposure.yaml:654cdebec98e685fe3b1816e54151f3c29357935 http/exposures/configs/esmtprc-config.yaml:3248d75c33e992ea44db18b2d978ab52223b18ef http/exposures/configs/exposed-authentication-asmx.yaml:d86cc5aeab17e2fbe1f1a01451a9f198273c8750 http/exposures/configs/exposed-bitkeeper.yaml:affc52cec6da2505690d8f3fbd6f03abf63c57f2 @@ -4230,7 +4230,7 @@ http/exposures/files/jetbrains-webservers.yaml:19feb7338c4ac6765ed812e8376abcaff http/exposures/files/joomla-file-listing.yaml:7d8669396f5a5f5b270ce199819347a6c053a69e http/exposures/files/jsapi-ticket-json.yaml:193b0da9ae67a300ecd18bb7509657982ac2c6b7 http/exposures/files/keycloak-json.yaml:8b3602c7b1175908c80a03ea62653238e683cf2d -http/exposures/files/kubernetes-etcd-keys.yaml:728145452764d8b9eb55960644f860725620483f +http/exposures/files/kubernetes-etcd-keys.yaml:ff536872dad612e466187245f7bc8df1c163e428 http/exposures/files/lazy-file.yaml:3a903e5bb495952849ab43a9adaa80b739d628b4 http/exposures/files/npm-anonymous-cli.yaml:e8b376262f39740387b8fd06f672f273545a0376 http/exposures/files/npm-cli-metrics-json.yaml:767c57514625303ae64c34a999ca7fcd136e3d12 @@ -4798,7 +4798,7 @@ http/misconfiguration/installer/mcloud-installer.yaml:833e2575e02b6336777860b535 http/misconfiguration/installer/metaview-explorer-installer.yaml:a54e5ad2e434423e51431bf877865d4cdb68a313 http/misconfiguration/installer/monstra-installer.yaml:686d3a375dea7e0d2bc9e985e32f7d73d2b69625 http/misconfiguration/installer/moodle-installer.yaml:6e7ea90cc61ba9f10eb355dce3b247e24724739f -http/misconfiguration/installer/mosparo-install.yaml:ecbddfcc51a02fa63926c7cc14449d462aea001b +http/misconfiguration/installer/mosparo-install.yaml:8c9e37da428e4cbbd723cf632a1d77fc40aedf9d http/misconfiguration/installer/nagiosxi-installer.yaml:81686704bf3178b0b4d2f02a03bb7560468109be http/misconfiguration/installer/netsparker-enterprise-installer.yaml:09b6cbec03cd639b45aaab2c8f1551c3a8e24d22 http/misconfiguration/installer/nginx-auto-installer.yaml:22043eb59a4cbc9a47c8f88f57037f9cde90811e @@ -7030,7 +7030,7 @@ http/vulnerabilities/other/rockmongo-xss.yaml:fbb4cde62ac1aa4e7bf4f35b1285d01223 http/vulnerabilities/other/rundeck-log4j.yaml:216aaae5c719d06cf8e567575cbe5274508c0c75 http/vulnerabilities/other/sangfor-cphp-rce.yaml:668f391b503e86505a94b4cc16c56e96e4269368 http/vulnerabilities/other/sangfor-download-lfi.yaml:8ebb8672f9395ef82e904f2d116e6bcdb58cfbd1 -http/vulnerabilities/other/sangfor-sysuser-conf.yaml:460633d056b1d04ad40a5318b9b6bf6b1bae77d0 +http/vulnerabilities/other/sangfor-sysuser-conf.yaml:562b73e5bd8fb32440a97354371f88a07b67f04c http/vulnerabilities/other/sanhui-smg-file-read.yaml:29d43a4a4ae20dc3c38cda9617893ca76e95f51e http/vulnerabilities/other/sap-redirect.yaml:089390b8edea4fde0420aeae152686a2e04d6b61 http/vulnerabilities/other/sar2html-rce.yaml:2f66f96ef3b9a6a18e82df1a5107f6f36134dd1c @@ -7445,7 +7445,7 @@ http/vulnerabilities/zyxel/unauth-ztp-ping.yaml:fe9fe6bf3d7f27b2f5297126714f53c3 http/vulnerabilities/zzzcms/zzzcms-info-disclosure.yaml:daa2040c8238fbe51311e7ac80eca48e3eb64691 http/vulnerabilities/zzzcms/zzzcms-ssrf.yaml:539291160ef312c1e5f1124b7f525ec6a9743696 http/vulnerabilities/zzzcms/zzzcms-xss.yaml:964a23c1b692ca2c29f6b9824b1608b2999f0922 -javascript/cves/2016/CVE-2016-8706.yaml:37dd114b55b9cc9f3f40dd25ec3e51a1be3ec717 +javascript/cves/2016/CVE-2016-8706.yaml:ce8006d11983dbeb5a00f31029fd096e423fa473 javascript/cves/2023/CVE-2023-34039.yaml:486be9f1b47681310f24989c0f92b1b0b9ba6134 javascript/default-logins/mssql-default-logins.yaml:675c23f13ed6ff177b6860b740d2a0be0968d160 javascript/default-logins/postgres-default-logins.yaml:1b6c296970fc3d5ce9bc78ab7c6f2eda860e5eba @@ -7622,7 +7622,7 @@ ssl/tls-version.yaml:07fa612fd325ec70b698e4a4e1c0d6e7a5a399bc ssl/untrusted-root-certificate.yaml:867f13cbcd5d5a3d8e1c25051b362bd33063d471 ssl/weak-cipher-suites.yaml:62fe808d9dfafda67c410e6cb9445fdc70257e89 ssl/wildcard-tls.yaml:eac3197b9e6ec0342dff2ef774c6785c852868b4 -templates-checksum.txt:a294c8a66add23eecf75ce0194474be0d183e8cb +templates-checksum.txt:8628645677ebb41f2fa7ddea10b2dcf39079c547 wappalyzer-mapping.yml:7f03bd65baacac20c1dc6bbf35ff2407959574f1 workflows/74cms-workflow.yaml:bb010e767ad32b906153e36ea618be545b4e22d0 workflows/acrolinx-workflow.yaml:8434089bb55dec3d7b2ebc6a6f340e73382dd0c4