{"vulnerability": "cve-2021-2119", "sightings": [{"uuid": "e39cf15a-c3d0-4f60-ad4d-d2fe0401ccee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "MISP/f5030aca-7d5a-43a4-ae03-8f4ac8e85422", "content": "", "creation_timestamp": "2021-11-08T08:58:18.000000Z"}, {"uuid": "5e944496-f3f9-41d8-a16f-aa8ad67e5f49", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "MISP/3c19819c-1dac-4ef2-bfed-be5efa7e0123", "content": "", "creation_timestamp": "2021-11-20T09:53:52.000000Z"}, {"uuid": "3ed213cc-6e39-47a5-b2b8-58a5f1cdca97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "MISP/54800c42-6338-4df7-bceb-212ed90bd973", "content": "", "creation_timestamp": "2024-11-14T06:08:11.000000Z"}, {"uuid": "79c87bd3-beaf-49b1-968f-2d39638d21ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21191", "type": "seen", "source": "MISP/b68115dc-e2d1-4996-8966-85cedf58e561", "content": "", "creation_timestamp": "2024-11-14T06:08:48.000000Z"}, {"uuid": "8668445a-f6ff-407a-a1b0-3eda86badaa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://feedsin.space/feed/CISAKevBot/items/2971063", "content": "", "creation_timestamp": "2024-12-24T20:23:44.529106Z"}, {"uuid": "8909e13f-4b73-4896-bfcb-11917bbadeb0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "MISP/3c19819c-1dac-4ef2-bfed-be5efa7e0123", "content": "", "creation_timestamp": "2025-02-23T02:09:52.000000Z"}, {"uuid": "1d347406-18f5-4402-be81-41c5ffbaef50", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://www.govcert.gov.hk/en/alerts_detail.php?id=562", "content": "", "creation_timestamp": "2021-03-15T04:00:00.000000Z"}, {"uuid": "94911cc4-e79f-46a4-b639-631f837bba54", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "af0120d0-3dac-4a6a-974b-a9f33d2a9846", "vulnerability": "CVE-2021-21193", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/31315a90-8e28-4040-93ff-512adeaf1e1e", "content": "", "creation_timestamp": "2026-02-02T12:28:46.649793Z"}, {"uuid": "f91e81ac-fc18-4e8a-ad85-e2c97c277aea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/cKure/4335", "content": "\u25a0\u25a0\u25a0\u25a1\u25a1 Google Chrome update patches CVE-2021-21193 vulnerability | Kaspersky official blog.\n\nhttps://www.kaspersky.com/blog/google-chrome-cve-2021-21193/39013/", "creation_timestamp": "2021-03-15T16:11:43.000000Z"}, {"uuid": "544fe9d0-7868-4611-bcc1-52a340019657", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "exploited", "source": "https://t.me/cyberbannews_ir/3407", "content": "\u200d \ud83d\uded1\u0631\u0641\u0639 \u0647\u0641\u062a\u0645\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0631\u0648\u0632 \u0635\u0641\u0631 \u062f\u0631 \u0645\u0631\u0648\u0631\u06af\u0631 \u06a9\u0631\u0648\u0645 \n\n\u0634\u0631\u06a9\u062a \u06af\u0648\u06af\u0644 \u0628\u0647\u200c\u062a\u0627\u0632\u06af\u06cc \u0645\u0631\u0648\u0631\u06af\u0631 \u06a9\u0631\u0648\u0645 \u0631\u0627 \u062a\u0627 \u0646\u0633\u062e\u0647 91.0.4472.114 \u0627\u0631\u062a\u0642\u0627\u0621 \u062f\u0627\u062f\u0647 \u0648 4 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0628\u0631\u0637\u0631\u0641 \u06a9\u0631\u062f \u06a9\u0647 \u06cc\u06a9\u06cc \u0627\u0632 \u0622\u0646\u200c\u0647\u0627 \u0632\u06cc\u0631\u0648\u062f\u06cc \u0628\u0648\u062f\u0647 \u0648 \u0628\u0627 \u0634\u0646\u0627\u0633\u0647 \u00abCVE-2021-30554\u00bb \u0634\u0646\u0627\u062e\u062a\u0647 \u0645\u06cc\u200c\u0634\u0648\u062f.\n\n\u06a9\u0627\u0631\u0634\u0646\u0627\u0633\u0627\u0646 \u06af\u0648\u06af\u0644 \u0647\u0634\u062f\u0627\u0631 \u062f\u0627\u062f\u0647\u200c\u0627\u0646\u062f \u0645\u0647\u0627\u062c\u0645\u0627\u0646 \u0627\u06a9\u0633\u067e\u0644\u0648\u06cc\u062a \u0641\u0639\u0627\u0644 \u0627\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0631\u0627 \u062f\u0631 \u0627\u062e\u062a\u06cc\u0627\u0631 \u062f\u0627\u0631\u0646\u062f \u0648 \u062d\u0645\u0644\u0627\u062a \u062e\u0648\u062f \u0631\u0627 \u0628\u0627 \u0628\u0647\u0631\u0647\u200c\u06af\u06cc\u0631\u06cc \u0627\u0632 \u0622\u0646 \u0627\u0646\u062c\u0627\u0645 \u0645\u06cc\u200c\u062f\u0647\u0646\u062f. \n\n\u0627\u06cc\u0646 \u06cc\u06a9 \u0646\u0642\u0635 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0627\u0632 \u0646\u0648\u0639 use-after-free \u062f\u0631 \u062a\u0631\u06a9\u06cc\u0628 WebGL (Web Graphics Library) JavaScript API \u0627\u0633\u062a \u06a9\u0647 \u062c\u0647\u062a \u0631\u0646\u062f\u0631\u06cc\u0646\u06af \u06af\u0631\u0627\u0641\u06cc\u06a9\u200c\u0647\u0627\u06cc \u062a\u0639\u0627\u0645\u0644\u06cc 2D \u0648 3D \u0628\u062f\u0648\u0646 \u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0627\u0632 \u067e\u0644\u0627\u06af\u06cc\u0646\u200c\u0647\u0627 \u0645\u0648\u0631\u062f\u0627\u0633\u062a\u0641\u0627\u062f\u0647 \u0642\u0631\u0627\u0631 \u0645\u06cc\u200c\u06af\u06cc\u0631\u062f. \u0628\u0647\u0631\u0647\u200c\u0628\u0631\u062f\u0627\u0631\u06cc \u0627\u0632 \u0622\u0646 \u0645\u0645\u06a9\u0646 \u0627\u0633\u062a \u0645\u0646\u062c\u0631 \u0628\u0647 \u0627\u062c\u0631\u0627\u06cc \u06a9\u062f \u062f\u0644\u062e\u0648\u0627\u0647 \u062f\u0631 \u0631\u0627\u06cc\u0627\u0646\u0647\u200c\u0647\u0627\u06cc \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0628\u0627 \u0646\u0633\u062e\u0647\u200c\u0647\u0627\u06cc \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631 \u06a9\u0631\u0648\u0645 \u06af\u0631\u062f\u062f. \n\n\u0646\u0645\u0627\u06cc\u0646\u062f\u06af\u0627\u0646 \u06af\u0648\u06af\u0644 \u0627\u0639\u0644\u0627\u0645 \u06a9\u0631\u062f\u0647\u200c\u0627\u0646\u062f \u0645\u0645\u06a9\u0646 \u0627\u0633\u062a \u062f\u0633\u062a\u0631\u0633\u06cc \u0628\u0647 \u0627\u0637\u0644\u0627\u0639\u0627\u062a \u0645\u0631\u0628\u0648\u0637 \u0628\u0647 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627 \u0648 \u0644\u06cc\u0646\u06a9\u200c\u0647\u0627 \u062a\u0627 \u0632\u0645\u0627\u0646\u06cc \u06a9\u0647 \u0627\u06a9\u062b\u0631 \u06a9\u0627\u0631\u0628\u0631\u0627\u0646 \u0646\u0633\u062e\u0647 \u0628\u0647\u200c\u0631\u0648\u0632\u0631\u0633\u0627\u0646\u06cc \u0631\u0627 \u0646\u0635\u0628 \u0646\u06a9\u0646\u0646\u062f\u060c \u0645\u062d\u062f\u0648\u062f \u0634\u0648\u062f. \u0639\u0644\u0627\u0648\u0647 \u0628\u0631 \u0627\u06cc\u0646\u060c \u0686\u0646\u0627\u0646\u0686\u0647 \u0627\u0634\u06a9\u0627\u0644\u06cc \u062f\u0631 \u06a9\u062a\u0627\u0628\u062e\u0627\u0646\u0647 \u062b\u0627\u0644\u062b \u0648\u062c\u0648\u062f \u062f\u0627\u0634\u062a\u0647 \u0628\u0627\u0634\u062f \u06a9\u0647 \u0633\u0627\u06cc\u0631 \u0628\u062e\u0634\u200c\u0647\u0627 \u0628\u0647 \u0631\u0648\u0634 \u0645\u0634\u0627\u0628\u0647 \u0628\u0647 \u0622\u0646 \u0648\u0627\u0628\u0633\u062a\u0647 \u0628\u0627\u0634\u0646\u062f \u0648 \u0647\u0646\u0648\u0632 \u0628\u0631\u0637\u0631\u0641 \u0646\u0634\u062f\u0647 \u0628\u0627\u0634\u062f\u060c \u0645\u0645\u06a9\u0646 \u0627\u0633\u062a \u0645\u062d\u062f\u0648\u062f\u06cc\u062a\u200c\u0647\u0627\u06cc \u0645\u0634\u0627\u0628\u0647 \u0627\u0639\u0645\u0627\u0644 \u0634\u0648\u0646\u062f. \n\n\u0627\u06cc\u0646 \u0646\u0642\u0635 \u0627\u0645\u0646\u06cc\u062a\u06cc \u0647\u0641\u062a\u0645\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0631\u0648\u0632 \u0635\u0641\u0631\u06cc \u0627\u0633\u062a \u06a9\u0647 \u062f\u0631 \u0633\u0627\u0644 2021 \u0627\u0632 \u06a9\u0631\u0648\u0645 \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647 \u0627\u0633\u062a. \u067e\u06cc\u0634\u200c\u062a\u0631 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc\u200c\u0647\u0627\u06cc CVE-2021-21148\u060c CVE-2021-21166\u060c CVE-2021-21193\u060c CVE-2021-21220 \u0648 CVE-2021-30551 \u0646\u06cc\u0632 \u0627\u0632 \u0627\u06cc\u0646 \u0645\u0631\u0648\u0631\u06af\u0631 \u0628\u0631\u0637\u0631\u0641 \u0634\u062f\u0647\u200c\u0627\u0646\u062f. \n\n\u0634\u0634\u0645\u06cc\u0646 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0631\u0648\u0632 \u0635\u0641\u0631 \u0646\u06cc\u0632 \u0686\u0646\u062f \u0631\u0648\u0632 \u067e\u06cc\u0634 \u0648\u0635\u0644\u0647 \u0634\u062f. \u06af\u0648\u06af\u0644 \u0645\u0631\u0648\u0631\u06af\u0631 \u06a9\u0631\u0648\u0645 \u0631\u0627 \u0628\u0631\u0627\u06cc \u0648\u06cc\u0646\u062f\u0648\u0632\u060c \u0645\u06a9 \u0648 \u0644\u06cc\u0646\u0648\u06a9\u0633 \u062a\u0627 \u0646\u0633\u062e\u0647 91.0.4472.101 \u0628\u0647 \u0631\u0633\u0627\u0646\u06cc \u06a9\u0631\u062f\u0647 \u0648 \u0628\u0627 \u0631\u0641\u0639 14 \u0646\u0642\u0635 \u0627\u0645\u0646\u06cc\u062a\u06cc \u06cc\u06a9 \u0622\u0633\u06cc\u0628\u200c\u067e\u0630\u06cc\u0631\u06cc \u0631\u0648\u0632 \u0635\u0641\u0631 \u0628\u0627 \u0634\u0646\u0627\u0633\u0647 \u00abCVE-2021-30551\u00bb \u0631\u0627 \u0646\u06cc\u0632 \u0628\u0631\u0637\u0631\u0641 \u0646\u0645\u0648\u062f. \n\n#\u06af\u0648\u06af\u0644 \n\n@cyberbannews_ir", "creation_timestamp": "2021-06-19T11:23:57.000000Z"}, {"uuid": "46d1ccee-1e2b-4549-87e4-44e2076f9a8b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "published-proof-of-concept", "source": "https://t.me/infobes/295", "content": "#Analytics\n10 most exploited vulnerabilities of the week (march 8 - 14)\nCVE-2021-26855, CVE-2021-27065 - ProxyLogon MS Exchange Server RCE Vulnerability\nhttps://t.me/cybersecuritytechnologies/2835\nCVE-2021-1732 - Windows kernel 0-day exploit\nhttps://t.me/cybersecuritytechnologies/2679\nCVE-2021-22986, CVE-2021-22987 - F5 BIG-IP TMM uri_normalize_host infoleak and out-of-bounds write\nhttps://t.me/cybersecuritytechnologies/2881\nCVE-2021-21193 - Google Chrome Blink code execution\nhttps://vulmon.com/vulnerabilitydetails?qid=CVE-2021-21193\nCVE-2021-21978 - VMware View Planner\u00a0RCE\nhttps://mobile.twitter.com/osama_hroot/status/1367258907601698816\nhttps://paper.seebug.org/1495\nCVE-2021-21300 - Git vulnerability\nhttps://t.me/cybersecuritytechnologies/2880\nCVE-2021-26411 - IE mshtml use-after-free\nhttps://t.me/cybersecuritytechnologies/2908", "creation_timestamp": "2021-03-15T04:50:46.000000Z"}, {"uuid": "050ba08d-1242-411f-b094-5e79fb909c5d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "exploited", "source": "https://t.me/infobes/301", "content": "CVE-2021-26855/27065 - ProxyLogon MS Exchange Server RCE Vulnerability\nhttps://t.me/cybersecuritytechnologies/2835\nCVE-2021-3156 - Heap-Based Buffer Overflow in Sudo\nhttps://t.me/cybersecuritytechnologies/2577\nCVE-2021-22986 - F5 BIG-IP TMM uri_normalize_host infoleak and out-of-bounds write\nhttps://t.me/cybersecuritytechnologies/2881\nCVE-2021-27076 - A Replay-style Deserialization Attack Against SharePoint\nhttps://t.me/cybersecuritytechnologies/2930\nCVE-2021-21193 - Google Chrome Blink code execution\nhttps://vulmon.com/vulnerabilitydetails?qid=CVE-2021-21193\nCVE-2021-22987 - F5 BIG-IP TMM uri_normalize_host infoleak and out-of-bounds write\nhttps://t.me/cybersecuritytechnologies/2881\nCVE-2021-21193:\nGoogle Chrome Blink code execution\nhttps://vulmon.com/vulnerabilitydetails?qid=CVE-2021-21193\nCVE-2021-27076:\nReplay Deserialization Attack Against SharePoint\nhttps://t.me/cybersecuritytechnologies/2930\nCVE-2021-27889, CVE-2021-27890:\nMyBB RCE Chain\nhttps://blog.sonarsource.com/mybb-remote-code-execution-chain", "creation_timestamp": "2021-03-22T10:14:45.000000Z"}, {"uuid": "87692c2a-09b0-4803-b647-9f5b3edd8fa3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/arpsyndicate/1244", "content": "#ExploitObserverAlert\n\nCVE-2021-21193\n\nDESCRIPTION: Exploit Observer has 10 entries related to CVE-2021-21193. Use after free in Blink in Google Chrome prior to 89.0.4389.90 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.\n\nFIRST-EPSS: 0.009190000\nNVD-IS: 5.9\nNVD-ES: 2.8", "creation_timestamp": "2023-12-04T15:59:19.000000Z"}, {"uuid": "b8e04819-5ef6-458d-8703-6a244926724f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21191", "type": "seen", "source": "https://t.me/cibsecurity/24954", "content": "\u203c CVE-2021-21191 \u203c\n\nUse after free in WebRTC in Google Chrome prior to 89.0.4389.90 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-03-16T17:30:07.000000Z"}, {"uuid": "9dacb98c-6122-4a9c-8926-f18c11c0ccc7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21192", "type": "seen", "source": "https://t.me/cibsecurity/24953", "content": "\u203c CVE-2021-21192 \u203c\n\nHeap buffer overflow in tab groups in Google Chrome prior to 89.0.4389.90 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-03-16T17:30:06.000000Z"}, {"uuid": "c32806c6-cac0-463d-aee5-dbf5d715c9fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/cibsecurity/24952", "content": "\u203c CVE-2021-21193 \u203c\n\nUse after free in Blink in Google Chrome prior to 89.0.4389.90 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-03-16T17:30:05.000000Z"}, {"uuid": "9cdd5708-793e-42ac-b757-8048614d2a80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21190", "type": "seen", "source": "https://t.me/cibsecurity/24640", "content": "\u203c CVE-2021-21190 \u203c\n\nUninitialized data in PDFium in Google Chrome prior to 89.0.4389.72 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted PDF file.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-03-09T20:52:09.000000Z"}, {"uuid": "632c2f85-8122-4cc6-bc46-c5bd2a5d3d9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21198", "type": "seen", "source": "https://t.me/pwnwiki_zhchannel/604", "content": "CVE-2021-21198 Chrome Legacy ipc\u5171\u4eab\u5167\u5b58\u6d88\u606f\u50b3\u905e\u6f0f\u6d1e\nhttps://www.pwnwiki.org/index.php?title=CVE-2021-21198_Chrome_Legacy_ipc%E5%85%B1%E4%BA%AB%E5%85%A7%E5%AD%98%E6%B6%88%E6%81%AF%E5%82%B3%E9%81%9E%E6%BC%8F%E6%B4%9E", "creation_timestamp": "2021-06-06T13:42:54.000000Z"}, {"uuid": "c23fba97-4b52-413f-a2c8-15d62bb4c424", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "exploited", "source": "https://t.me/thehackernews/1090", "content": "\ud83d\udd25 WARNING \u2014 A second Google Chrome browser zero-day vulnerability (CVE-2021-21193) has been found actively exploited in-the-wild.\n\nRead details: https://thehackernews.com/2021/03/another-google-chrome-0-day-bug-found.html\nUpdate your browser for Windows, Mac, and Linux systems to 89.0.4389.90 or the latest available version.", "creation_timestamp": "2021-03-13T04:24:31.000000Z"}, {"uuid": "0f0ea4f5-0c6b-46d1-858c-ec94ec9e7057", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/2911", "content": "#Analytics\n10 most exploited vulnerabilities of the week (march 8 - 14)\nCVE-2021-26855, CVE-2021-27065 - ProxyLogon MS Exchange Server RCE Vulnerability\nhttps://t.me/cybersecuritytechnologies/2835\nCVE-2021-1732 - Windows kernel 0-day exploit\nhttps://t.me/cybersecuritytechnologies/2679\nCVE-2021-22986, CVE-2021-22987 - F5 BIG-IP TMM uri_normalize_host infoleak and out-of-bounds write\nhttps://t.me/cybersecuritytechnologies/2881\nCVE-2021-21193 - Google Chrome Blink code execution\nhttps://vulmon.com/vulnerabilitydetails?qid=CVE-2021-21193\nCVE-2021-21978 - VMware View Planner\u00a0RCE\nhttps://mobile.twitter.com/osama_hroot/status/1367258907601698816\nhttps://paper.seebug.org/1495\nCVE-2021-21300 - Git vulnerability\nhttps://t.me/cybersecuritytechnologies/2880\nCVE-2021-26411 - IE mshtml use-after-free\nhttps://t.me/cybersecuritytechnologies/2908", "creation_timestamp": "2021-03-15T11:00:37.000000Z"}, {"uuid": "d7a31723-a15c-4ffb-a6db-81f002bf50a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/2955", "content": "#Analytics\n10 most exploited vulnerabilities of the week (march 15 - 21)\nCVE-2021-26855/27065 - ProxyLogon MS Exchange Server RCE\nhttps://t.me/cybersecuritytechnologies/2835\nCVE-2021-3156 - Heap-Based Buffer Overflow in Sudo\nhttps://t.me/cybersecuritytechnologies/2577\nCVE-2021-22986/22987 - F5 BIG-IP TMM uri_normalize_host infoleak and out-of-bounds write\nhttps://t.me/cybersecuritytechnologies/2881\nCVE-2021-27076 - A Replay-style Deserialization Attack Against SharePoint\nhttps://t.me/cybersecuritytechnologies/2930\nCVE-2021-21193 - Google Chrome Blink code execution\nhttps://vulmon.com/vulnerabilitydetails?qid=CVE-2021-21193\nCVE-2021-21193:\nGoogle Chrome Blink code execution\nhttps://vulmon.com/vulnerabilitydetails?qid=CVE-2021-21193\nCVE-2021-27076:\nReplay Deserialization Attack Against SharePoint\nhttps://t.me/cybersecuritytechnologies/2930\nCVE-2021-27889, CVE-2021-27890:\nMyBB RCE Chain\nhttps://blog.sonarsource.com/mybb-remote-code-execution-chain", "creation_timestamp": "2021-03-29T05:54:18.000000Z"}, {"uuid": "7cb37101-3086-4960-9e1c-22c4cc20fbf4", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/f692d11a-a658-4e46-82ba-58eab403859f", "content": "", "creation_timestamp": "2026-06-19T12:47:47.287896Z"}, {"uuid": "0c0699f9-4251-4260-9c99-3d0be79ee7c8", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/04ad8abe-86a6-4dd1-a82b-069bd507e6c7", "content": "", "creation_timestamp": "2026-06-23T14:04:41.697091Z"}, {"uuid": "7da71751-06bf-45a5-850e-deec9b23d551", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "published-proof-of-concept", "source": "Telegram/uFKuhzjL4w1ghh9qImWl4mkE9uG6FMJvqHn56zexlO-GvjE", "content": "", "creation_timestamp": "2026-08-27T14:00:12.632958Z"}, {"uuid": "44090335-10ab-42fe-b700-ffe084deea0d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "published-proof-of-concept", "source": "Telegram/uFKuhzjL4w1ghh9qImWl4mkE9uG6FMJvqHn56zexlO-GvjE", "content": "", "creation_timestamp": "2026-08-28T00:00:43.854275Z"}, {"uuid": "a8babe11-ec43-410b-8d4f-c64b3863d9be", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/cissp/2505", "content": "WARNING \u2014 A second Google Chrome browser zero-day vulnerability (CVE-2021-21193) has been found actively exploited in-the-wild.\nRead details: https://thehackernews.com/2021/03/another-google-chrome-0-day-bug-found.html\nUpdate your browser for Windows, Mac, and Linux systems to 89.0.4389.90 or the latest available version.", "creation_timestamp": "2026-09-01T17:01:00.074396Z"}, {"uuid": "07b97021-7fa6-4910-83c9-4c4a4ee37a90", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/hacking_Attack/23972", "content": "ock, pointed out that Google has patched plenty of zero-days already this year \u2013 eight prior to the latest two, to be exact \u2013 and he said to expect more.\nSee Also: Offensive Security Tool: Jenkins Attack Framework 10th Zero-Day in 2021 for Google\u201cToday, Google released a patch for its tenth [and ninth] zero-day exploit of the year,\u201d Dunne said in an email to media. \u201cThis milestone highlights the emphasis that bad actors are putting on browser exploits, with Chrome becoming a clear favorite, allowing a streamlined way to gain access to millions of devices regardless of OS.\n\n\u201cWe expect to see continued zero-day exploits in the wild,\u201d he added.\n\nThe other zero days discovered so far in 2021 are as follows, many of them in the V8 engine:\n\n* CVE-2021-21148\u00a0\u2013 (February)\n* CVE-2021-21166\u00a0\u2013 (March)\n* CVE-2021-21193\u00a0\u2013 (March)\n* CVE-2021-21220\u00a0\u2013 (April)\n* CVE-2021-21224\u00a0\u2013 (April, later used in Windows attacks)\n* CVE-2021-30551\u00a0\u2013 (June)\n* CVE-2021-30554\u00a0\u2013 (June)\n* CVE-2021-30563\u00a0\u2013 (July)\n\n\u201cGoogle\u2019s commitment to patching these exploits quickly is commendable, as they operate Google Chrome as freeware and therefore are the sole entity who can provide these updates,\u201d Dunne wrote. \u201cGoogle is committed to providing Chrome as a free browser, as it is a critical entry point for other businesses such as Google Search and Google Workspace.\u201d\n\nThe news comes as Apple rushed a fix\u00a0for a zero-click zero-day exploit targeting iMessaging. It\u2019s allegedly been used to illegally spy on Bahraini activists with NSO Group\u2019s Pegasus spyware, according to researchers.\nMicrosoft is also expected to release its monthly Patch Tuesday set of updates today, so we\u2019ll see if there are yet more zero-day exploits to worry about.\nSource: threatpost.com (Click Link)Recent News* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/banner-2021.3-release-90x90.jpg Kali Linux 2021.3 released: Kali NetHunter on a smartwatch, wider OpenSSL compatibility, new tools1 day ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/microsoft-exploit-90x90.jpg Microsoft Patches Actively Exploited Windows Zero-Day Bug2 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/Apple-marketing-communications-mix-90x90.jpg Apple Issues Emergency Fix for NSO Zero-Click Zero Day3 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/zeroday-90x90.png Windows MSHTML zero-day exploits shared on hacking forums4 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/microsoft-zero-day-vulnerabilities-800x358-1-90x90.png Windows MSHTML zero-day defenses bypassed as new info emerges7 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/Malware-90x90.jpg Microsoft shares temp fix for ongoing Office 365 zero-day attacks1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/Jenkins-90x90.jpg Jenkins project\u2019s Confluence server hacked to mine Monero1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/unnamed-e1630998483665-90x90.jpg Critical Auth Bypass Bug Affect NETGEAR Smart Switches1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/loyalty-card-90x90.jpg Brute-Force Attacks Target Inboxes for Gift Card Data2 weeks ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/Braktooth-New-Bluetooth-gaps-threaten-countless-devices-1024x576-1-90x90.jpg Bluetooth Bugs Open Billions of Devices to DoS, Code Execution2 weeks ago\nThe post Pair of Google Chrome Zero-Day Bugs Actively Exploited first appeared on Black Hat Ethical Hacking.", "creation_timestamp": "2026-09-01T20:02:23.545192Z"}, {"uuid": "31070724-aa48-4a09-98a4-01143fe5e531", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/hacking_Attack/25743", "content": "Black Hat Ethical Hacking\nGoogle pushes emergency Chrome update to fix two zero-days\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png Google pushes emergency Chrome update to fix two zero-daysPost Views: 73 \nReading Time: 1 Minute\nGoogle has released Chrome 94.0.4606.71 for Windows, Mac, and Linux, to fix two zero-day vulnerabilities that have been exploited by attackers.\n\u201cGoogle is aware the exploits for CVE-2021-37975 and CVE-2021-37976 exist in the wild,\u201d Google disclosed in the list of security fixes\u00a0fixed in today\u2019s Google Chrome release.\n\nGoogle has started rolling out Chrome 94.0.4606.71 to users worldwide\u00a0in the Stable Desktop channel and should be available to all users within the coming days.\n\nTo install the update immediately, Google Chrome users can go to Chrome menu > Help > About Google Chrome, and the browser will begin performing the update.\n\nIn our tests, the new version of the browser was installed immediately using the above steps.\nhttps://www.bleepstatic.com/images/news/web-browsers/chrome/chrome-94.jpg \nZero-day attacks\u2019 details not disclosedWhile this Chrome release includes fixes for four security vulnerabilities, the two zero-days are concerning as they are known to have been exploited in the wild.\n\nThe first zero-day, tracked as CVE-2021-37976, is described as an \u201cInformation leak in core\u201d and was assigned a Medium severity level. This vulnerability was discovered by Cl\u00e9ment Lecigne from Google TAG, with technical assistance from Sergei Glazunov and Mark Brand from Google Project Zero, on September 21st, 2021.\n\nThe second zero-day, tracked as CVE-2021-37975, is a High severity user after free\u00a0bug in the Chrome V8 JavaScript engine. The researcher disclosed this vulnerability on September 24th and wished to remain anonymous.\n\nUse after free bugs are commonly used to perform remote code execution or escape the browser\u2019s security sandbox.\n\nAt this time, there are no other details regarding how these zero-day vulnerabilities were used in attacks but may be released in future reports by Google TAG or Project Zero.\n2 more in-the-wild 0days fixed by Chrome:\n* CVE-2021-37975 use-after-free in V8 by anonymous\n* CVE-2021-37976 info leak in core by @_clem1 #itw0days\n\nThe release cycle that Chrome is making happen in order to get these patches out is pretty impressivehttps://t.co/j1xPY4zjlP\n\n\u2014 Maddie Stone (@maddiestone) September 30, 2021\nSee Also: Hackers exploiting critical VMware vCenter CVE-2021-22005 bug Chrome users should perform a manual upgrade or restart their browser to install the latest version and prevent exploitation attempts. Thirteenth zero-day fixed this yearWith these two fixes, Google has patched 13\u00a0zero-day vulnerabilities in the Chrome web browser since the start of 2021.\n\nThe other Chrome zero-day bugs Google fixed this year are:\n\n* CVE-2021-21148\u00a0\u2013 February 4th, 2021\n* CVE-2021-21166\u00a0\u2013 March 2nd, 2021\n* CVE-2021-21193\u00a0\u2013 March 12th, 2021\n* CVE-2021-21220\u00a0\u2013 April 13th, 2021\n* CVE-2021-21224\u00a0\u2013 April 20th, 2021\n* CVE-2021-30551\u00a0\u2013 June 9th, 2021\n* CVE-2021-30554\u00a0\u2013 June 17th, 2021\n* CVE-2021-30563\u00a0\u2013 July 15th, 2021\n* CVE-2021-30632 and CVE-2021-30633\u00a0\u2013 September 13th\n* CVE-2021-37973\u00a0\u2013 September 24th, 2021\n\nAs Google is\u00a0rushing out Chrome updates to fix zero-days as they are reported, it is always critical to install new browser updates as soon as they become available.\nSee Also: Offensive Security Tool: Discover\n[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:19.578124Z"}, {"uuid": "db03471d-727e-4a8e-8ec0-a3ec50eeeebb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/hacking_Attack/1241", "content": "Black Hat Ethical Hacking\nGoogle Warns Mac, Windows Users of Chrome Zero-Day Flaw\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Google Warns Mac, Windows Users of Chrome Zero-Day FlawPost Views: 163 \nstyle=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> \nReading Time: 1 Minute\nThe use-after-free vulnerability is the third Google Chrome zero-day flaw to be disclosed in three months.\nGoogle is hurrying out a fix for a vulnerability in its Chrome browser that\u2019s under active attack \u2013 its third zero-day flaw so far this year. If exploited, the flaw could allow remote code-execution and denial-of-service attacks on affected systems.\n\nThe vulnerability exists in Blink, the browser engine for Chrome\u00a0developed as part of the Chromium project. Browser engines convert HTML documents and other web page resources into the visual representations viewable to end users.\n\n\u201cThe Stable channel has been updated to 89.0.4389.90 for Windows, Mac and Linux which will roll out over the coming days/weeks,\u201d according to Google\u2019s Friday security update.\n\nThe flaw (CVE-2021-21193) ranks 8.8 out of 10 on the CVSS vulnerability-rating scale, making it high-severity. It\u2019s a use-after-free vulnerability, which relates to incorrect use of dynamic memory during program operation. If after freeing a memory location, a program does not clear the pointer to that memory, an attacker can use the error to hack the program, according to a description of the vulnerability.\nSee Also: Critical Security Hole Can Knock Smart Meters Offline Use-After-Free Zero-Day FlawAccording to an IBM X-Force vulnerability report, the flaw could allow a remote attacker to execute arbitrary code on the system.\n\n\u201cBy persuading a victim to visit a specially crafted website, a remote attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition on the system,\u201d according to the report.\n\nFurther details are scant because \u201caccess to bug details and links may be kept restricted until a majority of users are updated with a fix,\u201d according to Google. The bug was credited to an anonymous reporter.\n\nGoogle also did not provide further specifics on the exploits other than to say it \u201cis aware of reports that an exploit for CVE-2021-21193 exists in the wild.\u201d\n\nThreatpost has reached out to Google for further comment.\nSee Also: Offensive Security Tool: Skipfish Other Google Chrome Security FlawsBeyond the zero-day flaw, Google issued four other security fixes on Friday.\n\nThese included another high-severity use-after-free flaw (CVE-2021-21191), which exists in WebRTC. WebRTC, which stands for web real-time communications, is an open-source project that gives web browsers and mobile applications interactive communications capabilities (such as voice, video and chat). The flaw was reported by someone who goes under the alias \u201craven\u201d (@raid_akame on Twitter).\n\nAnother high-severity flaw is a heap-buffer overflow error (CVE-2021-21192) that stems from Chrome tab groups. The flaw was reported by Abdulrahman Alqabandi with Microsoft Browser Vulnerability Research. See Also: Hacking Stories: Albert Gonzalez & the \u2018Get Rich or Die Trying\u2019 Crew who stole 130 million credit-card numbersThird Zero-Day Chrome Security Flaw This YearThe use-after-free flaw is the third zero-day flaw to plague Google\u2019s Chrome browser in the past three months \u2014 and the second this month alone. Earlier in March, Google said it fixed a high-severity zero-day vulnerability in its Chrome browser, which stems from the audio component of the browser.\n[...]", "creation_timestamp": "2026-09-01T20:02:50.534770Z"}, {"uuid": "4155084f-6978-4b37-89dd-03bd51f3b250", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21191", "type": "seen", "source": "https://t.me/hacking_Attack/1241", "content": "Black Hat Ethical Hacking\nGoogle Warns Mac, Windows Users of Chrome Zero-Day Flaw\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Google Warns Mac, Windows Users of Chrome Zero-Day FlawPost Views: 163 \nstyle=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> \nReading Time: 1 Minute\nThe use-after-free vulnerability is the third Google Chrome zero-day flaw to be disclosed in three months.\nGoogle is hurrying out a fix for a vulnerability in its Chrome browser that\u2019s under active attack \u2013 its third zero-day flaw so far this year. If exploited, the flaw could allow remote code-execution and denial-of-service attacks on affected systems.\n\nThe vulnerability exists in Blink, the browser engine for Chrome\u00a0developed as part of the Chromium project. Browser engines convert HTML documents and other web page resources into the visual representations viewable to end users.\n\n\u201cThe Stable channel has been updated to 89.0.4389.90 for Windows, Mac and Linux which will roll out over the coming days/weeks,\u201d according to Google\u2019s Friday security update.\n\nThe flaw (CVE-2021-21193) ranks 8.8 out of 10 on the CVSS vulnerability-rating scale, making it high-severity. It\u2019s a use-after-free vulnerability, which relates to incorrect use of dynamic memory during program operation. If after freeing a memory location, a program does not clear the pointer to that memory, an attacker can use the error to hack the program, according to a description of the vulnerability.\nSee Also: Critical Security Hole Can Knock Smart Meters Offline Use-After-Free Zero-Day FlawAccording to an IBM X-Force vulnerability report, the flaw could allow a remote attacker to execute arbitrary code on the system.\n\n\u201cBy persuading a victim to visit a specially crafted website, a remote attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition on the system,\u201d according to the report.\n\nFurther details are scant because \u201caccess to bug details and links may be kept restricted until a majority of users are updated with a fix,\u201d according to Google. The bug was credited to an anonymous reporter.\n\nGoogle also did not provide further specifics on the exploits other than to say it \u201cis aware of reports that an exploit for CVE-2021-21193 exists in the wild.\u201d\n\nThreatpost has reached out to Google for further comment.\nSee Also: Offensive Security Tool: Skipfish Other Google Chrome Security FlawsBeyond the zero-day flaw, Google issued four other security fixes on Friday.\n\nThese included another high-severity use-after-free flaw (CVE-2021-21191), which exists in WebRTC. WebRTC, which stands for web real-time communications, is an open-source project that gives web browsers and mobile applications interactive communications capabilities (such as voice, video and chat). The flaw was reported by someone who goes under the alias \u201craven\u201d (@raid_akame on Twitter).\n\nAnother high-severity flaw is a heap-buffer overflow error (CVE-2021-21192) that stems from Chrome tab groups. The flaw was reported by Abdulrahman Alqabandi with Microsoft Browser Vulnerability Research. See Also: Hacking Stories: Albert Gonzalez & the \u2018Get Rich or Die Trying\u2019 Crew who stole 130 million credit-card numbersThird Zero-Day Chrome Security Flaw This YearThe use-after-free flaw is the third zero-day flaw to plague Google\u2019s Chrome browser in the past three months \u2014 and the second this month alone. Earlier in March, Google said it fixed a high-severity zero-day vulnerability in its Chrome browser, which stems from the audio component of the browser.\n[...]", "creation_timestamp": "2026-09-01T20:02:50.765013Z"}, {"uuid": "7526eef4-689f-421a-bee2-412b640f7b1f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21192", "type": "seen", "source": "https://t.me/hacking_Attack/1241", "content": "Black Hat Ethical Hacking\nGoogle Warns Mac, Windows Users of Chrome Zero-Day Flaw\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Google Warns Mac, Windows Users of Chrome Zero-Day FlawPost Views: 163 \nstyle=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> \nReading Time: 1 Minute\nThe use-after-free vulnerability is the third Google Chrome zero-day flaw to be disclosed in three months.\nGoogle is hurrying out a fix for a vulnerability in its Chrome browser that\u2019s under active attack \u2013 its third zero-day flaw so far this year. If exploited, the flaw could allow remote code-execution and denial-of-service attacks on affected systems.\n\nThe vulnerability exists in Blink, the browser engine for Chrome\u00a0developed as part of the Chromium project. Browser engines convert HTML documents and other web page resources into the visual representations viewable to end users.\n\n\u201cThe Stable channel has been updated to 89.0.4389.90 for Windows, Mac and Linux which will roll out over the coming days/weeks,\u201d according to Google\u2019s Friday security update.\n\nThe flaw (CVE-2021-21193) ranks 8.8 out of 10 on the CVSS vulnerability-rating scale, making it high-severity. It\u2019s a use-after-free vulnerability, which relates to incorrect use of dynamic memory during program operation. If after freeing a memory location, a program does not clear the pointer to that memory, an attacker can use the error to hack the program, according to a description of the vulnerability.\nSee Also: Critical Security Hole Can Knock Smart Meters Offline Use-After-Free Zero-Day FlawAccording to an IBM X-Force vulnerability report, the flaw could allow a remote attacker to execute arbitrary code on the system.\n\n\u201cBy persuading a victim to visit a specially crafted website, a remote attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition on the system,\u201d according to the report.\n\nFurther details are scant because \u201caccess to bug details and links may be kept restricted until a majority of users are updated with a fix,\u201d according to Google. The bug was credited to an anonymous reporter.\n\nGoogle also did not provide further specifics on the exploits other than to say it \u201cis aware of reports that an exploit for CVE-2021-21193 exists in the wild.\u201d\n\nThreatpost has reached out to Google for further comment.\nSee Also: Offensive Security Tool: Skipfish Other Google Chrome Security FlawsBeyond the zero-day flaw, Google issued four other security fixes on Friday.\n\nThese included another high-severity use-after-free flaw (CVE-2021-21191), which exists in WebRTC. WebRTC, which stands for web real-time communications, is an open-source project that gives web browsers and mobile applications interactive communications capabilities (such as voice, video and chat). The flaw was reported by someone who goes under the alias \u201craven\u201d (@raid_akame on Twitter).\n\nAnother high-severity flaw is a heap-buffer overflow error (CVE-2021-21192) that stems from Chrome tab groups. The flaw was reported by Abdulrahman Alqabandi with Microsoft Browser Vulnerability Research. See Also: Hacking Stories: Albert Gonzalez & the \u2018Get Rich or Die Trying\u2019 Crew who stole 130 million credit-card numbersThird Zero-Day Chrome Security Flaw This YearThe use-after-free flaw is the third zero-day flaw to plague Google\u2019s Chrome browser in the past three months \u2014 and the second this month alone. Earlier in March, Google said it fixed a high-severity zero-day vulnerability in its Chrome browser, which stems from the audio component of the browser.\n[...]", "creation_timestamp": "2026-09-01T20:02:50.811481Z"}, {"uuid": "4ead8e42-dcea-4b1c-945b-808cd9ccc6a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21191", "type": "seen", "source": "https://t.me/hacking_Attack/1241", "content": "Black Hat Ethical Hacking\nGoogle Warns Mac, Windows Users of Chrome Zero-Day Flaw\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Google Warns Mac, Windows Users of Chrome Zero-Day FlawPost Views: 163 \nstyle=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> \nReading Time: 1 Minute\nThe use-after-free vulnerability is the third Google Chrome zero-day flaw to be disclosed in three months.\nGoogle is hurrying out a fix for a vulnerability in its Chrome browser that\u2019s under active attack \u2013 its third zero-day flaw so far this year. If exploited, the flaw could allow remote code-execution and denial-of-service attacks on affected systems.\n\nThe vulnerability exists in Blink, the browser engine for Chrome\u00a0developed as part of the Chromium project. Browser engines convert HTML documents and other web page resources into the visual representations viewable to end users.\n\n\u201cThe Stable channel has been updated to 89.0.4389.90 for Windows, Mac and Linux which will roll out over the coming days/weeks,\u201d according to Google\u2019s Friday security update.\n\nThe flaw (CVE-2021-21193) ranks 8.8 out of 10 on the CVSS vulnerability-rating scale, making it high-severity. It\u2019s a use-after-free vulnerability, which relates to incorrect use of dynamic memory during program operation. If after freeing a memory location, a program does not clear the pointer to that memory, an attacker can use the error to hack the program, according to a description of the vulnerability.\nSee Also: Critical Security Hole Can Knock Smart Meters Offline Use-After-Free Zero-Day FlawAccording to an IBM X-Force vulnerability report, the flaw could allow a remote attacker to execute arbitrary code on the system.\n\n\u201cBy persuading a victim to visit a specially crafted website, a remote attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition on the system,\u201d according to the report.\n\nFurther details are scant because \u201caccess to bug details and links may be kept restricted until a majority of users are updated with a fix,\u201d according to Google. The bug was credited to an anonymous reporter.\n\nGoogle also did not provide further specifics on the exploits other than to say it \u201cis aware of reports that an exploit for CVE-2021-21193 exists in the wild.\u201d\n\nThreatpost has reached out to Google for further comment.\nSee Also: Offensive Security Tool: Skipfish Other Google Chrome Security FlawsBeyond the zero-day flaw, Google issued four other security fixes on Friday.\n\nThese included another high-severity use-after-free flaw (CVE-2021-21191), which exists in WebRTC. WebRTC, which stands for web real-time communications, is an open-source project that gives web browsers and mobile applications interactive communications capabilities (such as voice, video and chat). The flaw was reported by someone who goes under the alias \u201craven\u201d (@raid_akame on Twitter).\n\nAnother high-severity flaw is a heap-buffer overflow error (CVE-2021-21192) that stems from Chrome tab groups. The flaw was reported by Abdulrahman Alqabandi with Microsoft Browser Vulnerability Research. See Also: Hacking Stories: Albert Gonzalez & the \u2018Get Rich or Die Trying\u2019 Crew who stole 130 million credit-card numbersThird Zero-Day Chrome Security Flaw This YearThe use-after-free flaw is the third zero-day flaw to plague Google\u2019s Chrome browser in the past three months \u2014 and the second this month alone. Earlier in March, Google said it fixed a high-severity zero-day vulnerability in its Chrome browser, which stems from the audio component of the browser.\n[...]", "creation_timestamp": "2026-09-02T01:03:26.475316Z"}, {"uuid": "4dfd90b6-fb9c-4f1f-b11b-b21acfb117f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21192", "type": "seen", "source": "https://t.me/hacking_Attack/1241", "content": "Black Hat Ethical Hacking\nGoogle Warns Mac, Windows Users of Chrome Zero-Day Flaw\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Google Warns Mac, Windows Users of Chrome Zero-Day FlawPost Views: 163 \nstyle=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> \nReading Time: 1 Minute\nThe use-after-free vulnerability is the third Google Chrome zero-day flaw to be disclosed in three months.\nGoogle is hurrying out a fix for a vulnerability in its Chrome browser that\u2019s under active attack \u2013 its third zero-day flaw so far this year. If exploited, the flaw could allow remote code-execution and denial-of-service attacks on affected systems.\n\nThe vulnerability exists in Blink, the browser engine for Chrome\u00a0developed as part of the Chromium project. Browser engines convert HTML documents and other web page resources into the visual representations viewable to end users.\n\n\u201cThe Stable channel has been updated to 89.0.4389.90 for Windows, Mac and Linux which will roll out over the coming days/weeks,\u201d according to Google\u2019s Friday security update.\n\nThe flaw (CVE-2021-21193) ranks 8.8 out of 10 on the CVSS vulnerability-rating scale, making it high-severity. It\u2019s a use-after-free vulnerability, which relates to incorrect use of dynamic memory during program operation. If after freeing a memory location, a program does not clear the pointer to that memory, an attacker can use the error to hack the program, according to a description of the vulnerability.\nSee Also: Critical Security Hole Can Knock Smart Meters Offline Use-After-Free Zero-Day FlawAccording to an IBM X-Force vulnerability report, the flaw could allow a remote attacker to execute arbitrary code on the system.\n\n\u201cBy persuading a victim to visit a specially crafted website, a remote attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition on the system,\u201d according to the report.\n\nFurther details are scant because \u201caccess to bug details and links may be kept restricted until a majority of users are updated with a fix,\u201d according to Google. The bug was credited to an anonymous reporter.\n\nGoogle also did not provide further specifics on the exploits other than to say it \u201cis aware of reports that an exploit for CVE-2021-21193 exists in the wild.\u201d\n\nThreatpost has reached out to Google for further comment.\nSee Also: Offensive Security Tool: Skipfish Other Google Chrome Security FlawsBeyond the zero-day flaw, Google issued four other security fixes on Friday.\n\nThese included another high-severity use-after-free flaw (CVE-2021-21191), which exists in WebRTC. WebRTC, which stands for web real-time communications, is an open-source project that gives web browsers and mobile applications interactive communications capabilities (such as voice, video and chat). The flaw was reported by someone who goes under the alias \u201craven\u201d (@raid_akame on Twitter).\n\nAnother high-severity flaw is a heap-buffer overflow error (CVE-2021-21192) that stems from Chrome tab groups. The flaw was reported by Abdulrahman Alqabandi with Microsoft Browser Vulnerability Research. See Also: Hacking Stories: Albert Gonzalez & the \u2018Get Rich or Die Trying\u2019 Crew who stole 130 million credit-card numbersThird Zero-Day Chrome Security Flaw This YearThe use-after-free flaw is the third zero-day flaw to plague Google\u2019s Chrome browser in the past three months \u2014 and the second this month alone. Earlier in March, Google said it fixed a high-severity zero-day vulnerability in its Chrome browser, which stems from the audio component of the browser.\n[...]", "creation_timestamp": "2026-09-02T01:03:26.515452Z"}, {"uuid": "ec1485db-2c78-437b-b84c-f96b46ed4773", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/hacking_Attack/23972", "content": "ock, pointed out that Google has patched plenty of zero-days already this year \u2013 eight prior to the latest two, to be exact \u2013 and he said to expect more.\nSee Also: Offensive Security Tool: Jenkins Attack Framework 10th Zero-Day in 2021 for Google\u201cToday, Google released a patch for its tenth [and ninth] zero-day exploit of the year,\u201d Dunne said in an email to media. \u201cThis milestone highlights the emphasis that bad actors are putting on browser exploits, with Chrome becoming a clear favorite, allowing a streamlined way to gain access to millions of devices regardless of OS.\n\n\u201cWe expect to see continued zero-day exploits in the wild,\u201d he added.\n\nThe other zero days discovered so far in 2021 are as follows, many of them in the V8 engine:\n\n* CVE-2021-21148\u00a0\u2013 (February)\n* CVE-2021-21166\u00a0\u2013 (March)\n* CVE-2021-21193\u00a0\u2013 (March)\n* CVE-2021-21220\u00a0\u2013 (April)\n* CVE-2021-21224\u00a0\u2013 (April, later used in Windows attacks)\n* CVE-2021-30551\u00a0\u2013 (June)\n* CVE-2021-30554\u00a0\u2013 (June)\n* CVE-2021-30563\u00a0\u2013 (July)\n\n\u201cGoogle\u2019s commitment to patching these exploits quickly is commendable, as they operate Google Chrome as freeware and therefore are the sole entity who can provide these updates,\u201d Dunne wrote. \u201cGoogle is committed to providing Chrome as a free browser, as it is a critical entry point for other businesses such as Google Search and Google Workspace.\u201d\n\nThe news comes as Apple rushed a fix\u00a0for a zero-click zero-day exploit targeting iMessaging. It\u2019s allegedly been used to illegally spy on Bahraini activists with NSO Group\u2019s Pegasus spyware, according to researchers.\nMicrosoft is also expected to release its monthly Patch Tuesday set of updates today, so we\u2019ll see if there are yet more zero-day exploits to worry about.\nSource: threatpost.com (Click Link)Recent News* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/banner-2021.3-release-90x90.jpg Kali Linux 2021.3 released: Kali NetHunter on a smartwatch, wider OpenSSL compatibility, new tools1 day ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/microsoft-exploit-90x90.jpg Microsoft Patches Actively Exploited Windows Zero-Day Bug2 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/Apple-marketing-communications-mix-90x90.jpg Apple Issues Emergency Fix for NSO Zero-Click Zero Day3 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/zeroday-90x90.png Windows MSHTML zero-day exploits shared on hacking forums4 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/microsoft-zero-day-vulnerabilities-800x358-1-90x90.png Windows MSHTML zero-day defenses bypassed as new info emerges7 days ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/Malware-90x90.jpg Microsoft shares temp fix for ongoing Office 365 zero-day attacks1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/Jenkins-90x90.jpg Jenkins project\u2019s Confluence server hacked to mine Monero1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/unnamed-e1630998483665-90x90.jpg Critical Auth Bypass Bug Affect NETGEAR Smart Switches1 week ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/loyalty-card-90x90.jpg Brute-Force Attacks Target Inboxes for Gift Card Data2 weeks ago\n* https://www.blackhatethicalhacking.com/wp-content/uploads/2021/09/Braktooth-New-Bluetooth-gaps-threaten-countless-devices-1024x576-1-90x90.jpg Bluetooth Bugs Open Billions of Devices to DoS, Code Execution2 weeks ago\nThe post Pair of Google Chrome Zero-Day Bugs Actively Exploited first appeared on Black Hat Ethical Hacking.", "creation_timestamp": "2026-09-02T01:02:53.513431Z"}, {"uuid": "e9ec865e-531e-44d2-82dd-0274edd2ac72", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/hacking_Attack/25743", "content": "Black Hat Ethical Hacking\nGoogle pushes emergency Chrome update to fix two zero-days\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png Google pushes emergency Chrome update to fix two zero-daysPost Views: 73 \nReading Time: 1 Minute\nGoogle has released Chrome 94.0.4606.71 for Windows, Mac, and Linux, to fix two zero-day vulnerabilities that have been exploited by attackers.\n\u201cGoogle is aware the exploits for CVE-2021-37975 and CVE-2021-37976 exist in the wild,\u201d Google disclosed in the list of security fixes\u00a0fixed in today\u2019s Google Chrome release.\n\nGoogle has started rolling out Chrome 94.0.4606.71 to users worldwide\u00a0in the Stable Desktop channel and should be available to all users within the coming days.\n\nTo install the update immediately, Google Chrome users can go to Chrome menu > Help > About Google Chrome, and the browser will begin performing the update.\n\nIn our tests, the new version of the browser was installed immediately using the above steps.\nhttps://www.bleepstatic.com/images/news/web-browsers/chrome/chrome-94.jpg \nZero-day attacks\u2019 details not disclosedWhile this Chrome release includes fixes for four security vulnerabilities, the two zero-days are concerning as they are known to have been exploited in the wild.\n\nThe first zero-day, tracked as CVE-2021-37976, is described as an \u201cInformation leak in core\u201d and was assigned a Medium severity level. This vulnerability was discovered by Cl\u00e9ment Lecigne from Google TAG, with technical assistance from Sergei Glazunov and Mark Brand from Google Project Zero, on September 21st, 2021.\n\nThe second zero-day, tracked as CVE-2021-37975, is a High severity user after free\u00a0bug in the Chrome V8 JavaScript engine. The researcher disclosed this vulnerability on September 24th and wished to remain anonymous.\n\nUse after free bugs are commonly used to perform remote code execution or escape the browser\u2019s security sandbox.\n\nAt this time, there are no other details regarding how these zero-day vulnerabilities were used in attacks but may be released in future reports by Google TAG or Project Zero.\n2 more in-the-wild 0days fixed by Chrome:\n* CVE-2021-37975 use-after-free in V8 by anonymous\n* CVE-2021-37976 info leak in core by @_clem1 #itw0days\n\nThe release cycle that Chrome is making happen in order to get these patches out is pretty impressivehttps://t.co/j1xPY4zjlP\n\n\u2014 Maddie Stone (@maddiestone) September 30, 2021\nSee Also: Hackers exploiting critical VMware vCenter CVE-2021-22005 bug Chrome users should perform a manual upgrade or restart their browser to install the latest version and prevent exploitation attempts. Thirteenth zero-day fixed this yearWith these two fixes, Google has patched 13\u00a0zero-day vulnerabilities in the Chrome web browser since the start of 2021.\n\nThe other Chrome zero-day bugs Google fixed this year are:\n\n* CVE-2021-21148\u00a0\u2013 February 4th, 2021\n* CVE-2021-21166\u00a0\u2013 March 2nd, 2021\n* CVE-2021-21193\u00a0\u2013 March 12th, 2021\n* CVE-2021-21220\u00a0\u2013 April 13th, 2021\n* CVE-2021-21224\u00a0\u2013 April 20th, 2021\n* CVE-2021-30551\u00a0\u2013 June 9th, 2021\n* CVE-2021-30554\u00a0\u2013 June 17th, 2021\n* CVE-2021-30563\u00a0\u2013 July 15th, 2021\n* CVE-2021-30632 and CVE-2021-30633\u00a0\u2013 September 13th\n* CVE-2021-37973\u00a0\u2013 September 24th, 2021\n\nAs Google is\u00a0rushing out Chrome updates to fix zero-days as they are reported, it is always critical to install new browser updates as soon as they become available.\nSee Also: Offensive Security Tool: Discover\n[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:02:48.862885Z"}, {"uuid": "5dffdc0d-9a95-4b41-bcb2-65095c92ac64", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/hacking_Attack/1241", "content": "Black Hat Ethical Hacking\nGoogle Warns Mac, Windows Users of Chrome Zero-Day Flaw\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2017/11/black-hat-locks-and-electronics.jpg Google Warns Mac, Windows Users of Chrome Zero-Day FlawPost Views: 163 \nstyle=\"display:block\"\n data-ad-client=\"ca-pub-6620833063853657\"\n data-ad-slot=\"8337846400\"\n data-ad-format=\"auto\"\n data-full-width-responsive=\"true\"> \nReading Time: 1 Minute\nThe use-after-free vulnerability is the third Google Chrome zero-day flaw to be disclosed in three months.\nGoogle is hurrying out a fix for a vulnerability in its Chrome browser that\u2019s under active attack \u2013 its third zero-day flaw so far this year. If exploited, the flaw could allow remote code-execution and denial-of-service attacks on affected systems.\n\nThe vulnerability exists in Blink, the browser engine for Chrome\u00a0developed as part of the Chromium project. Browser engines convert HTML documents and other web page resources into the visual representations viewable to end users.\n\n\u201cThe Stable channel has been updated to 89.0.4389.90 for Windows, Mac and Linux which will roll out over the coming days/weeks,\u201d according to Google\u2019s Friday security update.\n\nThe flaw (CVE-2021-21193) ranks 8.8 out of 10 on the CVSS vulnerability-rating scale, making it high-severity. It\u2019s a use-after-free vulnerability, which relates to incorrect use of dynamic memory during program operation. If after freeing a memory location, a program does not clear the pointer to that memory, an attacker can use the error to hack the program, according to a description of the vulnerability.\nSee Also: Critical Security Hole Can Knock Smart Meters Offline Use-After-Free Zero-Day FlawAccording to an IBM X-Force vulnerability report, the flaw could allow a remote attacker to execute arbitrary code on the system.\n\n\u201cBy persuading a victim to visit a specially crafted website, a remote attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition on the system,\u201d according to the report.\n\nFurther details are scant because \u201caccess to bug details and links may be kept restricted until a majority of users are updated with a fix,\u201d according to Google. The bug was credited to an anonymous reporter.\n\nGoogle also did not provide further specifics on the exploits other than to say it \u201cis aware of reports that an exploit for CVE-2021-21193 exists in the wild.\u201d\n\nThreatpost has reached out to Google for further comment.\nSee Also: Offensive Security Tool: Skipfish Other Google Chrome Security FlawsBeyond the zero-day flaw, Google issued four other security fixes on Friday.\n\nThese included another high-severity use-after-free flaw (CVE-2021-21191), which exists in WebRTC. WebRTC, which stands for web real-time communications, is an open-source project that gives web browsers and mobile applications interactive communications capabilities (such as voice, video and chat). The flaw was reported by someone who goes under the alias \u201craven\u201d (@raid_akame on Twitter).\n\nAnother high-severity flaw is a heap-buffer overflow error (CVE-2021-21192) that stems from Chrome tab groups. The flaw was reported by Abdulrahman Alqabandi with Microsoft Browser Vulnerability Research. See Also: Hacking Stories: Albert Gonzalez & the \u2018Get Rich or Die Trying\u2019 Crew who stole 130 million credit-card numbersThird Zero-Day Chrome Security Flaw This YearThe use-after-free flaw is the third zero-day flaw to plague Google\u2019s Chrome browser in the past three months \u2014 and the second this month alone. Earlier in March, Google said it fixed a high-severity zero-day vulnerability in its Chrome browser, which stems from the audio component of the browser.\n[...]", "creation_timestamp": "2026-09-02T01:03:26.277321Z"}, {"uuid": "40eee275-c78b-4506-9b66-e470dbd80ccb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21193", "type": "seen", "source": "https://t.me/cissp/2505", "content": "WARNING \u2014 A second Google Chrome browser zero-day vulnerability (CVE-2021-21193) has been found actively exploited in-the-wild.\nRead details: https://thehackernews.com/2021/03/another-google-chrome-0-day-bug-found.html\nUpdate your browser for Windows, Mac, and Linux systems to 89.0.4389.90 or the latest available version.", "creation_timestamp": "2026-09-02T01:04:50.886314Z"}]}