{"uuid": "d5616cfe-5a91-4860-b29a-ca27a22c8ae4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-28482", "type": "seen", "source": "https://t.me/hacking_Attack/4998", "content": "Black Hat Ethical Hacking\nMicrosoft to Patch multiple Zero-Days, 110 vulnerabilities in total\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Microsoft to Patch multiple Zero-Days, 110 vulnerabilities in totalPost Views: 94 \nReading Time: 1 Minute\nMicrosoft had its hands full Tuesday snuffing out five zero-day vulnerabilities, a flaw under active attack and applying more patches to its problem-plagued Microsoft Exchange Server software.\nIn all, Microsoft released patches for 110 security holes, 19 classified critical in severity and 88 considered important. The most dire of those flaws disclosed is arguably a Win32k elevation of privilege vulnerability (CVE-2021-28310) actively being exploited in the wild by the cybercriminal group BITTER APT. Actively Exploited Zero-Day\u201cWe believe this exploit is used in the wild, potentially by several threat actors. It is an escalation of privilege (EoP) exploit that is likely used together with other browser exploits to escape sandboxes or get system privileges for further access,\u201d wrote Kaspersky in a Tuesday report\u00a0detailing its find.\n\nThe bug is an out-of-bounds write vulnerability in Windows dwmcore.dll library, which is part of Desktop Window Manager (dwm.exe). \u201cDue to the lack of bounds checking, attackers are able to create a situation that allows them to write controlled data at a controlled offset using DirectComposition API,\u201d wrote Kaspersky researchers Boris Larin, Costin Raiu and Brian Bartholomew, co-authors of the report.\nSee Also: Chrome Zero-Day Exploit Posted on Twitter More Bugs Tied to Plagued ExchangeOf note, the U.S. National Security Agency released information on four critical Exchange Server vulnerabilities \u00a0(CVE-2021-28480, CVE-2021-28481, CVE-2021-28482, CVE-2021-28483) impacting versions released between 2013 and 2019.\n\n\u201cThese vulnerabilities have been rated \u2018exploitation more likely\u2019 using Microsoft\u2019s Exploitability Index. Two of the four vulnerabilities (CVE-2021-28480, CVE-2021-28481) are pre-authentication, meaning an attacker does not need to authenticate to the vulnerable Exchange server to exploit the flaw. With the intense interest in Exchange Server since last month, it is crucial that organizations apply these Exchange Server patches immediately,\u201d wrote Satnam Narang, staff research engineer with Tenable in commentary shared with Threatpost.\n\nMicrosoft notes that two of the four Exchange bugs reported by the NSA were also found internally by its own research team.\nSee Also: Offensive Security Tool: CVE Binary Tool by Intel https://media.threatpost.com/wp-content/uploads/sites/103/2020/09/25150114/Bug-Bounty-Code_small-300x198.jpg Bugs, Bugs and More BugsMicrosoft also included patches for its Chromium-based Edge web browser, Azure and Azure DevOps Server, Microsoft Office, SharePoint Server, Hyper-V, Team Foundation Server and Visual Studio.\n\n\u201cApril\u2019s Patch Tuesday yields\u2026 [are] the highest monthly total for 2021 (so far) and showing a return to the 100-plus totals we consistently saw in 2020,\u201d wrote Justin Knapp, senior product marketing manager with Automox, in a prepared analysis shared with Threatpost. \u201cThis month\u2019s haul includes 19 critical vulnerabilities and a high-severity zero-day that is actively being exploited in the wild.\u201d\n\nHe added, \u201cWe\u2019re also seeing multiple browser-related vulnerabilities this month that should be addressed immediately. This represents an overall upward trend that\u2019s expected to continue throughout the year and draw greater urgency around patching velocity, to ensure organizations are not taking on unnecessary exposure \u2014 especially given the increased exploitation of[...]", "creation_timestamp": "2026-09-01T20:02:46.713370Z"}