{"vulnerability": "CVE-2022-3265", "sightings": [{"uuid": "44c5e101-7ec0-471c-9433-be60eb54bd8b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32655", "type": "published-proof-of-concept", "source": "https://t.me/ETHICALHACKERSCOMMUNITY2/2706", "content": "STEP2: Pick the attack module you wish      1) Frames detected at the moment of connectivity disruption, one-by-one\n    2) Sequence of frames till the moment a disruption was detected (BETA)\n  STEP3: The first mode of DoS802.11, tests all the frames that the fuzzer detected up to that moment. It is a second hand filtering to separate the true positive from the false positive frames. In case  a frame is positive, i.e., causes a DoS to the associated STA, an exploit is being produced automatically.\n  STEP4: DoS802.11 exits when the log files have been considered.  **The rest to modules are currently in BETA mode.  Vulnerabilities  So far, the fuzzer managed to identify the following CVE IDs, by exploiting different Management frames:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2022-32654 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32654)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32655 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32655)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32656 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32656)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32657 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32657)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32658 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32658)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32659 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32659)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986/mt8518s/mt8532  Both  Published  6.7 (Medium)      CVE-2022-46740 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-46740)  WS7100-20  Both  Published  6.5 (Medium)      We would like also to thank the MediaTek and Huawei security teams, for acknowledging and fixing these security issues, as stated in the following two security advisories: MediaTek (https://corp.mediatek.com/product-security-acknowledgements) and Huawei (https://www.huawei.com/en/psirt/security-advisories/2022/huawei-sa-dosvihswr-8f632df1-en).  Moreover, by following the methodology of the work titled \"How is your Wi-Fi connection today? DoS attacks on WPA3-SAE\" (https://www.sciencedirect.com/science/article/pii/S221421262100243X), the fuzzer can identify the same SAE vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) which are linked to the below CVE IDs:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2021-37910 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37910)  All ASUS RX-based models  WPA3-SAE  Published  5.3 (medium)      CVE-2021-40288 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40288)  AX10v1  WPA3-SAE  Published  7.5 (high)      CVE-2021-41753 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41753)  DIR-x1560/DIR-X6060  WPA3-SAE  Published  7.5 (high)      CVE-2021-41788 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41788)  mt7603E/mt7612/mt7613\nmt7615/mt7622/mt7628", "creation_timestamp": "2023-07-10T13:19:09.000000Z"}, {"uuid": "1a17dc48-09d7-4b54-be82-b8e262e1095a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32654", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/8973", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-32654\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220705011; Issue ID: GN20220705011.\n\ud83d\udccf Published: 2023-02-06T00:00:00.000Z\n\ud83d\udccf Modified: 2025-03-26T20:05:56.602Z\n\ud83d\udd17 References:\n1. https://corp.mediatek.com/product-security-bulletin/February-2023", "creation_timestamp": "2025-03-26T20:26:08.000000Z"}, {"uuid": "9c389c2f-d70e-40bf-8a0d-609b35833ab0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32658", "type": "published-proof-of-concept", "source": "https://t.me/ETHICALHACKERSCOMMUNITY2/2706", "content": "STEP2: Pick the attack module you wish      1) Frames detected at the moment of connectivity disruption, one-by-one\n    2) Sequence of frames till the moment a disruption was detected (BETA)\n  STEP3: The first mode of DoS802.11, tests all the frames that the fuzzer detected up to that moment. It is a second hand filtering to separate the true positive from the false positive frames. In case  a frame is positive, i.e., causes a DoS to the associated STA, an exploit is being produced automatically.\n  STEP4: DoS802.11 exits when the log files have been considered.  **The rest to modules are currently in BETA mode.  Vulnerabilities  So far, the fuzzer managed to identify the following CVE IDs, by exploiting different Management frames:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2022-32654 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32654)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32655 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32655)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32656 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32656)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32657 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32657)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32658 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32658)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32659 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32659)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986/mt8518s/mt8532  Both  Published  6.7 (Medium)      CVE-2022-46740 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-46740)  WS7100-20  Both  Published  6.5 (Medium)      We would like also to thank the MediaTek and Huawei security teams, for acknowledging and fixing these security issues, as stated in the following two security advisories: MediaTek (https://corp.mediatek.com/product-security-acknowledgements) and Huawei (https://www.huawei.com/en/psirt/security-advisories/2022/huawei-sa-dosvihswr-8f632df1-en).  Moreover, by following the methodology of the work titled \"How is your Wi-Fi connection today? DoS attacks on WPA3-SAE\" (https://www.sciencedirect.com/science/article/pii/S221421262100243X), the fuzzer can identify the same SAE vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) which are linked to the below CVE IDs:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2021-37910 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37910)  All ASUS RX-based models  WPA3-SAE  Published  5.3 (medium)      CVE-2021-40288 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40288)  AX10v1  WPA3-SAE  Published  7.5 (high)      CVE-2021-41753 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41753)  DIR-x1560/DIR-X6060  WPA3-SAE  Published  7.5 (high)      CVE-2021-41788 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41788)  mt7603E/mt7612/mt7613\nmt7615/mt7622/mt7628", "creation_timestamp": "2023-07-10T13:19:09.000000Z"}, {"uuid": "bcf706f0-ef86-44cc-9fbe-08eebcf03c79", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32659", "type": "published-proof-of-concept", "source": "https://t.me/ETHICALHACKERSCOMMUNITY2/2706", "content": "STEP2: Pick the attack module you wish      1) Frames detected at the moment of connectivity disruption, one-by-one\n    2) Sequence of frames till the moment a disruption was detected (BETA)\n  STEP3: The first mode of DoS802.11, tests all the frames that the fuzzer detected up to that moment. It is a second hand filtering to separate the true positive from the false positive frames. In case  a frame is positive, i.e., causes a DoS to the associated STA, an exploit is being produced automatically.\n  STEP4: DoS802.11 exits when the log files have been considered.  **The rest to modules are currently in BETA mode.  Vulnerabilities  So far, the fuzzer managed to identify the following CVE IDs, by exploiting different Management frames:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2022-32654 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32654)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32655 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32655)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32656 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32656)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32657 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32657)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32658 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32658)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32659 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32659)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986/mt8518s/mt8532  Both  Published  6.7 (Medium)      CVE-2022-46740 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-46740)  WS7100-20  Both  Published  6.5 (Medium)      We would like also to thank the MediaTek and Huawei security teams, for acknowledging and fixing these security issues, as stated in the following two security advisories: MediaTek (https://corp.mediatek.com/product-security-acknowledgements) and Huawei (https://www.huawei.com/en/psirt/security-advisories/2022/huawei-sa-dosvihswr-8f632df1-en).  Moreover, by following the methodology of the work titled \"How is your Wi-Fi connection today? DoS attacks on WPA3-SAE\" (https://www.sciencedirect.com/science/article/pii/S221421262100243X), the fuzzer can identify the same SAE vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) which are linked to the below CVE IDs:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2021-37910 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37910)  All ASUS RX-based models  WPA3-SAE  Published  5.3 (medium)      CVE-2021-40288 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40288)  AX10v1  WPA3-SAE  Published  7.5 (high)      CVE-2021-41753 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41753)  DIR-x1560/DIR-X6060  WPA3-SAE  Published  7.5 (high)      CVE-2021-41788 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41788)  mt7603E/mt7612/mt7613\nmt7615/mt7622/mt7628", "creation_timestamp": "2023-07-10T13:19:09.000000Z"}, {"uuid": "ea92c80b-e2bb-45ce-a29f-e2e0e29031e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32657", "type": "published-proof-of-concept", "source": "https://t.me/ETHICALHACKERSCOMMUNITY2/2706", "content": "STEP2: Pick the attack module you wish      1) Frames detected at the moment of connectivity disruption, one-by-one\n    2) Sequence of frames till the moment a disruption was detected (BETA)\n  STEP3: The first mode of DoS802.11, tests all the frames that the fuzzer detected up to that moment. It is a second hand filtering to separate the true positive from the false positive frames. In case  a frame is positive, i.e., causes a DoS to the associated STA, an exploit is being produced automatically.\n  STEP4: DoS802.11 exits when the log files have been considered.  **The rest to modules are currently in BETA mode.  Vulnerabilities  So far, the fuzzer managed to identify the following CVE IDs, by exploiting different Management frames:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2022-32654 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32654)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32655 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32655)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32656 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32656)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32657 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32657)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32658 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32658)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32659 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32659)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986/mt8518s/mt8532  Both  Published  6.7 (Medium)      CVE-2022-46740 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-46740)  WS7100-20  Both  Published  6.5 (Medium)      We would like also to thank the MediaTek and Huawei security teams, for acknowledging and fixing these security issues, as stated in the following two security advisories: MediaTek (https://corp.mediatek.com/product-security-acknowledgements) and Huawei (https://www.huawei.com/en/psirt/security-advisories/2022/huawei-sa-dosvihswr-8f632df1-en).  Moreover, by following the methodology of the work titled \"How is your Wi-Fi connection today? DoS attacks on WPA3-SAE\" (https://www.sciencedirect.com/science/article/pii/S221421262100243X), the fuzzer can identify the same SAE vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) which are linked to the below CVE IDs:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2021-37910 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37910)  All ASUS RX-based models  WPA3-SAE  Published  5.3 (medium)      CVE-2021-40288 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40288)  AX10v1  WPA3-SAE  Published  7.5 (high)      CVE-2021-41753 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41753)  DIR-x1560/DIR-X6060  WPA3-SAE  Published  7.5 (high)      CVE-2021-41788 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41788)  mt7603E/mt7612/mt7613\nmt7615/mt7622/mt7628", "creation_timestamp": "2023-07-10T13:19:09.000000Z"}, {"uuid": "f217a7ba-0514-4986-856f-d14c7b618ed2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32654", "type": "published-proof-of-concept", "source": "https://t.me/ETHICALHACKERSCOMMUNITY2/2706", "content": "STEP2: Pick the attack module you wish      1) Frames detected at the moment of connectivity disruption, one-by-one\n    2) Sequence of frames till the moment a disruption was detected (BETA)\n  STEP3: The first mode of DoS802.11, tests all the frames that the fuzzer detected up to that moment. It is a second hand filtering to separate the true positive from the false positive frames. In case  a frame is positive, i.e., causes a DoS to the associated STA, an exploit is being produced automatically.\n  STEP4: DoS802.11 exits when the log files have been considered.  **The rest to modules are currently in BETA mode.  Vulnerabilities  So far, the fuzzer managed to identify the following CVE IDs, by exploiting different Management frames:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2022-32654 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32654)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32655 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32655)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32656 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32656)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32657 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32657)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32658 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32658)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32659 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32659)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986/mt8518s/mt8532  Both  Published  6.7 (Medium)      CVE-2022-46740 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-46740)  WS7100-20  Both  Published  6.5 (Medium)      We would like also to thank the MediaTek and Huawei security teams, for acknowledging and fixing these security issues, as stated in the following two security advisories: MediaTek (https://corp.mediatek.com/product-security-acknowledgements) and Huawei (https://www.huawei.com/en/psirt/security-advisories/2022/huawei-sa-dosvihswr-8f632df1-en).  Moreover, by following the methodology of the work titled \"How is your Wi-Fi connection today? DoS attacks on WPA3-SAE\" (https://www.sciencedirect.com/science/article/pii/S221421262100243X), the fuzzer can identify the same SAE vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) which are linked to the below CVE IDs:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2021-37910 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37910)  All ASUS RX-based models  WPA3-SAE  Published  5.3 (medium)      CVE-2021-40288 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40288)  AX10v1  WPA3-SAE  Published  7.5 (high)      CVE-2021-41753 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41753)  DIR-x1560/DIR-X6060  WPA3-SAE  Published  7.5 (high)      CVE-2021-41788 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41788)  mt7603E/mt7612/mt7613\nmt7615/mt7622/mt7628", "creation_timestamp": "2023-07-10T13:19:09.000000Z"}, {"uuid": "3e192754-93a0-4cf9-9937-b05ba7f686c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32656", "type": "published-proof-of-concept", "source": "https://t.me/ETHICALHACKERSCOMMUNITY2/2706", "content": "STEP2: Pick the attack module you wish      1) Frames detected at the moment of connectivity disruption, one-by-one\n    2) Sequence of frames till the moment a disruption was detected (BETA)\n  STEP3: The first mode of DoS802.11, tests all the frames that the fuzzer detected up to that moment. It is a second hand filtering to separate the true positive from the false positive frames. In case  a frame is positive, i.e., causes a DoS to the associated STA, an exploit is being produced automatically.\n  STEP4: DoS802.11 exits when the log files have been considered.  **The rest to modules are currently in BETA mode.  Vulnerabilities  So far, the fuzzer managed to identify the following CVE IDs, by exploiting different Management frames:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2022-32654 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32654)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32655 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32655)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32656 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32656)  mt5221/mt7603/mt7613\nmt7615/mt7622/mt7628\nmt7629/mt7663/mt7668\nmt7682/mt7686/mt7687\nmt7697/mt7902/mt7915\nmt7916/mt7921/mt7933\nmt7981/mt7986/mt8167S\nmt8175/mt8362A/mt8365\nmt8385/mt8518S/mt8532\nmt8695/mt8696/mt8788  Both  Published  6.7 (Medium)      CVE-2022-32657 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32657)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32658 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32658)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986  Both  Published  6.7 (Medium)      CVE-2022-32659 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32659)  mt7603/mt7613/mt7615\nmt7622/mt7628/mt7629\nmt7915/mt7916/mt7981\nmt7986/mt8518s/mt8532  Both  Published  6.7 (Medium)      CVE-2022-46740 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-46740)  WS7100-20  Both  Published  6.5 (Medium)      We would like also to thank the MediaTek and Huawei security teams, for acknowledging and fixing these security issues, as stated in the following two security advisories: MediaTek (https://corp.mediatek.com/product-security-acknowledgements) and Huawei (https://www.huawei.com/en/psirt/security-advisories/2022/huawei-sa-dosvihswr-8f632df1-en).  Moreover, by following the methodology of the work titled \"How is your Wi-Fi connection today? DoS attacks on WPA3-SAE\" (https://www.sciencedirect.com/science/article/pii/S221421262100243X), the fuzzer can identify the same SAE vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) which are linked to the below CVE IDs:      CVE IDs  Vulnerable Devices/Chipsets  WPA2/WPA3-SAE  Status  Score      CVE-2021-37910 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37910)  All ASUS RX-based models  WPA3-SAE  Published  5.3 (medium)      CVE-2021-40288 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-40288)  AX10v1  WPA3-SAE  Published  7.5 (high)      CVE-2021-41753 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41753)  DIR-x1560/DIR-X6060  WPA3-SAE  Published  7.5 (high)      CVE-2021-41788 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41788)  mt7603E/mt7612/mt7613\nmt7615/mt7622/mt7628", "creation_timestamp": "2023-07-10T13:19:09.000000Z"}, {"uuid": "94f605e9-9e5f-4db8-9613-ae39e478e635", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32659", "type": "seen", "source": "https://t.me/cibsecurity/55825", "content": "\u203c CVE-2022-32659 \u203c\n\nIn Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220705066; Issue ID: GN20220705066.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-04T00:17:28.000000Z"}, {"uuid": "78074c6c-d8e1-408d-b535-9cac8376b972", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32656", "type": "seen", "source": "https://t.me/cibsecurity/57591", "content": "\u203c CVE-2022-32656 \u203c\n\nIn Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220705035; Issue ID: GN20220705035.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-02-06T22:23:47.000000Z"}, {"uuid": "78c6fe6f-d317-4279-ae77-822c3c49d16d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32655", "type": "seen", "source": "https://t.me/cibsecurity/57610", "content": "\u203c CVE-2022-32655 \u203c\n\nIn Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220705028; Issue ID: GN20220705028.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-02-06T22:29:50.000000Z"}, {"uuid": "75029425-fa4c-41ce-83b9-352f3170a33c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32658", "type": "seen", "source": "https://t.me/cibsecurity/55824", "content": "\u203c CVE-2022-32658 \u203c\n\nIn Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220705059; Issue ID: GN20220705059.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-04T00:17:27.000000Z"}, {"uuid": "79b7a161-a6af-4793-bd3b-3d454c18be5c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32652", "type": "seen", "source": "https://t.me/cibsecurity/55837", "content": "\u203c CVE-2022-32652 \u203c\n\nIn mtk-aie, there is a possible use after free due to a logic error. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07262617; Issue ID: ALPS07262617.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-04T00:17:45.000000Z"}, {"uuid": "240f1661-1f17-4b1a-a048-9db12dffbb09", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32653", "type": "seen", "source": "https://t.me/cibsecurity/55836", "content": "\u203c CVE-2022-32653 \u203c\n\nIn mtk-aie, there is a possible use after free due to a logic error. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07262518; Issue ID: ALPS07262518.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-04T00:17:45.000000Z"}, {"uuid": "85d895c7-c2f2-4066-940d-982e1fc53357", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32650", "type": "seen", "source": "https://t.me/cibsecurity/55831", "content": "\u203c CVE-2022-32650 \u203c\n\nIn mtk-isp, there is a possible use after free due to a logic error. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07225853; Issue ID: ALPS07225853.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-04T00:17:37.000000Z"}, {"uuid": "2988ed2c-502c-4e18-999b-32a84f928904", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32657", "type": "seen", "source": "https://t.me/cibsecurity/55829", "content": "\u203c CVE-2022-32657 \u203c\n\nIn Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220705042; Issue ID: GN20220705042.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-04T00:17:35.000000Z"}, {"uuid": "c542bcf6-76a4-48f7-a799-2775e5621940", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-32651", "type": "seen", "source": "https://t.me/cibsecurity/55828", "content": "\u203c CVE-2022-32651 \u203c\n\nIn mtk-aie, there is a possible use after free due to a logic error. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07225857; Issue ID: ALPS07225857.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-01-04T00:17:31.000000Z"}, {"uuid": "b5a2736c-6dfb-4592-92cd-f91238bb102a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-3265", "type": "seen", "source": "https://t.me/cibsecurity/52805", "content": "\u203c CVE-2022-3265 \u203c\n\nA cross-site scripting issue has been discovered in GitLab CE/EE affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2. It was possible to exploit a vulnerability in setting the labels colour feature which could lead to a stored XSS that allowed attackers to perform arbitrary actions on behalf of victims at client side.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-11-10T02:49:59.000000Z"}]}