{"vulnerability": "cve-2021-40487", "sightings": [{"uuid": "52225441-9f7f-4bae-bb19-7d1d0f929c7d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-40487", "type": "seen", "source": "https://t.me/true_secator/2209", "content": "Mayday! Mayday! \u0438\u0437 \u0420\u0435\u0434\u043c\u043e\u043d\u0434\u0430, \u0448\u0442\u0430\u0442\u0430 \u0412\u0430\u0448\u0438\u043d\u0433\u0442\u043e\u043d.\n \n\u041f\u043e\u0434\u044a\u0435\u0445\u0430\u043b \u0432\u0430\u0433\u043e\u043d \u0438 \u043c\u0430\u043b\u0435\u043d\u044c\u043a\u0430\u044f \u0442\u0435\u043b\u0435\u0436\u043a\u0430 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u043e\u0442 Microsoft \u0441 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f\u043c\u0438 \u043a\u0430\u043a \u043c\u0438\u043d\u0438\u043c\u0443\u043c 71 \u043e\u0448\u0438\u0431\u043a\u0438 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0432 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430\u0445 \u0438 \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u0430\u0445 Windows. \u041d\u043e \u0432\u0438\u0448\u0435\u043d\u043a\u043e\u0439 \u043d\u0430 \u0442\u043e\u0440\u0442\u0435 \u0441\u0442\u0430\u043b\u043e \u0441\u0440\u043e\u0447\u043d\u043e\u0435 \u043f\u0440\u0435\u0434\u0443\u043f\u0440\u0435\u0436\u0434\u0435\u043d\u0438\u0435 \u043e \u0432\u044b\u044f\u0432\u043b\u0435\u043d\u043d\u044b\u0445 \u0444\u0430\u043a\u0442\u0430\u0445 \u043a\u0438\u0431\u0435\u0440\u0448\u043f\u0438\u043e\u043d\u0430\u0436\u0430 \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c 0-day \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439:\n \n- CVE-2021-40449 (CVSS: 7,8) - \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c Win32k, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u0430\u044f \u0441 \u043f\u043e\u0432\u044b\u0448\u0435\u043d\u0438\u0435\u043c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0439.\n- CVE-2021-41335 (CVSS: 7,8) - \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u044f\u0434\u0440\u0430 Windows, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u0430\u044f \u0441 \u043f\u043e\u0432\u044b\u0448\u0435\u043d\u0438\u0435\u043c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0439.\n- CVE-2021-40469 (CVSS: 7,2) - \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c Windows DNS Server, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u0430\u044f \u0441 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u044b\u043c \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435\u043c \u043a\u043e\u0434\u0430.\n- CVE-2021-41338 (CVSS: 5,5) - \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u0430\u044f \u0441 \u043e\u0431\u0445\u043e\u0434\u043e\u043c \u0444\u0443\u043d\u043a\u0446\u0438\u0439 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0432 \u043f\u0440\u0430\u0432\u0438\u043b\u0430\u0445 \u0431\u0440\u0430\u043d\u0434\u043c\u0430\u0443\u044d\u0440\u0430 Windows AppContainer.\n \n\u041f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u043d\u043e\u0433\u043e \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f, \u043f\u043e\u0434\u0442\u0432\u0435\u0440\u0434\u0438\u043b \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044e CVE-2021-40449 \u0432 \u0446\u0435\u043f\u043e\u0447\u043a\u0435 \u044d\u043a\u0441\u043f\u043b\u043e\u0439\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0431\u044b\u043b\u0430 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0430 \u0441\u043e\u043e\u0442\u0435\u0447\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u0438\u043a\u0430\u043c\u0438 \u0438\u0437 Kaspersky. \u0418\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u043f\u0440\u044f\u043c\u043e \u043d\u0435 \u0437\u0430\u0432\u0435\u0440\u0438\u043b\u0438 \u0438 \u0441\u043e\u043e\u0431\u0449\u0438\u043b\u0438, \u0447\u0442\u043e \u0432\u0441\u0435 \u0443\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043d\u0430 \u0442\u043e, \u0447\u0442\u043e, \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043b\u0430\u0441\u044c APT IronHusky \u0438\u0437 \u041f\u043e\u0434\u043d\u0435\u0431\u0435\u0441\u043d\u043e\u0439, \u043d\u0430\u0446\u0435\u043b\u0435\u043d\u043d\u043e\u0439 \u043d\u0430 \u0418\u0422-\u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438, \u0434\u0438\u043f\u043b\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u0443\u0447\u0440\u0435\u0436\u0434\u0435\u043d\u0438\u044f, \u0430 \u0442\u0430\u043a\u0436\u0435 \u0432\u043e\u0435\u043d\u043d\u044b\u0435 \u0438 \u043e\u0431\u043e\u0440\u043e\u043d\u043d\u044b\u0435 \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f. \u0412 \u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u043e\u043c \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0438 \u0433\u043e\u0432\u043e\u0440\u0438\u0442\u0441\u044f, \u0447\u0442\u043e \u0446\u0435\u043f\u043e\u0447\u043a\u0438 \u0437\u0430\u0440\u0430\u0436\u0435\u043d\u0438\u044f \u043f\u0440\u0438\u0432\u043e\u0434\u044f\u0442 \u043a \u0440\u0430\u0437\u0432\u0435\u0440\u0442\u044b\u0432\u0430\u043d\u0438\u044e \u0442\u0440\u043e\u044f\u043d\u0430 \u0434\u043b\u044f \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0434\u043e\u0441\u0442\u0443\u043f\u0430, \u0441\u043f\u043e\u0441\u043e\u0431\u043d\u043e\u0433\u043e \u0441\u043e\u0431\u0438\u0440\u0430\u0442\u044c \u0438 \u0444\u0438\u043b\u044c\u0442\u0440\u043e\u0432\u0430\u0442\u044c \u0441\u0438\u0441\u0442\u0435\u043c\u043d\u0443\u044e \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u0438\u0437 \u0441\u043a\u043e\u043c\u043f\u0440\u043e\u043c\u0435\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0445 \u0445\u043e\u0441\u0442\u043e\u0432, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043e\u0431\u0440\u0430\u0449\u0430\u0442\u044c\u0441\u044f \u043a \u0441\u0432\u043e\u0435\u043c\u0443 \u0441\u0435\u0440\u0432\u0435\u0440\u0443 C2 \u0437\u0430 \u0434\u0430\u043b\u044c\u043d\u0435\u0439\u0448\u0438\u043c\u0438 \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u044f\u043c\u0438.\n \n\u0414\u0432\u0435 \u0438\u0437 71 \u0437\u0430\u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0438\u043c\u0435\u044e\u0442 \u043d\u0430\u0438\u0432\u044b\u0441\u0448\u0438\u0439 \u0440\u0435\u0439\u0442\u0438\u043d\u0433 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u043e\u0441\u0442\u0438 \u043f\u043e \u0432\u0435\u0440\u0441\u0438\u0438 Microsoft. \u0414\u0440\u0443\u0433\u0438\u0435 \u043d\u0430\u0438\u0431\u043e\u043b\u0435\u0435 \u043e\u043f\u0430\u0441\u043d\u044b\u0435 \u043e\u0448\u0438\u0431\u043a\u0438 \u0432\u043a\u043b\u044e\u0447\u0430\u044e\u0442 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043a\u043e\u0434\u0430, \u0432\u043b\u0438\u044f\u044e\u0449\u0438\u0435 \u043d\u0430 Microsoft Exchange Server (CVE-2021-26427), Windows Hyper-V (CVE-2021-38672 \u0438 CVE-2021-40461), SharePoint Server (CVE-2021-40487 \u0438 CVE- 2021-41344) \u0438 Microsoft Word (CVE-2021-40486), \u0430 \u0442\u0430\u043a\u0436\u0435 \u043e\u0448\u0438\u0431\u043a\u0430 \u0440\u0430\u0441\u043a\u0440\u044b\u0442\u0438\u044f \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432 Rich Text Edit Control (CVE-2021-40454).\n \n\u0410 CVE-2021-26427 \u0441 \u0440\u0435\u0439\u0442\u0438\u043d\u0433\u043e\u043c CVSS 9,0 \u043f\u0440\u044f\u043c \u043d\u0430\u0441\u0442\u043e\u043b\u044c\u043a\u043e \u0432\u043e\u0448\u043b\u0430 \u0445\u0430\u043a\u0435\u0440\u0430\u043c, \u0447\u0442\u043e \u0437\u0430\u0441\u0443\u0435\u0442\u0438\u043b\u0438\u0441\u044c \u0434\u0430\u0436\u0435 \u0440\u0435\u0431\u044f\u0442\u0430 \u0438\u0437 \u0410\u0433\u0435\u043d\u0442\u0441\u0442\u0432\u0430 \u043d\u0430\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u043e\u0439 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0421\u0428\u0410 (NSA), \u043e\u0441\u043e\u0431\u043e \u043e\u0442\u043c\u0435\u0447\u0430\u044f \u0442\u0440\u0435\u043d\u0434 \u043d\u0430\u0446\u0435\u043b\u0438\u0432\u0430\u043d\u0438\u044f \u0445\u0430\u043a\u0435\u0440\u043e\u0432 \u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u044b\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 Exchange \u0434\u043b\u044f \u0432\u0445\u043e\u0434\u0430 \u0432 \u043f\u0435\u0440\u0438\u043c\u0435\u0442\u0440 \u0441\u0432\u043e\u0438\u0445 \u0436\u0435\u0440\u0442\u0432.\n \nMicrosoft \u0438 \u043f\u0435\u0440\u0435\u0434\u043e\u0432\u043e\u0439 \u0438\u043d\u0444\u043e\u0441\u0435\u043a \u0438\u0441\u0442\u0435\u0431\u043b\u0438\u0448\u043c\u0435\u043d\u0442 \u043f\u0440\u0438\u0437\u044b\u0432\u0430\u044e\u0442 \u043d\u0435\u043c\u0435\u0434\u043b\u0435\u043d\u043d\u043e \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u0438\u0442\u044c \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0434\u0430\u0431\u044b \u0438\u0437\u0431\u0435\u0436\u0430\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u044b\u0445 \u043d\u0435\u0433\u0430\u0442\u0438\u0432\u043d\u044b\u0445 \u043f\u043e\u0441\u043b\u0435\u0434\u0441\u0442\u0432\u0438\u0439. \u041d\u0443, \u0430 \u043c\u044b, \u0432 \u0441\u0432\u043e\u044e \u043e\u0447\u0435\u0440\u0435\u0434\u044c, \u043f\u043e\u0434\u043e\u0436\u0434\u0451\u043c \u0432\u0435\u0441\u0442\u0435\u0439 \u043e\u0442 \u0442\u0435\u0445, \u043a\u0442\u043e \u043d\u0435 \u0443\u0441\u043f\u0435\u043b \u044d\u0442\u043e\u0433\u043e \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0432\u043e\u0432\u0440\u0435\u043c\u044f.", "creation_timestamp": "2021-10-13T15:52:05.000000Z"}, {"uuid": "ac85c72e-75fb-49c1-ac47-4080a5d64515", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-40487", "type": "seen", "source": "https://t.me/cibsecurity/30491", "content": "\u203c CVE-2021-40487 \u203c\n\nMicrosoft SharePoint Server Remote Code Execution Vulnerability This CVE ID is unique from CVE-2021-41344.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-10-13T07:32:41.000000Z"}, {"uuid": "bf5fb06d-b997-47a0-aa07-d17e06feee6d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-40487", "type": "seen", "source": "https://t.me/hacking_Attack/27441", "content": "38, this vulnerability is, again, high severity \u2013 it allows an attacker to bypass the security rules of Windows AppContainer Firewall \u2013 as well as publicly disclosed.\n\nAppContainers are designed to protect against infiltration from third-party apps. They essentially isolate the runtime environment of applications with the goal of blocking malicious code.\n\nThis vulnerability results in loss of confidentiality and can be exploited without any user interaction.\n\nMaarten Buis, Automox product marketing manager, noted that a successful attacker that exploits this vulnerability could run arbitrary code on the endpoint, but they need to have administrative privileges before they can meaningfully exploit it.\n\n\u201cHowever, there is still a significant risk because no user interaction is required, and no special endpoint conditions are required for an attack to succeed,\u201d Buis explained to Threatpost via email .\n\nThere are no reports of the vulnerability having been actively exploited \u2013 yet. Still, Automox recommends a rapid patch rollout \u2013 as in, within 72 hours of the patch being made available \u2013 given that it\u2019s been publicly disclosed in a proof of concept by James Forshaw of Google\u2019s Project Zero.\n\nAleks Haugom, Automox product marketing manager, noted that, given the sheer number of apps users download, \u201cmaking sure that AppContianers cannot be compromised is important to every company\u2019s security hygiene.\u201d\nSee Also: Hacking stories \u2013 Operation Aurora: When China hacked Google How to Prioritize?Williams said that he doesn\u2019t want to sound like a broken record, but he\u2019s still going to say what security experts say every Patch Tuesday. To wit, \u201cPatch now.\u201d\n\nThat\u2019s particularly true for the MysterySnail campaign, he said: \u201cSeriously, this is not a patch Tuesday to delay on,\u201d he advised. \u201cThreat actors are actively exploiting the vulnerability for CVE-2021-40449 to elevate from user to administrator permissions on compromised systems. While CVE-2021-40449 doesn\u2019t allow for remote exploitation, that doesn\u2019t mean it can be taken lightly. Threat actors regularly gain access to target machines using phishing attacks and vulnerabilities such as CVE-2021-40449 allow them to evade more effectively bypass endpoint controls and evade detection.\u201d\n\nBesides which, MysterySnail\u2019s success in weaponizing this flaw means that other APTs will soon follow, Williams said: \u201cBecause the code for this has already been weaponized by one threat actor, we should expect to see it weaponized by others more quickly because there is already sample exploit code in the wild to work with.\u201d\n\nDanny Kim, Principle Architect at Virsec, who spent time at Microsoft during his graduate work on the OS security development team, voted for prioritizing the three critical remote code execution vulnerabilities: CVE-2021-40469, CVE-2021-26427 and CVE-2021-40487, which affect a wide range of Windows versions.\n\n\u201cThese vulnerabilities not only have a high to critical CVSS rating, but two of the three attacks (CVE-2021-40487, CVE-2021-40469) can be executed remotely,\u201d he stressed. \u201cRemote Code Execution (RCE) attacks are especially devastating because once the exploit is executed, [the attackers] can launch any kind of cyberattack, including ransomware.\n\nHe noted that RCE vulnerabilities were also the root cause of the Hafnium and Kaseya attacks. \u201cTrying to mitigate the attacker\u2019s actions after they have gained access is significantly harder than stopping the actions that led to the successful exploit,\u201d Kim pointed out. \u201cThis is why runtime monitoring of enterprises\u2019 server workloads is becoming a key part of today\u2019s cybersecurity. Stopping the exploitation of these vulnerabilities has to start with equipping the servers themselves with constant, deterministic runtime protection, not just detection.\u201d\nSource: threatpost.com (Click Link)Recent News* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/10/apple-iphone-hacking-90[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:13.919621Z"}, {"uuid": "1430e2b1-87d7-4e5a-8aa4-71674d807f51", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-40487", "type": "seen", "source": "https://t.me/hacking_Attack/27439", "content": "g that allowed threat actors to conduct remote code execution (RCE) and to gain local system privileges.\n\nThis month\u2019s release includes a fix for CVE-2021-36970, a spoofing vulnerability in Microsoft\u2019s Windows Print Spooler that has a CVSSv3 score of 8.8.\n\nChris Morgan, senior cyber threat intelligence analyst at Digital Shadows, said that the spoofing vulnerability fix Microsoft put out today is meant to fix the problems that previous patches have introduced.\n\n\u201cWhile Microsoft provided a fix in their September 2021 update,\u00a0the patch resulted in a number of management problems,\u201d he told Threatpost. \u201cCertain printers required users to repeatedly input their administrator credentials every time an application attempted to print or had a client connect to a print server.\n\n\u201cOther problems included event logs recording error messages and denying users the ability to perform basic prints\u201d he continued. \u201cAs a result, many may have likely skipped the update due to its operational impact, ultimately leaving the risk posed by PrintNightmare in place.\u201d\n\nThis vulnerability was discovered by researchers XueFeng Li and Zhiniang Peng of Sangfor, who were also credited with the discovery of CVE-2021-1675, one of two vulnerabilities known as PrintNightmare.\n\nSatnam Narang, staff research engineer at Tenable noted that \u201cWhile no details have been shared publicly about the flaw, this is definitely one to watch for, as we saw a constant stream of Print Spooler-related vulnerabilities patched over the summer while ransomware groups began incorporating PrintNightmare into their affiliate playbook. We strongly encourage organizations to apply these patches as soon as possible.\u201d\nSee Also: Apple Pay with VISA lets hackers force payments on locked iPhones RCE Affects Microsoft Word, Office, SharePointAnother vulnerability worth noting is CVE-2021-40486, a critical RCE affecting Microsoft Word, Microsoft Office and some versions of SharePoint Server that can be exploited via the Preview Pane.\n\nGina Geisel, Automox product and partner marketing professional, noted that this vulnerability isn\u2019t new to Microsoft, with several other similar CVEs documented this year. In this case, the RCE vulnerability exists in some Microsoft apps when they fail to properly handle objects in memory.\n\nWith a low attack complexity, this vulnerability requires a user opening a specially crafted file either by email or via a website, either hosted by the attacker or through a compromised website that accepts or hosts user-provided content.\n\n\u201cAn attacker who successfully exploits this vulnerability can use this file to perform actions in the context of the current user,\u201d Geisel explained. \u201cFor example, the file could take actions on behalf of the logged-on user with the same permissions as the current user.\u201d Microsoft SharePoint Server RCEImmersive Labs\u2019 Breen told Threatpost that this RCE vulnerability \u2013 tracked as CVE-2021-40487\u00a0rated as 8.1 out of 10 CVSS score and marked as \u201cexploitation more likely\u201d \u2013 will be more difficult for an attacker to exploit, given that it requires an authenticated user on the domain.\n\nBut gaining RCE on a SharePoint server \u201copens up a lot of avenues for further exploitation,\u201d he noted via email.\n\n\u201cInternal SharePoint servers are often used to host company-sensitive documents and provide an intranet for staff to interact with,\u201d Breen explained. \u201cIf an attacker could manipulate the content of these articles or replace valid documents with malicious ones, they could steal credentials or trick targeted users into installing additional malware.\u201d Highest CVSS Award Goes to Microsoft Exchange Server RCECVE-2021-26427, the latest in Exchange Server RCEs, takes the severity cake this month, with a CVSS score of 9.0 out of 10. In spite of this hgh severity rating, Microsoft has marked it as being \u201cexploitation less likely,\u201d perhaps due to the what Breen called the \u201cnetwork adjacent vector.\u201d\n\nIn other [...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:14.438838Z"}, {"uuid": "36c5c41b-269c-4a80-b8d7-e2e4405ddb47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-40487", "type": "seen", "source": "https://t.me/hacking_Attack/27439", "content": "g that allowed threat actors to conduct remote code execution (RCE) and to gain local system privileges.\n\nThis month\u2019s release includes a fix for CVE-2021-36970, a spoofing vulnerability in Microsoft\u2019s Windows Print Spooler that has a CVSSv3 score of 8.8.\n\nChris Morgan, senior cyber threat intelligence analyst at Digital Shadows, said that the spoofing vulnerability fix Microsoft put out today is meant to fix the problems that previous patches have introduced.\n\n\u201cWhile Microsoft provided a fix in their September 2021 update,\u00a0the patch resulted in a number of management problems,\u201d he told Threatpost. \u201cCertain printers required users to repeatedly input their administrator credentials every time an application attempted to print or had a client connect to a print server.\n\n\u201cOther problems included event logs recording error messages and denying users the ability to perform basic prints\u201d he continued. \u201cAs a result, many may have likely skipped the update due to its operational impact, ultimately leaving the risk posed by PrintNightmare in place.\u201d\n\nThis vulnerability was discovered by researchers XueFeng Li and Zhiniang Peng of Sangfor, who were also credited with the discovery of CVE-2021-1675, one of two vulnerabilities known as PrintNightmare.\n\nSatnam Narang, staff research engineer at Tenable noted that \u201cWhile no details have been shared publicly about the flaw, this is definitely one to watch for, as we saw a constant stream of Print Spooler-related vulnerabilities patched over the summer while ransomware groups began incorporating PrintNightmare into their affiliate playbook. We strongly encourage organizations to apply these patches as soon as possible.\u201d\nSee Also: Apple Pay with VISA lets hackers force payments on locked iPhones RCE Affects Microsoft Word, Office, SharePointAnother vulnerability worth noting is CVE-2021-40486, a critical RCE affecting Microsoft Word, Microsoft Office and some versions of SharePoint Server that can be exploited via the Preview Pane.\n\nGina Geisel, Automox product and partner marketing professional, noted that this vulnerability isn\u2019t new to Microsoft, with several other similar CVEs documented this year. In this case, the RCE vulnerability exists in some Microsoft apps when they fail to properly handle objects in memory.\n\nWith a low attack complexity, this vulnerability requires a user opening a specially crafted file either by email or via a website, either hosted by the attacker or through a compromised website that accepts or hosts user-provided content.\n\n\u201cAn attacker who successfully exploits this vulnerability can use this file to perform actions in the context of the current user,\u201d Geisel explained. \u201cFor example, the file could take actions on behalf of the logged-on user with the same permissions as the current user.\u201d Microsoft SharePoint Server RCEImmersive Labs\u2019 Breen told Threatpost that this RCE vulnerability \u2013 tracked as CVE-2021-40487\u00a0rated as 8.1 out of 10 CVSS score and marked as \u201cexploitation more likely\u201d \u2013 will be more difficult for an attacker to exploit, given that it requires an authenticated user on the domain.\n\nBut gaining RCE on a SharePoint server \u201copens up a lot of avenues for further exploitation,\u201d he noted via email.\n\n\u201cInternal SharePoint servers are often used to host company-sensitive documents and provide an intranet for staff to interact with,\u201d Breen explained. \u201cIf an attacker could manipulate the content of these articles or replace valid documents with malicious ones, they could steal credentials or trick targeted users into installing additional malware.\u201d Highest CVSS Award Goes to Microsoft Exchange Server RCECVE-2021-26427, the latest in Exchange Server RCEs, takes the severity cake this month, with a CVSS score of 9.0 out of 10. In spite of this hgh severity rating, Microsoft has marked it as being \u201cexploitation less likely,\u201d perhaps due to the what Breen called the \u201cnetwork adjacent vector.\u201d\n\nIn other [...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:02:41.233288Z"}, {"uuid": "5238b152-e336-4364-8192-036af1a0b9c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-40487", "type": "seen", "source": "https://t.me/hacking_Attack/27441", "content": "38, this vulnerability is, again, high severity \u2013 it allows an attacker to bypass the security rules of Windows AppContainer Firewall \u2013 as well as publicly disclosed.\n\nAppContainers are designed to protect against infiltration from third-party apps. They essentially isolate the runtime environment of applications with the goal of blocking malicious code.\n\nThis vulnerability results in loss of confidentiality and can be exploited without any user interaction.\n\nMaarten Buis, Automox product marketing manager, noted that a successful attacker that exploits this vulnerability could run arbitrary code on the endpoint, but they need to have administrative privileges before they can meaningfully exploit it.\n\n\u201cHowever, there is still a significant risk because no user interaction is required, and no special endpoint conditions are required for an attack to succeed,\u201d Buis explained to Threatpost via email .\n\nThere are no reports of the vulnerability having been actively exploited \u2013 yet. Still, Automox recommends a rapid patch rollout \u2013 as in, within 72 hours of the patch being made available \u2013 given that it\u2019s been publicly disclosed in a proof of concept by James Forshaw of Google\u2019s Project Zero.\n\nAleks Haugom, Automox product marketing manager, noted that, given the sheer number of apps users download, \u201cmaking sure that AppContianers cannot be compromised is important to every company\u2019s security hygiene.\u201d\nSee Also: Hacking stories \u2013 Operation Aurora: When China hacked Google How to Prioritize?Williams said that he doesn\u2019t want to sound like a broken record, but he\u2019s still going to say what security experts say every Patch Tuesday. To wit, \u201cPatch now.\u201d\n\nThat\u2019s particularly true for the MysterySnail campaign, he said: \u201cSeriously, this is not a patch Tuesday to delay on,\u201d he advised. \u201cThreat actors are actively exploiting the vulnerability for CVE-2021-40449 to elevate from user to administrator permissions on compromised systems. While CVE-2021-40449 doesn\u2019t allow for remote exploitation, that doesn\u2019t mean it can be taken lightly. Threat actors regularly gain access to target machines using phishing attacks and vulnerabilities such as CVE-2021-40449 allow them to evade more effectively bypass endpoint controls and evade detection.\u201d\n\nBesides which, MysterySnail\u2019s success in weaponizing this flaw means that other APTs will soon follow, Williams said: \u201cBecause the code for this has already been weaponized by one threat actor, we should expect to see it weaponized by others more quickly because there is already sample exploit code in the wild to work with.\u201d\n\nDanny Kim, Principle Architect at Virsec, who spent time at Microsoft during his graduate work on the OS security development team, voted for prioritizing the three critical remote code execution vulnerabilities: CVE-2021-40469, CVE-2021-26427 and CVE-2021-40487, which affect a wide range of Windows versions.\n\n\u201cThese vulnerabilities not only have a high to critical CVSS rating, but two of the three attacks (CVE-2021-40487, CVE-2021-40469) can be executed remotely,\u201d he stressed. \u201cRemote Code Execution (RCE) attacks are especially devastating because once the exploit is executed, [the attackers] can launch any kind of cyberattack, including ransomware.\n\nHe noted that RCE vulnerabilities were also the root cause of the Hafnium and Kaseya attacks. \u201cTrying to mitigate the attacker\u2019s actions after they have gained access is significantly harder than stopping the actions that led to the successful exploit,\u201d Kim pointed out. \u201cThis is why runtime monitoring of enterprises\u2019 server workloads is becoming a key part of today\u2019s cybersecurity. Stopping the exploitation of these vulnerabilities has to start with equipping the servers themselves with constant, deterministic runtime protection, not just detection.\u201d\nSource: threatpost.com (Click Link)Recent News* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/10/apple-iphone-hacking-90[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:02:40.737256Z"}]}