{"vulnerability": "cve-2021-21148", "sightings": [{"uuid": "834ebe40-72ec-4381-843b-4461cb90c79a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "MISP/3c19819c-1dac-4ef2-bfed-be5efa7e0123", "content": "", "creation_timestamp": "2021-11-20T09:53:52.000000Z"}, {"uuid": "d64682bf-8fde-4175-bae5-2423b10f4b14", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "MISP/f5030aca-7d5a-43a4-ae03-8f4ac8e85422", "content": "", "creation_timestamp": "2021-11-08T08:58:17.000000Z"}, {"uuid": "27cab4c9-94c8-44b7-9011-012c3870e2d6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "MISP/1122b900-e4ba-4aaa-8ce3-cc7fc447cb31", "content": "", "creation_timestamp": "2024-11-14T06:08:25.000000Z"}, {"uuid": "e0119e31-67a3-4215-b09b-2753ae600bec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://feedsin.space/feed/CISAKevBot/items/2971073", "content": "", "creation_timestamp": "2024-12-24T20:23:52.189049Z"}, {"uuid": "b4e02d45-9fff-4c76-a079-ce439efeb26d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "MISP/3c19819c-1dac-4ef2-bfed-be5efa7e0123", "content": "", "creation_timestamp": "2025-02-23T02:09:51.000000Z"}, {"uuid": "c9c409d4-e84e-45c4-97ea-0ebcf13b3d41", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://www.govcert.gov.hk/en/alerts_detail.php?id=548", "content": "", "creation_timestamp": "2021-02-08T04:00:00.000000Z"}, {"uuid": "3e7d27c0-c8b7-4742-bb63-ca4d60c7d07d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "af0120d0-3dac-4a6a-974b-a9f33d2a9846", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/c7343d52-dd13-4321-947f-fb29745f05d2", "content": "", "creation_timestamp": "2026-02-02T12:28:45.196492Z"}, {"uuid": "45d1f06f-b06e-4a66-8ef2-37e978f72bfc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/cKure/3846", "content": "\u25a0\u25a0\u25a0\u25a0\u25a0 Google fixes Chrome zero-day actively exploited in the wild.\n\nCVE-2021-21148: A heap based buffer overflow. Exploit allegedly created by Zinc group; DPRK #NorthKorea \ud83c\uddf0\ud83c\uddf5\n\nhttps://www.bleepingcomputer.com/news/security/google-fixes-chrome-zero-day-actively-exploited-in-the-wild/ | #0day #Zeroday", "creation_timestamp": "2021-02-05T10:38:17.000000Z"}, {"uuid": "550d712d-23d6-4353-a9c3-cf1e011acc31", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/ARinteg/326", "content": "\u0421\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u044b \u00ab\u041b\u0430\u0431\u043e\u0440\u0430\u0442\u043e\u0440\u0438\u0438 \u041a\u0430\u0441\u043f\u0435\u0440\u0441\u043a\u043e\u0433\u043e\u00bb \u0440\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u044e\u0442 \u0441\u0440\u043e\u0447\u043d\u043e \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c Google Chrome \u0434\u043e \u0432\u0435\u0440\u0441\u0438\u0438 88.0.4324.150\n\n\u0412 \u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0435 \u0432\u0441\u043a\u0440\u044b\u043b\u0438 \u043a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0443\u044e \u0431\u0440\u0435\u0448\u044c CVE-2021-21148, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u0443\u0436\u0435 \u0432\u043e\u0448\u043b\u0430 \u0432 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u044e \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u043c\u0438 \u0445\u0430\u043a\u0435\u0440\u0430\u043c\u0438. \u0412 \u0437\u043e\u043d\u0443 \u0440\u0438\u0441\u043a\u0430 \u043f\u043e\u043f\u0430\u0434\u0430\u044e\u0442 \u0432\u0441\u0435 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c\u044b\u0435 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u044b\u0435 \u0441\u0438\u0441\u0442\u0435\u043c\u044b: Windows, MacOS \u0438 Linux. \u041f\u0430\u0442\u0447, \u0437\u0430\u043a\u0440\u044b\u0432\u0430\u044e\u0449\u0438\u0439 \u0434\u0430\u043d\u043d\u0443\u044e \u0431\u0440\u0435\u0448\u044c, \u0443\u0436\u0435 \u0432\u044b\u043f\u0443\u0449\u0435\u043d. \u0414\u043b\u044f \u0442\u043e\u0433\u043e, \u0447\u0442\u043e\u0431\u044b \u043e\u043d \u0440\u0430\u0431\u043e\u0442\u0430\u043b, \u043f\u0435\u0440\u0435\u0439\u0434\u0438\u0442\u0435 \u0432 \u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 -> \u041e \u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0435 Chrome. \u0411\u0440\u0430\u0443\u0437\u0435\u0440 \u043f\u043e\u0441\u043b\u0435 \u044d\u0442\u043e\u0433\u043e \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u0441\u044f \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438. \u041a\u043d\u043e\u043f\u043a\u0430 \u043d\u0430\u0445\u043e\u0434\u0438\u0442\u0441\u044f \u0432 \u0432\u0435\u0440\u0445\u043d\u0435\u043c \u043f\u0440\u0430\u0432\u043e\u043c \u0443\u0433\u043b\u0443 \u043e\u043a\u043d\u0430.", "creation_timestamp": "2021-02-20T12:43:00.000000Z"}, {"uuid": "702e1469-34b9-4c56-a106-f4b7a27b876c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/noobhackersyoutube/633", "content": "#cybernews by @noobhackersofficial\n\n\u26a0\ufe0f An important update for all users: update #Google Chrome immediately. \n\nHackers are actively exploiting a dangerous vulnerability (CVE-2021-21148) in Google Chrome. Time to get to updating! https://t.co/ws4JxZLAJZ", "creation_timestamp": "2021-02-08T12:52:12.000000Z"}, {"uuid": "dfbdae0e-fcc4-4dbc-8317-54ac6f3b2432", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "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": "7172cf3e-818c-4af9-816f-19585bb7e43e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/thesammymove/5733", "content": "Update your chrome browser immediately!\ud83d\udea8  \n\nChannel: @thesammymove\n#thesammymovenews \n\n- Google has patched a zero-day vulnerability in Chrome web browser for desktop that it says is being actively exploited in the wild.\n\n-The company released 88.0.4324.150 for Windows, Mac, and Linux, with a fix for a heap buffer overflow flaw (CVE-2021-21148) in its V8 JavaScript rendering engine.\n\n\"Google is aware of reports that an exploit for CVE-2021-21148 exists in the wild,\" the company said in a statement.\n\n-The security flaw was reported to Google by Mattias Buelens on January 24", "creation_timestamp": "2021-02-06T20:54:42.000000Z"}, {"uuid": "02427923-3848-4c6b-975c-a7ac071af490", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://t.me/arpsyndicate/1006", "content": "#ExploitObserverAlert\n\nCVE-2021-21148\n\nDESCRIPTION: Exploit Observer has 18 entries related to CVE-2021-21148. Heap buffer overflow in V8 in Google Chrome prior to 88.0.4324.150 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.\n\nFIRST-EPSS: 0.019330000\nNVD-IS: 5.9\nNVD-ES: 2.8", "creation_timestamp": "2023-12-03T19:05:52.000000Z"}, {"uuid": "81f861e9-9932-4b43-9495-a2cba3ac828c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/thesammymove/1694", "content": "Update your chrome browser immediately!\ud83d\udea8  \n\nChannel: @thesammymove\n#thesammymovenews \n\n- Google has patched a zero-day vulnerability in Chrome web browser for desktop that it says is being actively exploited in the wild.\n\n-The company released 88.0.4324.150 for Windows, Mac, and Linux, with a fix for a heap buffer overflow flaw (CVE-2021-21148) in its V8 JavaScript rendering engine.\n\n\"Google is aware of reports that an exploit for CVE-2021-21148 exists in the wild,\" the company said in a statement.\n\n-The security flaw was reported to Google by Mattias Buelens on January 24", "creation_timestamp": "2021-02-06T20:54:39.000000Z"}, {"uuid": "52e555ce-3832-4068-a29c-2758e9b9eac9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/true_secator/1402", "content": "Google \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0438 \u0432\u0435\u0440\u0441\u0438\u044e Chrome 88.0.4324.150 \u0434\u043b\u044f Windows, Mac \u0438 Linux.\n\n\u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u044f\u0435\u0442 \u0432\u0441\u0435\u0433\u043e \u043e\u0434\u043d\u0443 \u043e\u0448\u0438\u0431\u043a\u0443, \u0437\u0430\u0442\u043e \u043a\u0430\u043a\u0443\u044e. CVE-2021-21148 - \u044d\u0442\u043e 0-day \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u043e\u0431\u043e\u0439 \u043f\u0435\u0440\u0435\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u043a\u0443\u0447\u0438 \u0432 \u0434\u0432\u0438\u0436\u043a\u0435 V8 \u0438, \u043a\u0430\u043a \u0441\u043e\u043e\u0431\u0449\u0430\u0435\u0442 Google, \u043a \u043c\u043e\u043c\u0435\u043d\u0442\u0443 \u0435\u0435 \u043e\u0442\u043a\u0440\u044b\u0442\u0438\u044f 24 \u044f\u043d\u0432\u0430\u0440\u044f \u0443\u0436\u0435 \u0430\u043a\u0442\u0438\u0432\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043b\u0430\u0441\u044c \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c\u0438 \u0432 \u0434\u0438\u043a\u043e\u0439 \u043f\u0440\u0438\u0440\u043e\u0434\u0435.\n\n\u0421\u0443\u0434\u044f \u043f\u043e \u0432\u0441\u0435\u043c\u0443, \u044d\u0442\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u0441\u043e\u0441\u0442\u0430\u0432\u043b\u044f\u044e\u0449\u0438\u0445 \u0431\u043e\u0435\u0432\u043e\u0433\u043e \u044d\u043a\u0441\u043f\u043b\u043e\u0439\u0442-\u043a\u0438\u0442\u0430, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043f\u0440\u0438\u043c\u0435\u043d\u044f\u043b\u0438 \u0445\u0430\u043a\u0435\u0440\u044b \u0438\u0437 \u0441\u0435\u0432\u0435\u0440\u043e\u043a\u043e\u0440\u0435\u0439\u0441\u043a\u043e\u0439 APT Lazarus \u043f\u0440\u0438 \u0430\u0442\u0430\u043a\u0430\u0445 \u043d\u0430 \u0438\u043d\u0444\u043e\u0441\u0435\u043a \u044d\u043a\u0441\u043f\u0435\u0440\u0442\u043e\u0432.\n\n\u0422\u0430\u043a \u0447\u0442\u043e \u0432\u0441\u0435\u043c \u043f\u0440\u0438\u0447\u0430\u0441\u0442\u043d\u044b\u043c \u043a \u043e\u0442\u0440\u0430\u0441\u043b\u0438 \u0418\u0411 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e \u0441\u0440\u043e\u0447\u043d\u043e \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c \u0441\u0432\u043e\u0438 Chrome. \u041d\u0443, \u0438 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u043c \u0442\u043e\u0436\u0435.\n\n\u0414\u0440\u0443\u0433\u0443\u044e 0-day \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 Internet Explorer, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0442\u0430\u043a\u0436\u0435 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043b\u0438 \u0441\u0435\u0432\u0435\u0440\u043e\u043a\u043e\u0440\u0435\u0439\u0446\u044b \u0432 \u044d\u0442\u0438\u0445 \u0430\u0442\u0430\u043a\u0430\u0445, \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b\u0438 \u0438\u0441\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0438\u0437 \u044e\u0436\u043d\u043e\u043a\u043e\u0440\u0435\u0439\u0441\u043a\u043e\u0439 \u0438\u043d\u0444\u043e\u0441\u0435\u043a \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 ENKI. \u041f\u043e \u0438\u0445 \u0434\u0430\u043d\u043d\u044b\u043c, \u0430\u0442\u0430\u043a\u0435 \u043f\u043e\u0434\u0432\u0435\u0440\u0433\u043b\u0438\u0441\u044c \u0438\u0445 \u0441\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0435 \u044d\u043a\u0441\u043f\u0435\u0440\u0442\u044b. \u0418, \u0445\u043e\u0442\u044f \u043e\u043d\u0430 \u043d\u0435 \u0443\u0432\u0435\u043d\u0447\u0430\u043b\u0430\u0441\u044c \u0443\u0441\u043f\u0435\u0445\u043e\u043c, \u043f\u043e\u043b\u0443\u0447\u0435\u043d\u043d\u044b\u0435 \u0434\u0430\u043d\u043d\u044b\u0435 \u043f\u043e\u043c\u043e\u0433\u043b\u0438 \u0432\u044b\u044f\u0432\u0438\u0442\u044c \u0441\u0432\u0435\u0436\u0443\u044e \u043e\u0448\u0438\u0431\u043a\u0443. \u0421\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0443\u044e\u0449\u0438\u0439 PoC \u0438\u043c\u0435\u0435\u0442\u0441\u044f.\n\n\u041f\u0440\u0430\u0432\u0434\u0430 Microsoft, \u0432 \u043e\u0442\u043b\u0438\u0447\u0438\u0435 \u043e\u0442 Google, \u044d\u0442\u0443 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u043f\u043e\u043a\u0430 \u043d\u0435 \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u043b\u0438.", "creation_timestamp": "2021-02-05T10:35:08.000000Z"}, {"uuid": "e244bbb5-3b6e-4223-8d8e-af2225d4b670", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/NeKaspersky/485", "content": "Google \u0437\u0430\u043a\u0440\u044b\u043b\u0438 0-day \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0434\u043b\u044f Windows, Mac \u0438 Linux\n\n\u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c CVE-2021-21148 \u043f\u043e\u0444\u0438\u043a\u0441\u0438\u043b\u0438 \u0432 \u043d\u043e\u0432\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 Chrome. \u041e\u043d\u0430 \u0431\u044b\u043b\u0430 \u0432 \u0434\u0432\u0438\u0436\u043a\u0435 V8 JavaScript \u0438 \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0438\u0440\u043e\u0432\u0430\u043b\u0430\u0441\u044c \u0445\u0430\u043a\u0435\u0440\u0430\u043c\u0438. \u0415\u0451 \u043e\u043f\u0438\u0441\u044b\u0432\u0430\u044e\u0442 \u043a\u0430\u043a \u043e\u0448\u0438\u0431\u043a\u0443 \u043d\u0430\u0440\u0443\u0448\u0435\u043d\u0438\u044f \u0446\u0435\u043b\u043e\u0441\u0442\u043d\u043e\u0441\u0442\u0438 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0439 \u043f\u0430\u043c\u044f\u0442\u0438. \n\n\u041e\u043d\u0430 \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u043b\u0430 \u043e\u0441\u0443\u0449\u0435\u0441\u0442\u0432\u043b\u044f\u0442\u044c \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u043e\u0433\u043e \u043a\u043e\u0434\u0430. \u041f\u043e\u044d\u0442\u043e\u043c\u0443, \u043d\u0430\u0441\u0442\u043e\u044f\u0442\u0435\u043b\u044c\u043d\u043e \u0441\u043e\u0432\u0435\u0442\u0443\u0435\u043c \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c\u0441\u044f, \u043f\u0440\u0435\u0436\u0434\u0435 \u0447\u0435\u043c \u043f\u043e\u0435\u0445\u0430\u0442\u044c \u0431\u0443\u0445\u0430\u0442\u044c \u0432 \u0431\u0430\u0440.\n\nhttps://chromereleases.googleblog.com/2021/02/stable-channel-update-for-desktop_4.html", "creation_timestamp": "2021-02-05T17:44:53.000000Z"}, {"uuid": "57afcb6e-ba8e-4645-8666-8e3f61f5c75c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://t.me/cibsecurity/23306", "content": "\u203c CVE-2021-21148 \u203c\n\nHeap buffer overflow in V8 in Google Chrome prior to 88.0.4324.150 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-02-09T18:40:38.000000Z"}, {"uuid": "d9ff3c66-256b-4954-b69a-fed59a152344", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://t.me/pwnwiki_zhchannel/427", "content": "CVE-2021-21156&CVE-2021-21148 Chrome Array Transfer \u7e5e\u904e\u6f0f\u6d1e\nhttps://www.pwnwiki.org/index.php?title=CVE-2021-21156%26CVE-2021-21148_Chrome_Array_Transfer_%E7%B9%9E%E9%81%8E%E6%BC%8F%E6%B4%9E", "creation_timestamp": "2021-05-15T05:05:20.000000Z"}, {"uuid": "aa4835ae-3cf6-4c3c-bedd-2e5ea8865a95", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/3428", "content": "#exploit\nCVE-2021-21148,\nCVE-2021-21156:\nChrome Array Transfer Bypass (PoC)\n\n// The fix for CVE-2021-21148 has added a check in |ValueSerializer::WriteJSArrayBuffer| to make sure non-detachable array buffers cannot be transferred. The check can be bypassed with the help of asm.js and property getters", "creation_timestamp": "2021-05-22T13:03:01.000000Z"}, {"uuid": "1039c84f-f110-4de5-a751-e55c8dab2e4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "Telegram/9RHj3eL8JEPv9m7C413UU7_ewFPt-Ox3W930FtyU4VNnI9g", "content": "", "creation_timestamp": "2021-02-08T11:38:28.000000Z"}, {"uuid": "9daec77d-d447-4481-b1c8-a7689b64bc49", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/b8106cec-4c6e-4b66-a5c3-b7a407c9cf21", "content": "", "creation_timestamp": "2026-06-19T12:47:46.434240Z"}, {"uuid": "5bd03943-cced-4ad2-95f2-357d869442e8", "vulnerability_lookup_origin": "caeb2787-0d58-4236-9039-7c86c3e566f3", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://vulnerability.circl.lu/known-exploited-vulnerabilities-catalog/3034aa64-c42f-4d85-9716-94c53519e03a", "content": "", "creation_timestamp": "2026-06-23T14:04:42.495789Z"}, {"uuid": "229fcc29-3131-44e5-93cd-7de2a35b7ed9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://t.me/hacking_Attack/48245", "content": "Black Hat Ethical Hacking\nGoogle Chrome Bug Actively Exploited as Zero-Day\n\nGoogle Chrome Bug Actively Exploited as Zero-DayPost Views: 32 \nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/02/Patreon.png \nReading Time: 2 Minutes\nGoogle issued an update for the bug, which is found in the open-source V8 JavaScript engine.\nGoogle has updated its Stable channel for the desktop version of Chrome, to address a zero-day security vulnerability that\u2019s being actively exploited in the wild.\n\nThe bug, tracked as CVE-2022-1096, is a type-confusion issue in the V8 JavaScript engine, which is an open-source engine used by Chrome and Chromium-based web browsers. Type confusion, as Microsoft has laid out in the past, occurs \u201cwhen a piece of code doesn\u2019t verify the type of object that is passed to it, and uses it blindly without type-checking, it leads to type confusion\u2026Also with type confusion, wrong function pointers or data are fed into the wrong piece of code. In some circumstances this can lead to code execution.\u201d\n\nGoogle didn\u2019t provide additional technical details, as is its wont, but did say that it was \u201caware that an exploit for CVE-2022-1096 exists in the wild.\u201d An anonymous researcher was credited with finding the issue, which is labeled \u201chigh-severity\u201d (no CVSS score was given).\n\nThe lack of any further information is a source of frustration to some.\n\n\u201cAs a defender, I really wish it was more clear what this security fix is,\u201d John Bambenek, principal threat hunter at Netenrich, said via email. \u201cI get permission-denied errors or \u2018need to authenticate,\u2019 so I can\u2019t make decisions or advise my clients. A little more transparency would be beneficial and appreciated.\u201d\nSee Also: Complete Offensive Security and Ethical Hacking Course\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/03/Solutions-1.png Emergency Patch; Active ExploitThe internet giant has updated the Stable channel to 99.0.4844.84 for Chrome for Windows, Mac and Linux, according to the its security advisory. Microsoft, which offers the Chromium-based Edge browser, also issued its own advisory. It\u2019s unclear whether other offerings built in V8, such as the JavaScript runtime environment Node.js, are also affected.\n\nThe patch was issued on an emergency basis, likely due to the active exploit that\u2019s circulating, researchers noted.\n\n\u201cThe first thing which stood out to me about this update is that it only fixes a single issue,\u201d Casey Ellis, founder and CTO at Bugcrowd, noted by email. \u201cThis is pretty unusual for Google. They typically fix multiple issues in these types of releases, which suggests that they are quite concerned and very motivated to see fixes against CVE-2022-1096 applied across their user-base ASAP.\u201d\n\nHe also commented on the speed of the patch being rolled out.\n\n\u201cThe vulnerability was only reported on the 23rd of March, and while Google\u2019s Chrome team do tend to be fairly prompt in developing, testing and rolling patches, the idea of a patch for software deployed as widely deployed as Chrome in 48 hours is something is continue to be impressed by,\u201d he said. \u201cSpeculatively, I\u2019d suggest that the vulnerability has been discovered via detection of active exploitation in the wild, and the combination of impact and potentially the malicious actors currently using it contributed to the fast turnaround.\u201d\nSee Also: Kali Linux 2022.1 Release with Visual Updates, New Tools, Legacy SSH V8 Engine in the CrosshairsThe V8 engine has been plagued with security bugs and targeted by cyberattackers many times in the last year:\n\nLast year delivered a total of these 16 Chrome zero days:\n\n* CVE-2021-21148\u00a0\u2013 Feb. 4, an unnamed type of bug in V8\n* CVE-2021-21224\u00a0\u2013 April 20, an issue with type confusion in V8 that could have allowed a remote attacker t[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:01:49.288867Z"}, {"uuid": "0fa35fe3-af35-4bda-8475-c8cabbeb4d4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "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.682009Z"}, {"uuid": "40ff3497-0133-4e8d-9951-78cbdc3e7968", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "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.720599Z"}, {"uuid": "3c3e8cf2-08b2-4b82-883d-464f5f82343b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://t.me/hacking_Attack/8661", "content": "Exploit Collector\nChrome Array Transfer Bypass\n\nhttps://2.bp.blogspot.com/-LETyKySuDgQ/WWlvb4o-z5I/AAAAAAAAIPU/5gCHtKhwhLoet_fHEL-XnPuLlDk7q9atQCLcBGAs/s1600/h76.png \nThe fix for CVE-2021-21148 has added a check in |ValueSerializer::WriteJSArrayBuffer| to make sure non-detachable array buffers cannot be transferred. The check can be bypassed with the help of asm.js and property getters.\n\nMD5 | 2c54899cf0b5cf9ab027a5329061b62e\n\nDownload\nSource:packetstormsecurity.com", "creation_timestamp": "2026-09-01T20:02:41.910182Z"}, {"uuid": "d70a4fd0-91de-4df9-a037-cc678ea21624", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://t.me/hacking_Attack/48245", "content": "Black Hat Ethical Hacking\nGoogle Chrome Bug Actively Exploited as Zero-Day\n\nGoogle Chrome Bug Actively Exploited as Zero-DayPost Views: 32 \nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/02/Patreon.png \nReading Time: 2 Minutes\nGoogle issued an update for the bug, which is found in the open-source V8 JavaScript engine.\nGoogle has updated its Stable channel for the desktop version of Chrome, to address a zero-day security vulnerability that\u2019s being actively exploited in the wild.\n\nThe bug, tracked as CVE-2022-1096, is a type-confusion issue in the V8 JavaScript engine, which is an open-source engine used by Chrome and Chromium-based web browsers. Type confusion, as Microsoft has laid out in the past, occurs \u201cwhen a piece of code doesn\u2019t verify the type of object that is passed to it, and uses it blindly without type-checking, it leads to type confusion\u2026Also with type confusion, wrong function pointers or data are fed into the wrong piece of code. In some circumstances this can lead to code execution.\u201d\n\nGoogle didn\u2019t provide additional technical details, as is its wont, but did say that it was \u201caware that an exploit for CVE-2022-1096 exists in the wild.\u201d An anonymous researcher was credited with finding the issue, which is labeled \u201chigh-severity\u201d (no CVSS score was given).\n\nThe lack of any further information is a source of frustration to some.\n\n\u201cAs a defender, I really wish it was more clear what this security fix is,\u201d John Bambenek, principal threat hunter at Netenrich, said via email. \u201cI get permission-denied errors or \u2018need to authenticate,\u2019 so I can\u2019t make decisions or advise my clients. A little more transparency would be beneficial and appreciated.\u201d\nSee Also: Complete Offensive Security and Ethical Hacking Course\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/03/Solutions-1.png Emergency Patch; Active ExploitThe internet giant has updated the Stable channel to 99.0.4844.84 for Chrome for Windows, Mac and Linux, according to the its security advisory. Microsoft, which offers the Chromium-based Edge browser, also issued its own advisory. It\u2019s unclear whether other offerings built in V8, such as the JavaScript runtime environment Node.js, are also affected.\n\nThe patch was issued on an emergency basis, likely due to the active exploit that\u2019s circulating, researchers noted.\n\n\u201cThe first thing which stood out to me about this update is that it only fixes a single issue,\u201d Casey Ellis, founder and CTO at Bugcrowd, noted by email. \u201cThis is pretty unusual for Google. They typically fix multiple issues in these types of releases, which suggests that they are quite concerned and very motivated to see fixes against CVE-2022-1096 applied across their user-base ASAP.\u201d\n\nHe also commented on the speed of the patch being rolled out.\n\n\u201cThe vulnerability was only reported on the 23rd of March, and while Google\u2019s Chrome team do tend to be fairly prompt in developing, testing and rolling patches, the idea of a patch for software deployed as widely deployed as Chrome in 48 hours is something is continue to be impressed by,\u201d he said. \u201cSpeculatively, I\u2019d suggest that the vulnerability has been discovered via detection of active exploitation in the wild, and the combination of impact and potentially the malicious actors currently using it contributed to the fast turnaround.\u201d\nSee Also: Kali Linux 2022.1 Release with Visual Updates, New Tools, Legacy SSH V8 Engine in the CrosshairsThe V8 engine has been plagued with security bugs and targeted by cyberattackers many times in the last year:\n\nLast year delivered a total of these 16 Chrome zero days:\n\n* CVE-2021-21148\u00a0\u2013 Feb. 4, an unnamed type of bug in V8\n* CVE-2021-21224\u00a0\u2013 April 20, an issue with type confusion in V8 that could have allowed a remote attacker t[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:02:02.660388Z"}, {"uuid": "69393d38-de8a-48e9-9fe2-7b7228d37b73", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "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.665949Z"}, {"uuid": "b7cea78a-6af9-43ee-8bfa-9277d62a30ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "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.969268Z"}, {"uuid": "9544c73a-6e35-41af-93e8-7e204bd7fa79", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "seen", "source": "https://t.me/hacking_Attack/8661", "content": "Exploit Collector\nChrome Array Transfer Bypass\n\nhttps://2.bp.blogspot.com/-LETyKySuDgQ/WWlvb4o-z5I/AAAAAAAAIPU/5gCHtKhwhLoet_fHEL-XnPuLlDk7q9atQCLcBGAs/s1600/h76.png \nThe fix for CVE-2021-21148 has added a check in |ValueSerializer::WriteJSArrayBuffer| to make sure non-detachable array buffers cannot be transferred. The check can be bypassed with the help of asm.js and property getters.\n\nMD5 | 2c54899cf0b5cf9ab027a5329061b62e\n\nDownload\nSource:packetstormsecurity.com", "creation_timestamp": "2026-09-02T01:03:18.460344Z"}, {"uuid": "78961f07-75bf-4f68-a1e3-bff196522d85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/hacking_Attack/48245", "content": "Black Hat Ethical Hacking\nGoogle Chrome Bug Actively Exploited as Zero-Day\n\nGoogle Chrome Bug Actively Exploited as Zero-DayPost Views: 32 \nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/02/Patreon.png \nReading Time: 2 Minutes\nGoogle issued an update for the bug, which is found in the open-source V8 JavaScript engine.\nGoogle has updated its Stable channel for the desktop version of Chrome, to address a zero-day security vulnerability that\u2019s being actively exploited in the wild.\n\nThe bug, tracked as CVE-2022-1096, is a type-confusion issue in the V8 JavaScript engine, which is an open-source engine used by Chrome and Chromium-based web browsers. Type confusion, as Microsoft has laid out in the past, occurs \u201cwhen a piece of code doesn\u2019t verify the type of object that is passed to it, and uses it blindly without type-checking, it leads to type confusion\u2026Also with type confusion, wrong function pointers or data are fed into the wrong piece of code. In some circumstances this can lead to code execution.\u201d\n\nGoogle didn\u2019t provide additional technical details, as is its wont, but did say that it was \u201caware that an exploit for CVE-2022-1096 exists in the wild.\u201d An anonymous researcher was credited with finding the issue, which is labeled \u201chigh-severity\u201d (no CVSS score was given).\n\nThe lack of any further information is a source of frustration to some.\n\n\u201cAs a defender, I really wish it was more clear what this security fix is,\u201d John Bambenek, principal threat hunter at Netenrich, said via email. \u201cI get permission-denied errors or \u2018need to authenticate,\u2019 so I can\u2019t make decisions or advise my clients. A little more transparency would be beneficial and appreciated.\u201d\nSee Also: Complete Offensive Security and Ethical Hacking Course\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/03/Solutions-1.png Emergency Patch; Active ExploitThe internet giant has updated the Stable channel to 99.0.4844.84 for Chrome for Windows, Mac and Linux, according to the its security advisory. Microsoft, which offers the Chromium-based Edge browser, also issued its own advisory. It\u2019s unclear whether other offerings built in V8, such as the JavaScript runtime environment Node.js, are also affected.\n\nThe patch was issued on an emergency basis, likely due to the active exploit that\u2019s circulating, researchers noted.\n\n\u201cThe first thing which stood out to me about this update is that it only fixes a single issue,\u201d Casey Ellis, founder and CTO at Bugcrowd, noted by email. \u201cThis is pretty unusual for Google. They typically fix multiple issues in these types of releases, which suggests that they are quite concerned and very motivated to see fixes against CVE-2022-1096 applied across their user-base ASAP.\u201d\n\nHe also commented on the speed of the patch being rolled out.\n\n\u201cThe vulnerability was only reported on the 23rd of March, and while Google\u2019s Chrome team do tend to be fairly prompt in developing, testing and rolling patches, the idea of a patch for software deployed as widely deployed as Chrome in 48 hours is something is continue to be impressed by,\u201d he said. \u201cSpeculatively, I\u2019d suggest that the vulnerability has been discovered via detection of active exploitation in the wild, and the combination of impact and potentially the malicious actors currently using it contributed to the fast turnaround.\u201d\nSee Also: Kali Linux 2022.1 Release with Visual Updates, New Tools, Legacy SSH V8 Engine in the CrosshairsThe V8 engine has been plagued with security bugs and targeted by cyberattackers many times in the last year:\n\nLast year delivered a total of these 16 Chrome zero days:\n\n* CVE-2021-21148\u00a0\u2013 Feb. 4, an unnamed type of bug in V8\n* CVE-2021-21224\u00a0\u2013 April 20, an issue with type confusion in V8 that could have allowed a remote attacker t[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-06T04:00:05.059065Z"}, {"uuid": "f0428620-e2d0-4307-acaa-40459e476d1b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "source": "https://t.me/hacking_Attack/48245", "content": "Black Hat Ethical Hacking\nGoogle Chrome Bug Actively Exploited as Zero-Day\n\nGoogle Chrome Bug Actively Exploited as Zero-DayPost Views: 32 \nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/02/Patreon.png \nReading Time: 2 Minutes\nGoogle issued an update for the bug, which is found in the open-source V8 JavaScript engine.\nGoogle has updated its Stable channel for the desktop version of Chrome, to address a zero-day security vulnerability that\u2019s being actively exploited in the wild.\n\nThe bug, tracked as CVE-2022-1096, is a type-confusion issue in the V8 JavaScript engine, which is an open-source engine used by Chrome and Chromium-based web browsers. Type confusion, as Microsoft has laid out in the past, occurs \u201cwhen a piece of code doesn\u2019t verify the type of object that is passed to it, and uses it blindly without type-checking, it leads to type confusion\u2026Also with type confusion, wrong function pointers or data are fed into the wrong piece of code. In some circumstances this can lead to code execution.\u201d\n\nGoogle didn\u2019t provide additional technical details, as is its wont, but did say that it was \u201caware that an exploit for CVE-2022-1096 exists in the wild.\u201d An anonymous researcher was credited with finding the issue, which is labeled \u201chigh-severity\u201d (no CVSS score was given).\n\nThe lack of any further information is a source of frustration to some.\n\n\u201cAs a defender, I really wish it was more clear what this security fix is,\u201d John Bambenek, principal threat hunter at Netenrich, said via email. \u201cI get permission-denied errors or \u2018need to authenticate,\u2019 so I can\u2019t make decisions or advise my clients. A little more transparency would be beneficial and appreciated.\u201d\nSee Also: Complete Offensive Security and Ethical Hacking Course\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/03/Solutions-1.png Emergency Patch; Active ExploitThe internet giant has updated the Stable channel to 99.0.4844.84 for Chrome for Windows, Mac and Linux, according to the its security advisory. Microsoft, which offers the Chromium-based Edge browser, also issued its own advisory. It\u2019s unclear whether other offerings built in V8, such as the JavaScript runtime environment Node.js, are also affected.\n\nThe patch was issued on an emergency basis, likely due to the active exploit that\u2019s circulating, researchers noted.\n\n\u201cThe first thing which stood out to me about this update is that it only fixes a single issue,\u201d Casey Ellis, founder and CTO at Bugcrowd, noted by email. \u201cThis is pretty unusual for Google. They typically fix multiple issues in these types of releases, which suggests that they are quite concerned and very motivated to see fixes against CVE-2022-1096 applied across their user-base ASAP.\u201d\n\nHe also commented on the speed of the patch being rolled out.\n\n\u201cThe vulnerability was only reported on the 23rd of March, and while Google\u2019s Chrome team do tend to be fairly prompt in developing, testing and rolling patches, the idea of a patch for software deployed as widely deployed as Chrome in 48 hours is something is continue to be impressed by,\u201d he said. \u201cSpeculatively, I\u2019d suggest that the vulnerability has been discovered via detection of active exploitation in the wild, and the combination of impact and potentially the malicious actors currently using it contributed to the fast turnaround.\u201d\nSee Also: Kali Linux 2022.1 Release with Visual Updates, New Tools, Legacy SSH V8 Engine in the CrosshairsThe V8 engine has been plagued with security bugs and targeted by cyberattackers many times in the last year:\n\nLast year delivered a total of these 16 Chrome zero days:\n\n* CVE-2021-21148\u00a0\u2013 Feb. 4, an unnamed type of bug in V8\n* CVE-2021-21224\u00a0\u2013 April 20, an issue with type confusion in V8 that could have allowed a remote attacker t[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-07T01:00:35.689305Z"}, {"uuid": "f6933585-478f-4e2a-bce9-c509ac272f06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "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-07T12:00:03.726613Z"}, {"uuid": "cce7369d-7d67-4f93-8def-f3950677e015", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "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-07T15:00:05.648255Z"}, {"uuid": "b330b417-538d-4a55-bb23-00dfb78f33b4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "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-08T00:00:41.148024Z"}, {"uuid": "981f44f3-fd60-4a92-bf10-e3e1223324a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "exploited", "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-08T00:00:46.160327Z"}, {"uuid": "692da93d-694e-4ecf-be57-94f76e4791de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/8661", "content": "Exploit Collector\nChrome Array Transfer Bypass\n\nhttps://2.bp.blogspot.com/-LETyKySuDgQ/WWlvb4o-z5I/AAAAAAAAIPU/5gCHtKhwhLoet_fHEL-XnPuLlDk7q9atQCLcBGAs/s1600/h76.png \nThe fix for CVE-2021-21148 has added a check in |ValueSerializer::WriteJSArrayBuffer| to make sure non-detachable array buffers cannot be transferred. The check can be bypassed with the help of asm.js and property getters.\n\nMD5 | 2c54899cf0b5cf9ab027a5329061b62e\n\nDownload\nSource:packetstormsecurity.com", "creation_timestamp": "2026-09-08T07:00:05.911549Z"}, {"uuid": "f5d345dc-830a-4da5-adcd-bbf034fe856f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-21148", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/8661", "content": "Exploit Collector\nChrome Array Transfer Bypass\n\nhttps://2.bp.blogspot.com/-LETyKySuDgQ/WWlvb4o-z5I/AAAAAAAAIPU/5gCHtKhwhLoet_fHEL-XnPuLlDk7q9atQCLcBGAs/s1600/h76.png \nThe fix for CVE-2021-21148 has added a check in |ValueSerializer::WriteJSArrayBuffer| to make sure non-detachable array buffers cannot be transferred. The check can be bypassed with the help of asm.js and property getters.\n\nMD5 | 2c54899cf0b5cf9ab027a5329061b62e\n\nDownload\nSource:packetstormsecurity.com", "creation_timestamp": "2026-09-09T00:00:39.155996Z"}]}