{"uuid": "94ecfe5c-8b34-4216-bd7d-6d0c13e1a7f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-21990", "type": "seen", "source": "https://t.me/hacking_Attack/45623", "content": "nerability affecting on-prem Exchange servers could potentially be used during lateral movement into a part of the environment which presents the opportunity for business email compromise or data theft from email,\u201d he said via email.\n\nClaire Tillis, senior research engineer at Tenable, meanwhile told Threatpost: \u201d Given the prevalence of attacks against Microsoft Exchange flaws in the past, organizations should apply the available updates immediately.\u201d Publicly Known BugsMeanwhile, the three zero-day issues are:\n\n* CVE-2022-21990\u00a0\u2013 Remote Desktop Client (CVSS rating of 8.8, allows RCE)\n* CVE-2022-24512\u00a0\u2013 .NET and Visual Studio (CVSS rating of 6.3, allows RCE)\n* CVE-2022-24459\u00a0\u2013 Windows Fax and Scan Service (CVSS rating of 7.8, allows elevation of privilege)\n\nThe RDP client issue deserves to be treated as though it was designated critical, Childs said.\n\n\u201cThis client-side bug doesn\u2019t have the same punch as server-side-related RDP, but since it\u2019s listed as publicly known, it makes sense to treat this as a critical-rated bug,\u201d he said. \u201cThis isn\u2019t as severe as BlueKeep or some of the other RDP server bugs, but it definitely shouldn\u2019t be overlooked.\u201d\n\nWith regards to attack vector, a threat actor would need to lure an affected RDP client to connect to a malicious RDP server, which would allow the person to trigger code execution on the targeted client, Childs explained.\n\nBreen pointed out that the bug is one of three RCE bugs affecting RDP included in the advisory; the other two are CVE-2022-23285\u00a0(CVSS 8.8) and CVE-2022-24503\u00a0(CVSS 5.4).\n\n\u201cWith the increase in remote working driving the expansion of the attack surface presented by RDP, a trio of RCE vulnerabilities affecting this protocol should be on security teams\u2019 radar,\u201d Breen said via email. \u201c[They] are a potential concern especially as this infection vector is commonly used by ransomware actors. While exploitation is not trivial, requiring an attacker to set up bespoke infrastructure, it still presents enough of a risk to be a priority.\u201d\n\nThe second known RCE bug is much less of a concern, according to Microsoft\u2019s advisory.\n\n\u201cWhile we cannot rule out the impact to confidentiality, integrity and availability, the ability to exploit this vulnerability by itself is limited,\u201d according to the company. \u201cAn attacker would need to combine this with other vulnerabilities to perform an attack.\u201d\n\nPlus, a targeted user would need to be lured to trigger a payload within the application.\n\nMicrosoft offered no technical details about the third publicly known bug. See Also: Offensive Security Tool: Scapy Other March Vulnerabilities of InterestResearchers flagged a handful of other issues to patch quickly, including CVE-2022-24508, which exists in the Windows SMBv3 client and server, and which could lead to RCE on Windows 10 version 2004 and newer systems.\n\n\u201cAuthentication is required here, but since this affected both clients and servers, an attacker could use this for lateral movement within a network,\u201d Childs explained. \u201cThis is another one I would treat as critical and mitigate quickly.\u201d\n\nBreen again agreed, and noted that Microsoft offered additional mitigations.\n\n\u201cAnother potential component of lateral movement, remotely executable CVE-2022-24508 in Windows SMB v3, seems to be one to watch out for,\u201d he said. \u201cWhile successful exploitation requires valid credentials, Microsoft provides advice on limiting SMB traffic in lateral and external connections. While this is a strong step in providing defense in depth, blocking such connections can also have an adverse effect on other tools using these connections, something to be considered in mitigation attempts.\u201d\n\nHe also flagged three privilege-escalation vulnerabilities (CVE-2022-23286\u00a0in the Windows Cloud Files Mini Filter Driver; CVE-2022-24507\u00a0in the Windows Ancillary Function Driver for WinSock; and CVE-2022-23299\u00a0in Windows PDEV) as ones to prioritize, since they \u201cc[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:01:52.292521Z"}