{"vulnerability": "cve-2022-44563", "sightings": [{"uuid": "e66d51cf-ea77-4ea7-84d9-693301168104", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-44563", "type": "published-proof-of-concept", "source": "Telegram/f_V5WAw89TJE3mX7iA0X18pm5lwQ8AySxeot_kMKmTKhRCw", "content": "", "creation_timestamp": "2023-02-19T21:50:11.000000Z"}, {"uuid": "0df6d97b-056b-4bef-9844-1e99e97dbf39", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-44563", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/7775", "content": "#exploit\n1. Proxylogon & Proxyshell & Proxyoracle & Proxytoken & ALL Exchange Server Vulns Summarization\nhttps://github.com/FDlucifer/Proxy-Attackchain\n\n2. CVE-2022-44563:\nHuawei Recovery Update Zip ToC-ToU Vulnerability\nhttps://labs.taszk.io/articles/post/reunzip", "creation_timestamp": "2023-02-18T13:07:01.000000Z"}, {"uuid": "741e027a-826e-4369-af74-c3bba8ac9eb2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-44563", "type": "published-proof-of-concept", "source": "Telegram/jxixKB1GGbK3q7ZKTf-z1SAMg-aPMfOcd1311YRna1Tccdk", "content": "", "creation_timestamp": "2023-02-21T13:05:46.000000Z"}, {"uuid": "d069ca5a-a525-45fb-8aa0-3b0922766389", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-44563", "type": "published-proof-of-concept", "source": "https://t.me/crackcodes/2638", "content": "\ud83d\udd25\ud83d\udd25\ud83d\udd25REUnziP: Re-Exploiting Huawei Recovery With FaultyUSB(CVE-2022-44563, Toc-ToU race condition vuln can be exploited to achieve arbitrary code execution )\nThis is a new vulnerability in a proprietary mode called \u201cSD-Update\u201d, which can once again be used to achieve arbitrary code execution in the recovery mode, enabling unauthentic firmware updates, firmware downgrades to a known vulnerable version or other system modifications. Taszk advisory for the vulnerability is published here. The story of exploiting this vulnerability was made interesting by the fact that, since the exploit abuses wrong assumptions about the behavior of an external SD card, we needed some hardware-fu to actually be able to trigger it. In this blog post, Lorant Szabo describe how we went about creating \u201cFaultyUSB\u201d - a custom Raspberry Pi based setup that emulates a maliciously behaving USB flash drive - and exploiting this vulnerability to achieve arbitrary code execution as root!", "creation_timestamp": "2023-02-22T17:25:48.000000Z"}]}