{"uuid": "5eaf7eb7-06eb-4928-9175-8b9ae761313d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-37852", "type": "seen", "source": "https://t.me/hacking_Attack/41284", "content": "Black Hat Ethical Hacking\nESET antivirus bug let attackers gain Windows SYSTEM privileges\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png ESET antivirus bug let attackers gain Windows SYSTEM privilegesPost Views: 188 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute\nThe flaw (CVE-2021-37852) was reported by Michael DePlante of Trend Micro\u2019s Zero Day Initiative, and it enables attackers to escalate privileges to NT AUTHORITY\\SYSTEM account rights (the highest level of privileges on a Windows system) using the Windows Antimalware Scan Interface (AMSI).\nSlovak internet security firm ESET released security fixes to address a high severity local privilege escalation vulnerability affecting multiple products on systems running Windows 10 and later or Windows Server 2016 and above. AMSI\u00a0was first introduced with Windows 10 Technical Preview in 2015, and it allows apps and services to request memory buffer scans from any major antivirus product installed on the system. According to ESET, this can only be achieved after attackers gain SeImpersonatePrivilege rights, normally assigned to users in the local Administrators group and the device\u2019s local Service account to impersonate a client after authentication which should \u201climit the impact of this vulnerability.\u201d\n\nHowever, ZDI\u2019s advisory\u00a0says attackers are only required to \u201cobtain the ability to execute low-privileged code on the target system,\u201d which matches ESET\u2019s CVSS severity rating\u00a0also showing that\u00a0the bug can be exploited by threat actors with low privileges.\n\nWhile ESET said it only found out about this bug on November 18, a disclosure timeline available in ZDI\u2019s advisory reveals that the vulnerability was reported four months earlier, on June 18, 2021.\nSee Also: Complete Offensive Security and Ethical Hacking Course Affected ESET productsThe list of products impacted by this vulnerability is quite long, and it includes:\n\n* ESET NOD32 Antivirus, ESET Internet Security, ESET Smart Security, and ESET Smart Security Premium from version 10.0.337.1 to 15.0.18.0\n* ESET Endpoint Antivirus for Windows and ESET Endpoint Security for Windows from version 6.6.2046.0 to 9.0.2032.4\n* ESET Server Security for Microsoft Windows Server 8.0.12003.0 and 8.0.12003.1, ESET File Security for Microsoft Windows Server from version 7.0.12014.0 to 7.3.12006.0\n* ESET Server Security for Microsoft Azure from version 7.0.12016.1002 to 7.2.12004.1000\n* ESET Security for Microsoft SharePoint Server from version 7.0.15008.0 to 8.0.15004.0\n* ESET Mail Security for IBM Domino from version 7.0.14008.0 to 8.0.14004.0\n* ESET Mail Security for Microsoft Exchange Server from version 7.0.10019 to 8.0.10016.0\nSee Also: Windows vulnerability with new public exploits lets you become admin Users of ESET Server Security for Microsoft Azure are also advised\u00a0to immediately update ESET File Security for Microsoft Azure to the latest available version of ESET Server Security for Microsoft Windows Server to address the flaw.\n\nThe antivirus maker released multiple security updates between December 8 and January 31\u00a0to address this vulnerability, when it patched the last vulnerable product exposed to attacks.\n\nLuckily, ESET\u00a0found no evidence of exploits designed to target products affected by this security bug in the wild.\n\n\u201cThe attack surface can also be eliminated by disabling the Enable advanced scanning via AMSI option in ESET products\u2019 Advanced setup,\u201d ESET added.\n\n\u201cHowever, ESET strongly recommends performing an upgrade to a fixed product version and only applying this workaround when the upgrade is not possible[...]", "creation_timestamp": "2026-09-01T20:01:57.352752Z"}