{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata — refreshed continuously.","feed_url":"https://feed.craftedsignal.io/products/chrome/","home_page_url":"https://feed.craftedsignal.io/","items":[{"_cs_actors":[],"_cs_cves":[{"cvss":8.8,"id":"CVE-2026-7359"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["high"],"_cs_tags":["use-after-free","chromium","edge","chrome","cve-2026-7359"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7359 describes a use-after-free vulnerability present in ANGLE (Almost Native Graphics Layer Engine), a crucial component of the Chromium open-source project. This vulnerability impacts applications that utilize the Chromium engine, most notably Google Chrome and Microsoft Edge. While the provided source does not give specific exploitation details, use-after-free vulnerabilities can allow for arbitrary code execution. Google Chrome has already addressed this vulnerability, and Microsoft Edge has incorporated the fix from Chromium. This vulnerability matters to defenders because successful exploitation could lead to compromise of the browser and potentially the underlying system.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker crafts a malicious web page containing JavaScript code that leverages a flaw in ANGLE\u0026rsquo;s memory management.\u003c/li\u003e\n\u003cli\u003eA user visits the malicious web page through Chrome or Edge.\u003c/li\u003e\n\u003cli\u003eThe JavaScript code triggers the use-after-free vulnerability by freeing a memory object in ANGLE and then attempting to access it again.\u003c/li\u003e\n\u003cli\u003eThis memory corruption leads to a controlled crash or allows the attacker to overwrite memory with arbitrary data.\u003c/li\u003e\n\u003cli\u003eThe attacker leverages the memory overwrite to inject malicious code into the browser process.\u003c/li\u003e\n\u003cli\u003eThe injected code executes within the context of the browser, granting the attacker access to user data, cookies, and other sensitive information.\u003c/li\u003e\n\u003cli\u003eThe attacker may then use this access to perform actions on behalf of the user, such as stealing credentials, installing malware, or spreading the attack to other systems.\u003c/li\u003e\n\u003cli\u003eThe attacker achieves arbitrary code execution on the user\u0026rsquo;s system, potentially leading to full system compromise.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eA successful exploit of CVE-2026-7359 could allow an attacker to execute arbitrary code within the context of the affected browser (Chrome or Edge). This can lead to sensitive information disclosure, data theft, and potentially full system compromise. The scope of impact is broad, affecting any user who visits a malicious webpage while using a vulnerable version of Chrome or Edge. Since Chrome and Edge are widely used, this vulnerability poses a significant risk.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eDeploy the Sigma rule \u003ccode\u003eDetect Suspicious WebGL Usage\u003c/code\u003e to identify potential exploitation attempts targeting ANGLE via WebGL.\u003c/li\u003e\n\u003cli\u003eMonitor web server logs for suspicious requests (cs-uri-query) that may be related to the exploitation of CVE-2026-7359.\u003c/li\u003e\n\u003cli\u003eEnsure that all Chrome and Edge installations are updated to the latest versions to patch CVE-2026-7359.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:40Z","date_published":"2026-05-01T02:21:40Z","id":"/briefs/2026-05-chromium-use-after-free/","summary":"A use-after-free vulnerability in the ANGLE graphics engine within Chromium (CVE-2026-7359) allows for potential exploitation in Google Chrome and Microsoft Edge.","title":"Chromium Use-After-Free Vulnerability in ANGLE (CVE-2026-7359)","url":"https://feed.craftedsignal.io/briefs/2026-05-chromium-use-after-free/"},{"_cs_actors":[],"_cs_cves":[{"cvss":8.8,"id":"CVE-2026-7339"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["critical"],"_cs_tags":["webrtc","heap-overflow","code-execution","cve-2026-7339"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7339 is a critical heap buffer overflow vulnerability affecting the WebRTC (Web Real-Time Communication) component in Google Chrome and Microsoft Edge (Chromium-based). This vulnerability stems from improper memory management within WebRTC, potentially allowing a remote attacker to execute arbitrary code by crafting malicious web content. As Microsoft Edge ingests Chromium, it is also vulnerable. Users of Chrome and Edge are affected. Defenders should apply available patches promptly to mitigate potential exploitation.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker crafts a malicious website designed to trigger the WebRTC vulnerability.\u003c/li\u003e\n\u003cli\u003eThe victim visits the malicious website using a vulnerable version of Chrome or Edge.\u003c/li\u003e\n\u003cli\u003eThe website uses JavaScript to initiate a WebRTC session.\u003c/li\u003e\n\u003cli\u003eThe crafted WebRTC data triggers a heap buffer overflow during memory allocation within the WebRTC component.\u003c/li\u003e\n\u003cli\u003eThe overflow overwrites adjacent memory regions on the heap.\u003c/li\u003e\n\u003cli\u003eThe attacker carefully crafts the overflow data to overwrite critical program data or function pointers.\u003c/li\u003e\n\u003cli\u003eThe corrupted data leads to arbitrary code execution within the context of the browser process.\u003c/li\u003e\n\u003cli\u003eThe attacker gains control of the user\u0026rsquo;s browser and potentially the underlying system.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of CVE-2026-7339 can lead to arbitrary code execution, allowing an attacker to potentially install malware, steal sensitive information, or take control of the affected system. Given the widespread use of Chrome and Edge, this vulnerability could impact a large number of users across various sectors, including individuals, businesses, and government organizations.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eApply the latest security updates for Google Chrome and Microsoft Edge (Chromium-based) to patch CVE-2026-7339.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026ldquo;Detect WebRTC Heap Overflow Attempt\u0026rdquo; to identify potential exploitation attempts targeting CVE-2026-7339.\u003c/li\u003e\n\u003cli\u003eMonitor web server logs for unusual requests or patterns associated with WebRTC usage that could indicate exploitation attempts.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:27Z","date_published":"2026-05-01T02:21:27Z","id":"/briefs/2026-05-chromium-webrtc-overflow/","summary":"A heap buffer overflow vulnerability exists in the WebRTC component of Google Chrome and Microsoft Edge (Chromium-based), potentially leading to code execution.","title":"CVE-2026-7339: Heap Buffer Overflow in WebRTC","url":"https://feed.craftedsignal.io/briefs/2026-05-chromium-webrtc-overflow/"},{"_cs_actors":[],"_cs_cves":[{"cvss":8.8,"id":"CVE-2026-7355"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["high"],"_cs_tags":["use-after-free","chromium","cve-2026-7355","browser"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7355 is a critical use-after-free vulnerability residing in the Media component of the Chromium browser engine. This vulnerability affects Google Chrome and Microsoft Edge, as Edge incorporates Chromium. A use-after-free vulnerability occurs when an application attempts to use memory after it has been freed, which can lead to crashes, arbitrary code execution, or other unexpected behavior. Successful exploitation could allow an attacker to execute arbitrary code within the context of the browser. This vulnerability was reported and patched by the Chromium project.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker crafts a malicious webpage containing specially crafted media content.\u003c/li\u003e\n\u003cli\u003eA user opens the malicious webpage in a vulnerable version of Chrome or Edge.\u003c/li\u003e\n\u003cli\u003eThe browser attempts to process the malicious media content, triggering the use-after-free vulnerability in the Media component.\u003c/li\u003e\n\u003cli\u003eThe vulnerable code attempts to access a freed memory region.\u003c/li\u003e\n\u003cli\u003eThe attacker gains control of the memory region due to the use-after-free condition.\u003c/li\u003e\n\u003cli\u003eThe attacker injects malicious code into the controlled memory region.\u003c/li\u003e\n\u003cli\u003eThe browser executes the attacker-controlled code.\u003c/li\u003e\n\u003cli\u003eThe attacker achieves arbitrary code execution within the context of the browser process, potentially leading to system compromise.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of CVE-2026-7355 can lead to arbitrary code execution within the context of the browser process. An attacker could potentially gain control of the user\u0026rsquo;s system, steal sensitive information, or install malware. Given the widespread use of Chrome and Edge, a successful exploit could impact a large number of users across various sectors.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eApply the latest security updates for Google Chrome and Microsoft Edge to patch CVE-2026-7355.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026ldquo;Detect Chromium Use-After-Free in Media Component\u0026rdquo; to identify potential exploitation attempts.\u003c/li\u003e\n\u003cli\u003eEnable process creation logging to capture events related to potential exploitation attempts, facilitating detection rule functionality.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:27Z","date_published":"2026-05-01T02:21:27Z","id":"/briefs/2026-05-chromium-uaf/","summary":"CVE-2026-7355 is a use-after-free vulnerability in the Media component of Chromium, affecting Google Chrome and Microsoft Edge, potentially allowing for arbitrary code execution.","title":"Chromium Use-After-Free Vulnerability in Media Component (CVE-2026-7355)","url":"https://feed.craftedsignal.io/briefs/2026-05-chromium-uaf/"},{"_cs_actors":[],"_cs_cves":[{"cvss":7.5,"id":"CVE-2026-7357"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["critical"],"_cs_tags":["use-after-free","chromium","edge","chrome"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7357 is a critical use-after-free vulnerability residing within the GPU component of the Chromium rendering engine. This flaw directly impacts Google Chrome and, due to Microsoft Edge\u0026rsquo;s reliance on Chromium, also affects Edge users. A remote attacker could potentially exploit this vulnerability to execute arbitrary code on a targeted system. The vulnerability stems from improper memory management within the GPU processing routines. While the specific exploitation details are not provided in this brief, successful exploitation generally involves crafting malicious web content to trigger the vulnerability during GPU operations.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAttacker crafts a malicious HTML page containing JavaScript that triggers specific GPU functions.\u003c/li\u003e\n\u003cli\u003eUser visits the malicious website using Chrome or Edge.\u003c/li\u003e\n\u003cli\u003eThe browser\u0026rsquo;s rendering engine processes the malicious JavaScript, leading to the allocation and subsequent freeing of a memory region in the GPU component.\u003c/li\u003e\n\u003cli\u003eThe attacker\u0026rsquo;s JavaScript code then attempts to access the previously freed memory region, triggering the use-after-free vulnerability.\u003c/li\u003e\n\u003cli\u003eBy manipulating the memory layout, the attacker can overwrite the freed memory with controlled data.\u003c/li\u003e\n\u003cli\u003eThe overwritten memory is later accessed by the GPU, leading to the execution of attacker-controlled code.\u003c/li\u003e\n\u003cli\u003eThe attacker gains arbitrary code execution within the context of the browser process.\u003c/li\u003e\n\u003cli\u003eThe attacker leverages the code execution to escalate privileges or perform other malicious activities.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of CVE-2026-7357 can lead to arbitrary code execution on the victim\u0026rsquo;s machine. The attacker could potentially install malware, steal sensitive data, or take control of the affected system. Given the widespread use of Chrome and Edge, this vulnerability poses a significant risk to a large number of users.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eApply the latest security updates for Google Chrome to address CVE-2026-7357.\u003c/li\u003e\n\u003cli\u003eApply the latest security updates for Microsoft Edge to address CVE-2026-7357.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026ldquo;Detect Suspicious WebAssembly Execution\u0026rdquo; to identify potential exploitation attempts involving WebAssembly.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:27Z","date_published":"2026-05-01T02:21:27Z","id":"/briefs/2024-01-chromium-use-after-free/","summary":"CVE-2026-7357 is a use-after-free vulnerability in the GPU component of Chromium that also affects Microsoft Edge, potentially leading to arbitrary code execution.","title":"Chromium Use-After-Free Vulnerability in GPU Component (CVE-2026-7357)","url":"https://feed.craftedsignal.io/briefs/2024-01-chromium-use-after-free/"},{"_cs_actors":[],"_cs_cves":[{"cvss":9.6,"id":"CVE-2026-7333"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["critical"],"_cs_tags":["use-after-free","chromium","gpu","cve-2026-7333","remote code execution"],"_cs_type":"threat","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7333 is a critical use-after-free vulnerability residing in the GPU component of the Chromium browser engine. This flaw allows an attacker to potentially corrupt memory and execute arbitrary code in the context of the browser process. As Microsoft Edge is built upon the Chromium engine, it is also susceptible to this vulnerability. Public details are limited, but exploitation likely involves crafting malicious web content that triggers the use-after-free condition within the GPU processing routines. This vulnerability poses a significant threat as it could allow attackers to compromise user systems simply by visiting a malicious website.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAttacker crafts a malicious HTML page containing JavaScript that interacts with the GPU functionality of the browser.\u003c/li\u003e\n\u003cli\u003eThe user visits the malicious page via a phishing email or drive-by download.\u003c/li\u003e\n\u003cli\u003eThe JavaScript code triggers the use-after-free vulnerability in the Chromium GPU component.\u003c/li\u003e\n\u003cli\u003eThe vulnerability allows the attacker to corrupt memory allocated for GPU processing.\u003c/li\u003e\n\u003cli\u003eThe attacker manipulates memory to gain control of program execution.\u003c/li\u003e\n\u003cli\u003eThe attacker injects malicious code into the browser process.\u003c/li\u003e\n\u003cli\u003eThe injected code executes with the privileges of the browser process, allowing the attacker to perform actions such as stealing cookies, credentials, or installing malware.\u003c/li\u003e\n\u003cli\u003eThe attacker gains persistent access to the compromised system and exfiltrates sensitive data.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eA successful exploitation of CVE-2026-7333 could allow an attacker to execute arbitrary code on a user\u0026rsquo;s system. This could lead to the theft of sensitive information, installation of malware, or complete system compromise. Given the widespread use of Chromium-based browsers such as Chrome and Edge, this vulnerability has the potential to affect millions of users. The impact is considered critical due to the ease of exploitation and the potential for widespread damage.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eApply the latest security updates for Google Chrome and Microsoft Edge to patch CVE-2026-7333.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026ldquo;Detect Suspicious GPU Process Creation\u0026rdquo; to identify potential exploitation attempts.\u003c/li\u003e\n\u003cli\u003eEnable process creation logging with command-line arguments to detect suspicious processes spawned by the browser (logsource: process_creation).\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:27Z","date_published":"2026-05-01T02:21:27Z","id":"/briefs/2024-01-03-chromium-use-after-free/","summary":"CVE-2026-7333 is a use-after-free vulnerability in the GPU component of Chromium, affecting Google Chrome and Microsoft Edge, potentially leading to arbitrary code execution.","title":"Chromium Use-After-Free Vulnerability in GPU Component (CVE-2026-7333)","url":"https://feed.craftedsignal.io/briefs/2024-01-03-chromium-use-after-free/"},{"_cs_actors":[],"_cs_cves":[{"cvss":8.8,"id":"CVE-2026-7348"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["critical"],"_cs_tags":["use-after-free","vulnerability","browser"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7348 is a critical use-after-free vulnerability residing within the Codecs component of the Chromium browser engine. This vulnerability affects applications that utilize the Chromium engine, most notably Google Chrome and Microsoft Edge. While the specific details of the vulnerability are documented in Google Chrome Releases, the underlying issue stems from improper memory management within the Codecs library. Successful exploitation could allow an attacker to execute arbitrary code within the context of the affected browser, potentially leading to data theft, system compromise, or other malicious activities. This vulnerability requires immediate attention from organizations utilizing Chrome or Edge.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker crafts a malicious web page containing specially crafted media content designed to trigger the use-after-free condition in the Codecs library.\u003c/li\u003e\n\u003cli\u003eThe user visits the malicious web page using Google Chrome or Microsoft Edge.\u003c/li\u003e\n\u003cli\u003eThe browser attempts to process the malicious media content, triggering the vulnerable code path within the Codecs library.\u003c/li\u003e\n\u003cli\u003eThe use-after-free condition is triggered when the browser attempts to access memory that has already been freed.\u003c/li\u003e\n\u003cli\u003eThe attacker leverages the use-after-free condition to corrupt memory and gain control of program execution.\u003c/li\u003e\n\u003cli\u003eThe attacker injects and executes arbitrary code within the context of the browser process.\u003c/li\u003e\n\u003cli\u003eThe attacker gains unauthorized access to sensitive data, such as cookies, credentials, or browsing history.\u003c/li\u003e\n\u003cli\u003eThe attacker potentially escalates privileges or installs malware on the user\u0026rsquo;s system.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of CVE-2026-7348 allows an attacker to execute arbitrary code within the context of the affected browser (Chrome or Edge). This can lead to sensitive information disclosure, such as credentials or browsing history. The attacker could potentially gain full control of the user\u0026rsquo;s system. Given the widespread use of Chromium-based browsers, a successful exploit could impact a significant number of users across various sectors.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eUpgrade Google Chrome to the latest version that addresses this vulnerability; refer to \u003ca href=\"https://chromereleases.googleblog.com/2025\"\u003eGoogle Chrome Releases\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003eEnsure Microsoft Edge is updated to the latest version incorporating the Chromium security patch.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026ldquo;Detect Chromium Codecs Use-After-Free Exploit Attempt\u0026rdquo; to identify potential exploitation attempts via webserver logs.\u003c/li\u003e\n\u003cli\u003eEnable webserver logging to capture HTTP requests, which is required for the provided Sigma rule.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:27Z","date_published":"2026-05-01T02:21:27Z","id":"/briefs/2024-01-chromium-cve-2026-7348/","summary":"CVE-2026-7348 is a use-after-free vulnerability in the Codecs component of Chromium, affecting Google Chrome and Microsoft Edge.","title":"Chromium Use-After-Free Vulnerability in Codecs (CVE-2026-7348)","url":"https://feed.craftedsignal.io/briefs/2024-01-chromium-cve-2026-7348/"},{"_cs_actors":[],"_cs_cves":[{"cvss":7.5,"id":"CVE-2026-7349"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["high"],"_cs_tags":["use-after-free","browser","chromium"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7349 is a use-after-free vulnerability found in the Cast component of the Chromium browser engine. This vulnerability affects Google Chrome and, by extension, Microsoft Edge, as Edge is built upon Chromium. Use-after-free vulnerabilities can allow an attacker to execute arbitrary code or cause a denial-of-service. While the original report comes from Chrome, the nature of Chromium\u0026rsquo;s shared codebase means that other Chromium-based browsers are also vulnerable. Successful exploitation of this vulnerability could lead to code execution within the context of the browser process. Defenders need to prioritize patching and monitoring for unusual browser behavior.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker crafts a malicious webpage designed to trigger the use-after-free vulnerability in the Cast component.\u003c/li\u003e\n\u003cli\u003eThe user visits the malicious webpage using a vulnerable version of Chrome or Edge.\u003c/li\u003e\n\u003cli\u003eThe Cast component attempts to access a freed memory location.\u003c/li\u003e\n\u003cli\u003eThe attacker exploits the use-after-free condition to corrupt memory.\u003c/li\u003e\n\u003cli\u003eThe attacker overwrites a function pointer or other critical data structure in memory.\u003c/li\u003e\n\u003cli\u003eThe attacker triggers the execution of the corrupted function pointer or data structure.\u003c/li\u003e\n\u003cli\u003eThe attacker gains arbitrary code execution within the context of the browser process.\u003c/li\u003e\n\u003cli\u003eThe attacker could potentially escalate privileges or perform other malicious activities, such as installing malware or stealing sensitive data.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of CVE-2026-7349 could allow an attacker to execute arbitrary code within the context of the browser, potentially leading to data theft, malware installation, or further system compromise. Given the widespread use of Chrome and Edge, this vulnerability has a significant impact. The specific number of potential victims is dependent on the speed of patching, but could potentially affect millions of users.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eApply the latest security updates for Google Chrome and Microsoft Edge to patch CVE-2026-7349.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rules provided in this brief to your SIEM to detect potential exploitation attempts.\u003c/li\u003e\n\u003cli\u003eMonitor browser process execution for unexpected code loading or memory access patterns using process creation logs.\u003c/li\u003e\n\u003cli\u003eImplement memory protection techniques such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to mitigate the impact of successful exploitation.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:27Z","date_published":"2026-05-01T02:21:27Z","id":"/briefs/2024-01-chrome-cve-2026-7349/","summary":"CVE-2026-7349 is a use-after-free vulnerability in the Cast component of Chromium, affecting Google Chrome and Microsoft Edge.","title":"Chromium Use-After-Free Vulnerability in Cast (CVE-2026-7349)","url":"https://feed.craftedsignal.io/briefs/2024-01-chrome-cve-2026-7349/"},{"_cs_actors":[],"_cs_cves":[{"cvss":7.5,"id":"CVE-2026-7338"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["critical"],"_cs_tags":["use-after-free","chrome","edge","cve-2026-7338","remote code execution"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7338 is a critical use-after-free vulnerability residing within the Cast component of the Chromium browser engine. Google Chrome and Microsoft Edge (Chromium-based) are both affected by this flaw. While the provided source does not specify the exact vulnerable versions, it indicates that Microsoft Edge ingests Chromium, and thus is affected by vulnerabilities addressed in Chromium releases. Successful exploitation of this vulnerability could lead to arbitrary code execution in the context of the user running the browser. This poses a significant risk, as attackers could potentially gain control of the user\u0026rsquo;s system. Defenders should prioritize patching affected browsers.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker crafts a malicious webpage or injects malicious code into a legitimate website that utilizes the Cast functionality.\u003c/li\u003e\n\u003cli\u003eThe victim visits the malicious website or interacts with the compromised legitimate website using an affected browser (Chrome or Edge).\u003c/li\u003e\n\u003cli\u003eThe malicious webpage triggers the use-after-free vulnerability in the Cast component.\u003c/li\u003e\n\u003cli\u003eThe vulnerability allows the attacker to access memory that has already been freed.\u003c/li\u003e\n\u003cli\u003eThe attacker overwrites the freed memory with attacker-controlled data.\u003c/li\u003e\n\u003cli\u003eThe attacker manipulates the memory layout to redirect program execution.\u003c/li\u003e\n\u003cli\u003eThe browser attempts to execute code from the attacker-controlled memory location.\u003c/li\u003e\n\u003cli\u003eThis results in arbitrary code execution within the context of the browser process.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of CVE-2026-7338 allows an attacker to execute arbitrary code on a victim\u0026rsquo;s machine. This can lead to complete system compromise, data theft, installation of malware, or other malicious activities. Given the widespread use of Chromium-based browsers like Chrome and Edge, this vulnerability has the potential to impact a large number of users across various sectors. The severity is critical due to the potential for remote code execution.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eApply the latest security updates for Google Chrome to address CVE-2026-7338 as detailed in Google Chrome Releases.\u003c/li\u003e\n\u003cli\u003eApply the latest security updates for Microsoft Edge (Chromium-based) to address CVE-2026-7338, ensuring the ingested Chromium version contains the fix.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rules provided in this brief to your SIEM to detect potential exploitation attempts targeting the Cast component.\u003c/li\u003e\n\u003cli\u003eEnable enhanced browser security features, such as sandboxing and site isolation, to limit the impact of potential exploits.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:27Z","date_published":"2026-05-01T02:21:27Z","id":"/briefs/2024-01-chromium-cve-2026-7338/","summary":"CVE-2026-7338 is a use-after-free vulnerability in the Cast component of Chromium, affecting Google Chrome and Microsoft Edge, potentially leading to arbitrary code execution.","title":"Chromium Use-After-Free Vulnerability in Cast (CVE-2026-7338)","url":"https://feed.craftedsignal.io/briefs/2024-01-chromium-cve-2026-7338/"},{"_cs_actors":[],"_cs_cves":[{"cvss":8.3,"id":"CVE-2026-7353"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge"],"_cs_severities":["critical"],"_cs_tags":["heap overflow","chromium","cve-2026-7353"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7353 is a critical heap buffer overflow vulnerability residing within the Skia graphics library, a core component of the Chromium open-source project. This vulnerability impacts applications that utilize Chromium, including Google Chrome and Microsoft Edge. While the specific details of exploitation are not provided in this brief, the nature of a heap buffer overflow suggests a high potential for arbitrary code execution. Successful exploitation could allow an attacker to gain control of the affected browser process. Given the widespread use of Chromium-based browsers, this vulnerability poses a significant risk to a large user base. Defenders should prioritize patching and consider implementing mitigations to detect and prevent potential exploitation attempts.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker crafts a malicious web page or injects malicious content into a trusted website.\u003c/li\u003e\n\u003cli\u003eThe victim visits the malicious web page or interacts with the injected content using a Chromium-based browser (Chrome or Edge).\u003c/li\u003e\n\u003cli\u003eThe browser\u0026rsquo;s rendering engine, utilizing the Skia library, processes the malicious content, triggering the heap buffer overflow in Skia.\u003c/li\u003e\n\u003cli\u003eThe overflow allows the attacker to overwrite adjacent memory regions in the heap.\u003c/li\u003e\n\u003cli\u003eBy carefully crafting the overflowed data, the attacker can overwrite critical data structures within the browser process.\u003c/li\u003e\n\u003cli\u003eThe attacker gains control of the execution flow by overwriting function pointers or other control data.\u003c/li\u003e\n\u003cli\u003eThe attacker executes arbitrary code within the context of the browser process.\u003c/li\u003e\n\u003cli\u003eThe attacker could then perform actions such as installing malware, stealing sensitive data, or further compromising the system.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of CVE-2026-7353 allows for arbitrary code execution within the context of the affected browser process. This can lead to a complete compromise of the user\u0026rsquo;s browser session, potentially enabling the attacker to steal credentials, inject malicious code into other websites, or install malware on the victim\u0026rsquo;s system. Given the widespread use of Chrome and Edge, the potential impact is significant, affecting potentially millions of users.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eApply the latest security updates for Google Chrome and Microsoft Edge to patch CVE-2026-7353.\u003c/li\u003e\n\u003cli\u003eDeploy the following Sigma rule to detect potential exploitation attempts based on suspicious process execution originating from the browser (see \u0026ldquo;Detect Suspicious Process Creation from Browser\u0026rdquo;).\u003c/li\u003e\n\u003cli\u003eEnable enhanced browser security features such as site isolation to mitigate the impact of successful exploitation.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-01T02:21:27Z","date_published":"2026-05-01T02:21:27Z","id":"/briefs/2026-05-chromium-heap-overflow/","summary":"CVE-2026-7353 is a heap buffer overflow vulnerability in the Skia graphics library used by Chromium, affecting both Google Chrome and Microsoft Edge.","title":"Chromium Heap Buffer Overflow Vulnerability (CVE-2026-7353)","url":"https://feed.craftedsignal.io/briefs/2026-05-chromium-heap-overflow/"},{"_cs_actors":[],"_cs_cves":[{"cvss":9.6,"id":"CVE-2026-6296"},{"cvss":8.3,"id":"CVE-2026-6297"},{"cvss":4.3,"id":"CVE-2026-6298"},{"cvss":8.8,"id":"CVE-2026-6299"},{"cvss":8.8,"id":"CVE-2026-6300"}],"_cs_exploited":false,"_cs_products":["Chrome"],"_cs_severities":["high"],"_cs_tags":["chrome","vulnerability","code-execution","defense-evasion","information-disclosure","denial-of-service"],"_cs_type":"advisory","_cs_vendors":["Google"],"content_html":"\u003cp\u003eMultiple unspecified vulnerabilities have been identified in Google Chrome. An attacker exploiting these vulnerabilities could potentially execute arbitrary code, circumvent security measures, expose and manipulate sensitive information, and trigger a denial-of-service condition. The specifics of these vulnerabilities, including CVE identifiers, are not detailed in the source document. The lack of detail makes it difficult to determine the scope of the attack, but successful exploitation could lead to significant compromise of systems running Chrome. Defenders should prioritize monitoring for suspicious activity within Chrome processes.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker identifies a vulnerable version of Google Chrome.\u003c/li\u003e\n\u003cli\u003eThe attacker crafts a malicious web page or injects malicious code into a legitimate website.\u003c/li\u003e\n\u003cli\u003eA user visits the malicious web page or a compromised legitimate website using Google Chrome.\u003c/li\u003e\n\u003cli\u003eThe attacker exploits a vulnerability in Chrome, such as a use-after-free or buffer overflow.\u003c/li\u003e\n\u003cli\u003eSuccessful exploitation allows the attacker to execute arbitrary code within the context of the Chrome process.\u003c/li\u003e\n\u003cli\u003eThe attacker leverages the code execution to bypass security mechanisms like sandboxing.\u003c/li\u003e\n\u003cli\u003eThe attacker gains access to sensitive data, such as cookies, browsing history, or credentials.\u003c/li\u003e\n\u003cli\u003eThe attacker manipulates data or causes a denial-of-service condition by crashing the browser or consuming excessive resources.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of these vulnerabilities could allow an attacker to execute arbitrary code, bypass security mechanisms, disclose and manipulate data, and cause a denial-of-service condition. The impact ranges from data theft and credential compromise to complete system takeover, depending on the specific vulnerability and the attacker\u0026rsquo;s objectives. While the exact number of potential victims is unknown, the widespread use of Chrome makes this a high-impact threat.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eMonitor process creation events for suspicious child processes spawned by chrome.exe, especially those involving command-line interpreters or scripting engines. Use the \u0026ldquo;Detect Suspicious Child Process of Chrome\u0026rdquo; Sigma rule.\u003c/li\u003e\n\u003cli\u003eInspect network connections originating from chrome.exe for unusual destinations or protocols. Deploy the \u0026ldquo;Detect Outbound Connection from Chrome without User Interaction\u0026rdquo; Sigma rule.\u003c/li\u003e\n\u003cli\u003eImplement web content filtering to block access to known malicious websites that might attempt to exploit Chrome vulnerabilities.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-04-30T09:09:14Z","date_published":"2026-04-30T09:09:14Z","id":"/briefs/2026-05-chrome-vulns/","summary":"Multiple vulnerabilities in Google Chrome could allow an attacker to execute arbitrary code, bypass security mechanisms, disclose and manipulate data, and cause a denial-of-service condition.","title":"Multiple Vulnerabilities in Google Chrome","url":"https://feed.craftedsignal.io/briefs/2026-05-chrome-vulns/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["OneDrive","Chrome","Brave","Opera","Discord","Slack","Microsoft 365","SharePoint"],"_cs_severities":["medium"],"_cs_tags":["command-and-control","windows","threat-detection"],"_cs_type":"advisory","_cs_vendors":["Microsoft","Google","Brave Software","Opera","Discord","Slack"],"content_html":"\u003cp\u003eAdversaries may implement command and control (C2) communications that use common web services to hide their activity. This attack technique is typically targeted at an organization and uses web services common to the victim network, which allows the adversary to blend into legitimate traffic activity. These popular services are typically targeted since they have most likely been used before compromise, which helps malicious traffic blend in. This detection focuses on identifying connections from Windows hosts to a predefined list of commonly abused web services from processes running outside of typical program installation directories, indicating a potential C2 channel leveraging legitimate services. The rule aims to detect this behavior by monitoring network connections and DNS requests originating from unusual locations.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eInitial access is achieved via an unknown method (e.g., phishing, exploit).\u003c/li\u003e\n\u003cli\u003eMalware is installed on the victim\u0026rsquo;s system, likely outside typical program directories.\u003c/li\u003e\n\u003cli\u003eThe malware establishes a DNS connection to a commonly abused web service (e.g., pastebin.com, raw.githubusercontent.com) to obscure C2 traffic.\u003c/li\u003e\n\u003cli\u003eThe malware sends encrypted or encoded commands to the web service.\u003c/li\u003e\n\u003cli\u003eThe web service acts as an intermediary, relaying the commands to the attacker\u0026rsquo;s C2 server.\u003c/li\u003e\n\u003cli\u003eThe C2 server responds with instructions, which are then relayed back to the compromised host through the same web service.\u003c/li\u003e\n\u003cli\u003eThe malware executes the received commands, potentially leading to data exfiltration, lateral movement, or other malicious activities.\u003c/li\u003e\n\u003cli\u003eThe attacker maintains persistent access and control over the compromised system using the web service as a hidden C2 channel.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation can lead to data theft, system compromise, and further propagation within the network. Since commonly used web services are utilized, the malicious activity can blend in with legitimate network traffic, making it difficult to detect. The impact can range from minor data breaches to complete network compromise, depending on the attacker\u0026rsquo;s objectives and the level of access gained.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eDeploy the Sigma rule \u003ccode\u003eDetect Commonly Abused Web Services via DNS\u003c/code\u003e to your SIEM to identify suspicious DNS queries to known C2 web services originating from anomalous processes.\u003c/li\u003e\n\u003cli\u003eEnable DNS query logging on Windows endpoints to provide the data source required for the Sigma rule.\u003c/li\u003e\n\u003cli\u003eReview network connection logs for processes outside standard installation directories communicating with domains listed in the \u003ccode\u003equery\u003c/code\u003e section of the Sigma rule to identify potential C2 activity.\u003c/li\u003e\n\u003cli\u003eImplement network segmentation to limit the potential impact of compromised hosts.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-04T12:00:00Z","date_published":"2024-01-04T12:00:00Z","id":"/briefs/2024-01-04-c2-web-services/","summary":"This rule detects command and control activity using common web services by identifying Windows hosts making DNS requests to a list of commonly abused web services from processes outside of known program locations, potentially indicating adversaries attempting to blend malicious traffic with legitimate network activity.","title":"Detection of Command and Control Activity via Commonly Abused Web Services","url":"https://feed.craftedsignal.io/briefs/2024-01-04-c2-web-services/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Edge","Chrome","Elastic Defend","Microsoft Defender XDR","SentinelOne Cloud Funnel"],"_cs_severities":["high"],"_cs_tags":["credential-access","windows","browser-exploitation"],"_cs_type":"advisory","_cs_vendors":["Microsoft","Google","Elastic","SentinelOne"],"content_html":"\u003cp\u003eThis detection identifies instances where a browser process, specifically Google Chrome or Microsoft Edge, is initiated from an unexpected parent process on a Windows system. The rule focuses on scenarios where browsers are launched with arguments indicative of remote debugging, headless automation, or minimal user interaction. Such activity can signal an attempt to manipulate a browser session for malicious purposes, potentially leading to credential theft or unauthorized access to sensitive information. The rule is designed to leverage data from Elastic Defend, Microsoft Defender XDR, SentinelOne Cloud Funnel, Sysmon, and Windows Process Creation Logs.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker gains initial access to a Windows system (e.g., via phishing or exploiting a vulnerability).\u003c/li\u003e\n\u003cli\u003eThe attacker executes a script or command to launch a browser process (chrome.exe or msedge.exe).\u003c/li\u003e\n\u003cli\u003eThe browser is launched with specific command-line arguments, such as \u003ccode\u003e--remote-debugging-port\u003c/code\u003e, \u003ccode\u003e--headless\u003c/code\u003e, or \u003ccode\u003e--window-position=-x,-y\u003c/code\u003e, to enable remote control or hide the browser window.\u003c/li\u003e\n\u003cli\u003eThe parent process of the browser is an unusual executable, not typically associated with launching browsers (e.g., not explorer.exe).\u003c/li\u003e\n\u003cli\u003eThe attacker leverages the remote debugging port to interact with the browser session programmatically.\u003c/li\u003e\n\u003cli\u003eThe attacker attempts to steal credentials or session cookies from the browser.\u003c/li\u003e\n\u003cli\u003eThe attacker uses stolen credentials to access sensitive data.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation can lead to the theft of user credentials, enabling unauthorized access to sensitive data and systems. This could result in financial loss, data breaches, and reputational damage for affected organizations. The targeted use of browser manipulation techniques increases the likelihood of bypassing traditional security controls.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eDeploy the Sigma rule \u003ccode\u003eBrowser Process Spawned from Unusual Parent\u003c/code\u003e to your SIEM and tune for your environment.\u003c/li\u003e\n\u003cli\u003eEnable Sysmon process-creation logging (Event ID 1) to collect the necessary data for the Sigma rule.\u003c/li\u003e\n\u003cli\u003eInvestigate any alerts generated by the \u003ccode\u003eBrowser Process Spawned from Unusual Parent\u003c/code\u003e Sigma rule.\u003c/li\u003e\n\u003cli\u003eReview process command lines for arguments like \u003ccode\u003e--remote-debugging-port\u003c/code\u003e or \u003ccode\u003e--headless\u003c/code\u003e to identify potential browser manipulation attempts.\u003c/li\u003e\n\u003cli\u003eMonitor network connections originating from browser processes for unexpected destinations, as described in the investigation guide from the source.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-03T18:15:00Z","date_published":"2024-01-03T18:15:00Z","id":"/briefs/2024-01-browser-unusual-parent/","summary":"Attackers may attempt credential theft by launching browsers (Chrome, Edge) with remote debugging, headless automation, or minimal arguments from an unusual parent process on Windows systems.","title":"Browser Process Spawned from an Unusual Parent","url":"https://feed.craftedsignal.io/briefs/2024-01-browser-unusual-parent/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Elastic Defend","SentinelOne Cloud Funnel","OneDrive","Chrome","Opera","Fiddler","PowerToys","Vivaldi","Zen Browser","WaveBrowser","MicrosoftEdgeCP"],"_cs_severities":["low"],"_cs_tags":["command-and-control","webservice","windows"],"_cs_type":"advisory","_cs_vendors":["Elastic","Microsoft","Google","BraveSoftware","Opera","Vivaldi","Wavesor Software","Discord","Telegram","Facebook","Trello","GitHub","Supabase"],"content_html":"\u003cp\u003eThis detection rule, sourced from Elastic, identifies potential command and control (C2) activity by detecting connections to commonly abused web services. Adversaries often leverage popular web services like pastebin, GitHub, Dropbox, and Discord to mask malicious communications within legitimate network traffic. This technique makes it challenging for defenders to distinguish between normal user activity and malicious C2 traffic. The rule focuses on Windows systems and monitors DNS queries to identify processes communicating with a predefined list of services known to be abused by attackers. The rule was last updated on 2026-05-04 and is designed to work with data from Elastic Defend and SentinelOne Cloud Funnel. The goal is to identify anomalous network connections originating from unusual processes.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eA user on a Windows host unknowingly executes a malicious file (e.g., via phishing or drive-by download).\u003c/li\u003e\n\u003cli\u003eThe malicious file executes a process outside of typical program directories (e.g., \u003ccode\u003eC:\\Windows\\Temp\u003c/code\u003e).\u003c/li\u003e\n\u003cli\u003eThis process initiates a DNS query to a domain associated with a commonly abused web service (e.g., \u003ccode\u003epastebin.com\u003c/code\u003e, \u003ccode\u003egithubusercontent.com\u003c/code\u003e).\u003c/li\u003e\n\u003cli\u003eThe DNS query resolves to an IP address, and a network connection is established to the web service.\u003c/li\u003e\n\u003cli\u003eThe malicious process uploads or downloads data from the web service, potentially containing commands for the compromised host or exfiltrated data.\u003c/li\u003e\n\u003cli\u003eThe web service acts as an intermediary, relaying commands from the attacker to the compromised host or exfiltrated data from the compromised host to the attacker.\u003c/li\u003e\n\u003cli\u003eThe attacker uses the C2 channel to perform further actions on the compromised host, such as lateral movement or data theft.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eA successful attack using common web services for C2 can lead to data exfiltration, system compromise, and further propagation within the network. The low severity suggests a focus on detecting early-stage C2 activity, which if left unchecked, could escalate into a significant incident. The usage of popular web services makes detection difficult, requiring careful analysis and tuning to avoid false positives.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026ldquo;Connection to Commonly Abused Web Services\u0026rdquo; to your SIEM and tune it for your environment to minimize false positives.\u003c/li\u003e\n\u003cli\u003eEnable Sysmon DNS query logging to accurately capture DNS requests for improved detection capabilities, activating the \u0026ldquo;DNS Query to Commonly Abused Web Services\u0026rdquo; rule.\u003c/li\u003e\n\u003cli\u003eInvestigate any alerts generated by this rule, focusing on the process execution chain and network connections to determine the legitimacy of the activity, referencing the investigation steps described in the rule documentation.\u003c/li\u003e\n\u003cli\u003eReview and update the list of excluded processes in the Sigma rule to reflect your organization\u0026rsquo;s approved software and reduce false positives.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-03T15:00:00Z","date_published":"2024-01-03T15:00:00Z","id":"/briefs/2024-01-common-web-services-c2/","summary":"This rule detects command and control (C2) communications that use common web services to hide malicious activity on Windows hosts by identifying network connections to commonly abused web services from processes outside of known legitimate program locations, indicating potential exfiltration or C2 activity blended with legitimate traffic.","title":"Detection of Command and Control Activity via Common Web Services","url":"https://feed.craftedsignal.io/briefs/2024-01-common-web-services-c2/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Elastic Defend","SentinelOne Cloud Funnel","Corretto JDK","UEM Proxy Server","UEM Core","dbeaver.exe","Docker","Chrome","Internet Explorer","PyCharm Community Edition","Firefox","VirtualBox","Puppet","nexpose","Silverfort AD Adapter","Nessus","VMware View","Advanced Port Scanner","DesktopCentral Agent","LanGuard","SAP BusinessObjects","SuperScan","ZSATunnel"],"_cs_severities":["medium"],"_cs_tags":["kerberoasting","credential-access","lateral-movement","windows"],"_cs_type":"threat","_cs_vendors":["Elastic","SentinelOne","Amazon","BlackBerry","DBeaver","Docker","Google","Microsoft","JetBrains","Mozilla","Oracle","Puppet Labs","Rapid7","Silverfort","Tenable","VMware","GFI","SAP","Zscaler"],"content_html":"\u003cp\u003eThis detection identifies unusual processes initiating network connections to the standard Kerberos port (88) on Windows systems. Typically, the \u003ccode\u003elsass.exe\u003c/code\u003e process handles Kerberos traffic on domain-joined hosts. The rule aims to detect processes other than \u003ccode\u003elsass.exe\u003c/code\u003e communicating with the Kerberos port, which could indicate malicious activity such as Kerberoasting (T1558.003) or Pass-the-Ticket (T1550.003). The detection is designed to work with data from Elastic Defend and SentinelOne Cloud Funnel. This can help security teams identify potential credential access attempts and lateral movement within the network.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker compromises a user account or system within the domain.\u003c/li\u003e\n\u003cli\u003eThe attacker executes a malicious binary or script (e.g., PowerShell) on the compromised system.\u003c/li\u003e\n\u003cli\u003eThe malicious process attempts to request Kerberos service tickets (TGS) for various services within the domain. This is done by connecting to the Kerberos port (88) on a domain controller.\u003c/li\u003e\n\u003cli\u003eThe attacker uses tools like \u003ccode\u003eRubeus\u003c/code\u003e or \u003ccode\u003eKerberoast.ps1\u003c/code\u003e to enumerate and request TGS tickets.\u003c/li\u003e\n\u003cli\u003eThe unusual process (not \u003ccode\u003elsass.exe\u003c/code\u003e) sends Kerberos traffic to the domain controller.\u003c/li\u003e\n\u003cli\u003eThe attacker extracts the Kerberos tickets from memory or network traffic.\u003c/li\u003e\n\u003cli\u003eThe attacker cracks the offline TGS tickets to obtain service account passwords (Kerberoasting).\u003c/li\u003e\n\u003cli\u003eThe attacker uses the compromised service account credentials to move laterally within the network or access sensitive data.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eA successful Kerberoasting or Pass-the-Ticket attack can lead to unauthorized access to sensitive resources and lateral movement within the network. Attackers can compromise service accounts with elevated privileges, potentially leading to domain-wide compromise. Detection of this behavior can prevent attackers from gaining access to critical assets. While the exact number of victims and sectors targeted are unknown, this technique is widely used by various threat actors in targeted attacks.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eDeploy the \u0026ldquo;Kerberos Traffic from Unusual Process\u0026rdquo; Sigma rule to your SIEM and tune for your environment. Enable network connection logging to capture the necessary traffic.\u003c/li\u003e\n\u003cli\u003eInvestigate any alerts triggered by the Sigma rule, focusing on the process execution chain and potential malicious binaries.\u003c/li\u003e\n\u003cli\u003eReview event ID 4769 for suspicious ticket requests as mentioned in the rule\u0026rsquo;s documentation.\u003c/li\u003e\n\u003cli\u003eExamine host services for suspicious entries as outlined in the original Elastic detection rule using Osquery.\u003c/li\u003e\n\u003cli\u003eMonitor for processes connecting to port 88, filtering out legitimate Kerberos clients like \u003ccode\u003elsass.exe\u003c/code\u003e, using the \u0026ldquo;Detect Kerberos Traffic from Non-Standard Process\u0026rdquo; Sigma rule.\u003c/li\u003e\n\u003cli\u003eInvestigate processes identified by the rule and compare them to the list of legitimate processes to identify unauthorized connections to the Kerberos port.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-03T14:00:00Z","date_published":"2024-01-03T14:00:00Z","id":"/briefs/2024-01-03-kerberoasting-unusual-process/","summary":"Detects network connections to the standard Kerberos port from an unusual process other than lsass.exe, potentially indicating Kerberoasting or Pass-the-Ticket activity on Windows systems.","title":"Kerberos Traffic from Unusual Process","url":"https://feed.craftedsignal.io/briefs/2024-01-03-kerberoasting-unusual-process/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Chrome","Splunk Enterprise Security","Splunk Enterprise","Splunk Cloud"],"_cs_severities":["high"],"_cs_tags":["credential-access","password-stealing","chrome"],"_cs_type":"advisory","_cs_vendors":["Google","Splunk"],"content_html":"\u003cp\u003eThis threat brief focuses on detecting unauthorized access to the Chrome \u0026lsquo;Local State\u0026rsquo; file, a critical component of the Chrome browser that stores settings and, more importantly, the encrypted master key used to protect saved passwords. The \u0026lsquo;Local State\u0026rsquo; file is typically accessed only by the Chrome browser itself. When other processes attempt to read this file, it\u0026rsquo;s a strong indicator of malicious activity, potentially involving credential theft or reconnaissance by malware such as RedLine Stealer. This analytic leverages Windows Security Event logs, specifically event code 4663, to identify this behavior. Detecting and responding to this activity is crucial for preventing attackers from gaining access to sensitive user credentials stored within the Chrome browser.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eThe attacker gains initial access to the system, often through phishing or exploitation of a software vulnerability (not specified in this advisory).\u003c/li\u003e\n\u003cli\u003eMalware is deployed on the victim machine (e.g., RedLine Stealer).\u003c/li\u003e\n\u003cli\u003eThe malware attempts to locate the Chrome \u0026lsquo;Local State\u0026rsquo; file, typically found at \u003ccode\u003e*\\\\AppData\\\\Local\\\\Google\\\\Chrome\\\\User Data\\\\Local State\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003eThe malware process accesses the \u0026lsquo;Local State\u0026rsquo; file, triggering a Windows Security Event 4663.\u003c/li\u003e\n\u003cli\u003eThe malware extracts the encrypted master key from the \u0026lsquo;Local State\u0026rsquo; file.\u003c/li\u003e\n\u003cli\u003eThe malware decrypts the master key using attacker-controlled methods.\u003c/li\u003e\n\u003cli\u003eThe decrypted master key is used to decrypt saved passwords stored by Chrome.\u003c/li\u003e\n\u003cli\u003eThe stolen credentials are exfiltrated to the attacker\u0026rsquo;s command and control server.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation allows attackers to steal user credentials stored in the Chrome browser. This can lead to unauthorized access to email accounts, social media profiles, banking websites, and other sensitive online services. The impact could range from identity theft and financial fraud to corporate espionage and data breaches. The number of potential victims depends on the number of systems compromised and the extent of Chrome usage on those systems.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eEnable \u0026ldquo;Audit Object Access\u0026rdquo; in Group Policy and configure auditing for both \u0026ldquo;Success\u0026rdquo; and \u0026ldquo;Failure\u0026rdquo; events to ensure Windows Security Event 4663 is generated for file access, as described in the \u0026ldquo;how_to_implement\u0026rdquo; section.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u0026ldquo;Detect Chrome Local State File Access by Non-Chrome Processes\u0026rdquo; to your SIEM to detect unauthorized access attempts (see \u0026ldquo;rules\u0026rdquo; section). Tune the rule\u0026rsquo;s filter list to reduce false positives related to legitimate software uninstallers.\u003c/li\u003e\n\u003cli\u003eInvestigate any alerts generated by the Sigma rule, focusing on identifying the process name and path involved in accessing the \u0026lsquo;Local State\u0026rsquo; file, as described in the rule\u0026rsquo;s description.\u003c/li\u003e\n\u003cli\u003eConsider implementing network egress filtering to prevent exfiltration of stolen credentials to known malicious command and control servers.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-03T12:00:00Z","date_published":"2024-01-03T12:00:00Z","id":"/briefs/2024-01-chrome-localstate-access/","summary":"Detection of non-Chrome processes accessing the Chrome 'Local State' file, potentially leading to extraction of the master key used for decrypting saved passwords.","title":"Unauthorized Access to Chrome Local State File","url":"https://feed.craftedsignal.io/briefs/2024-01-chrome-localstate-access/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Elastic Defend","Sysmon","Chrome","Edge","Firefox","Safari","Brave Browser","Opera Browser","Vivaldi Browser","WebView2"],"_cs_severities":["medium"],"_cs_tags":["command-and-control","rmm","dns"],"_cs_type":"advisory","_cs_vendors":["Elastic","Microsoft","Mozilla","Apple","Brave","Opera","Vivaldi"],"content_html":"\u003cp\u003eThis detection identifies potentially malicious use of Remote Monitoring and Management (RMM) tools by detecting DNS queries to known RMM domains originating from processes that are not web browsers. Attackers frequently abuse legitimate RMM software for command and control, persistence, and lateral movement within compromised networks. This rule focuses on surfacing RMM clients, scripts, or other non-browser activity contacting these services, thereby increasing the likelihood of detecting unauthorized remote access or malicious activity. The rule aims to reduce false positives by excluding common browser processes and focusing on unusual network activity. The identified domains are associated with various RMM tools like TeamViewer, AnyDesk, and ScreenConnect. This detection is relevant for organizations concerned about insider threats, supply chain attacks, or general compromise leading to unauthorized remote access.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker gains initial access to a system, possibly through phishing or exploiting a vulnerability.\u003c/li\u003e\n\u003cli\u003eThe attacker installs an unauthorized RMM tool (e.g., using a script or installer).\u003c/li\u003e\n\u003cli\u003eThe RMM tool initiates a DNS query to resolve its command and control domain (e.g., teamviewer.com).\u003c/li\u003e\n\u003cli\u003eThe system, now running the RMM agent, establishes a connection to the attacker-controlled RMM server.\u003c/li\u003e\n\u003cli\u003eThe attacker uses the RMM tool to execute commands on the compromised system.\u003c/li\u003e\n\u003cli\u003eThe attacker uses the RMM tool for lateral movement within the network.\u003c/li\u003e\n\u003cli\u003eThe attacker uses the RMM tool to maintain persistence on the compromised system.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eCompromise via unauthorized RMM tools can provide attackers with persistent remote access, enabling them to perform a range of malicious activities, including data theft, ransomware deployment, and further lateral movement within the network. Successful exploitation can lead to significant financial loss, reputational damage, and disruption of business operations. The number of affected systems can vary depending on the scope of the initial compromise and the attacker\u0026rsquo;s ability to move laterally.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eDeploy the Sigma rule \u003ccode\u003eRMM Domain DNS Queries from Non-Browser Processes\u003c/code\u003e to your SIEM and tune it to your environment, excluding legitimate non-browser processes that use RMM tools.\u003c/li\u003e\n\u003cli\u003eInvestigate any alerts generated by the rule, focusing on identifying the process making the DNS query and its parent process, as outlined in the rule\u0026rsquo;s description.\u003c/li\u003e\n\u003cli\u003eMonitor DNS query logs for queries to the RMM domains listed in the IOC table, and block them at the DNS resolver if unauthorized RMM use is confirmed.\u003c/li\u003e\n\u003cli\u003eEnable Sysmon Event ID 22 (DNS Query) logging to provide the necessary data for this detection, as recommended in the \u0026ldquo;Setup\u0026rdquo; section of the content.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-03T12:00:00Z","date_published":"2024-01-03T12:00:00Z","id":"/briefs/2024-01-rmm-domain-dns/","summary":"Detects DNS queries to commonly abused remote monitoring and management (RMM) or remote access software domains from non-browser processes, potentially indicating unauthorized remote access or command and control activity.","title":"RMM Domain DNS Queries from Non-Browser Processes","url":"https://feed.craftedsignal.io/briefs/2024-01-rmm-domain-dns/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Chrome","Splunk Enterprise","Splunk Enterprise Security","Splunk Cloud"],"_cs_severities":["high"],"_cs_tags":["credential-access","password-stealing","windows"],"_cs_type":"advisory","_cs_vendors":["Google","Splunk"],"content_html":"\u003cp\u003eThis threat brief focuses on detecting unauthorized access to Chrome\u0026rsquo;s \u0026ldquo;Login Data\u0026rdquo; file, a local SQLite database that stores user credentials. Attackers, after gaining initial access to a Windows system, may attempt to steal these credentials by directly accessing and parsing this file. The \u0026ldquo;Login Data\u0026rdquo; file contains sensitive information, including usernames, passwords, and URLs. The technique is commonly associated with credential-stealing malware families like RedLine Stealer, DarkGate, and others listed below. Successful exploitation allows attackers to harvest credentials for lateral movement and further compromise. This detection is based on Windows Security Event logs, specifically event ID 4663, which records attempts to access objects like files.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eThe attacker gains initial access to the target system, potentially through phishing or exploiting a software vulnerability.\u003c/li\u003e\n\u003cli\u003eThe attacker executes a malicious executable or script on the compromised system.\u003c/li\u003e\n\u003cli\u003eThe malicious process attempts to access the Chrome \u0026ldquo;Login Data\u0026rdquo; file, typically located at \u003ccode\u003e*\\\\AppData\\\\Local\\\\Google\\\\Chrome\\\\User Data\\\\Default\\\\Login Data\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003eWindows Security Event Log generates an event with EventCode 4663, recording the file access attempt.\u003c/li\u003e\n\u003cli\u003eThe attacker\u0026rsquo;s process reads the \u0026ldquo;Login Data\u0026rdquo; SQLite database.\u003c/li\u003e\n\u003cli\u003eThe attacker extracts and potentially decrypts stored usernames and passwords from the \u0026ldquo;Login Data\u0026rdquo; file.\u003c/li\u003e\n\u003cli\u003eThe attacker uses the stolen credentials for lateral movement within the network.\u003c/li\u003e\n\u003cli\u003eThe attacker achieves their final objective, such as data exfiltration or ransomware deployment.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eCompromised Chrome \u0026ldquo;Login Data\u0026rdquo; files can lead to widespread credential theft, granting attackers unauthorized access to numerous online accounts. Depending on the user\u0026rsquo;s browsing habits and password reuse, this can include access to sensitive corporate resources, financial accounts, and personal email. The impact can range from financial loss to significant data breaches and reputational damage. The references section in the original source mentions Redline Stealer which is used in various attacks, indicating a potentially large number of victims across different sectors.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eEnable \u0026ldquo;Audit Object Access\u0026rdquo; in Group Policy and configure auditing for both \u0026ldquo;Success\u0026rdquo; and \u0026ldquo;Failure\u0026rdquo; events to generate Windows Security Event 4663, as described in the \u0026ldquo;how_to_implement\u0026rdquo; section.\u003c/li\u003e\n\u003cli\u003eDeploy the Sigma rule \u003ccode\u003eChrome Login Data Accessed by Non-Browser Process\u003c/code\u003e to your SIEM and tune the \u003ccode\u003eprocess_path\u003c/code\u003e filter to exclude legitimate software in your environment.\u003c/li\u003e\n\u003cli\u003eInvestigate any alerts generated by the \u003ccode\u003eChrome Login Data Accessed by Non-Browser Process\u003c/code\u003e Sigma rule to determine if credential theft has occurred and remediate any affected accounts.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-03T12:00:00Z","date_published":"2024-01-03T12:00:00Z","id":"/briefs/2024-01-chrome-login-data-access/","summary":"This analytic identifies non-Chrome processes accessing the Chrome user data file 'login data', which is an SQLite database containing sensitive information like saved passwords, potentially leading to credential theft.","title":"Non-Chrome Process Accessing Chrome Login Data","url":"https://feed.craftedsignal.io/briefs/2024-01-chrome-login-data-access/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Edge","Chrome","Firefox"],"_cs_severities":["low"],"_cs_tags":["defense-evasion","dns-over-https","registry-modification"],"_cs_type":"advisory","_cs_vendors":["Microsoft","Google","Mozilla"],"content_html":"\u003cp\u003eThe use of DNS-over-HTTPS (DoH) can obscure network activity, potentially allowing malicious actors to bypass traditional DNS monitoring and conceal data exfiltration. When DoH is enabled, visibility into DNS query types, responses, and originating IPs is lost, hindering the detection of malicious activity. This behavior is detected by monitoring registry modifications associated with enabling DoH in popular browsers such as Microsoft Edge, Google Chrome, and Mozilla Firefox. The registry keys targeted are associated with settings that force the browsers to use secure DNS resolution, potentially circumventing organizational security policies.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003e\u003cstrong\u003eInitial Access:\u003c/strong\u003e An attacker gains initial access to a Windows system through various means, such as phishing or exploiting a software vulnerability.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePrivilege Escalation (if necessary):\u003c/strong\u003e The attacker may need to escalate privileges to modify registry settings.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefense Evasion:\u003c/strong\u003e The attacker modifies the Windows registry to enable DNS-over-HTTPS (DoH) in web browsers like Edge, Chrome, or Firefox. This is achieved by modifying specific registry keys such as \u003ccode\u003eHKLM\\SOFTWARE\\Policies\\Microsoft\\Edge\\BuiltInDnsClientEnabled\u003c/code\u003e, \u003ccode\u003eHKLM\\SOFTWARE\\Google\\Chrome\\DnsOverHttpsMode\u003c/code\u003e, or \u003ccode\u003eHKLM\\SOFTWARE\\Policies\\Mozilla\\Firefox\\DNSOverHTTPS\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eObfuscation:\u003c/strong\u003e By enabling DoH, the attacker encrypts DNS queries, making it difficult for network monitoring tools to inspect DNS traffic.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCommand and Control:\u003c/strong\u003e The attacker establishes command and control (C2) communication with a remote server over encrypted DNS traffic, evading traditional network-based detection methods.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eData Exfiltration:\u003c/strong\u003e The attacker uses the encrypted DNS channel to exfiltrate sensitive data, bypassing network security controls that rely on DNS inspection.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePersistence (Optional):\u003c/strong\u003e The attacker might establish persistence by ensuring the DoH settings remain enabled across system reboots.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation leads to a loss of visibility into DNS traffic, hindering incident response and threat hunting efforts. Attackers can effectively hide command-and-control communications and data exfiltration activities. Although this activity by itself isn\u0026rsquo;t inherently malicious, it removes a layer of defense, increasing the risk that malicious activities will go undetected.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eDeploy the Sigma rules provided in this brief to your SIEM to detect the enabling of DNS-over-HTTPS via registry modifications.\u003c/li\u003e\n\u003cli\u003eEnable Sysmon registry event logging to capture the necessary events for the provided Sigma rules to function effectively.\u003c/li\u003e\n\u003cli\u003eReview and update security policies to ensure DNS-over-HTTPS is only enabled through approved channels and for legitimate purposes, reducing the risk of misuse, and create exceptions in the detection rule for systems where this is a known requirement.\u003c/li\u003e\n\u003cli\u003eInvestigate any alerts generated by the Sigma rules, focusing on identifying the user account, process, and associated network activity (reference the investigation guide in the source URL).\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-03T12:00:00Z","date_published":"2024-01-03T12:00:00Z","id":"/briefs/2024-01-dns-over-https-enabled/","summary":"Detection of DNS-over-HTTPS (DoH) being enabled via registry modifications on Windows systems, potentially indicating defense evasion and obfuscation of network activity by masking DNS queries.","title":"DNS-over-HTTPS Enabled via Registry Modification","url":"https://feed.craftedsignal.io/briefs/2024-01-dns-over-https-enabled/"},{"_cs_actors":[],"_cs_cves":[{"cvss":8.8,"id":"CVE-2026-7337"}],"_cs_exploited":false,"_cs_products":["Chrome","Edge (Chromium-based)"],"_cs_severities":["high"],"_cs_tags":["type confusion","v8 engine","chromium","cve-2026-7337"],"_cs_type":"advisory","_cs_vendors":["Google","Microsoft"],"content_html":"\u003cp\u003eCVE-2026-7337 is a type confusion vulnerability residing within the V8 JavaScript engine, the core component of Chromium-based browsers. This vulnerability impacts Google Chrome and Microsoft Edge (Chromium-based), as Edge incorporates the Chromium project. The vulnerability stems from improper handling of object types within the V8 engine during JavaScript execution, potentially leading to exploitable conditions. Successful exploitation could allow an attacker to execute arbitrary code within the context of the browser. Public details are available via the Google Chrome Releases blog and the Microsoft Security Response Center (MSRC). Defenders should prioritize patching to the latest available versions of Chrome and Edge.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAn attacker crafts a malicious web page containing JavaScript code designed to trigger the type confusion vulnerability in the V8 engine.\u003c/li\u003e\n\u003cli\u003eThe victim visits the malicious web page using a vulnerable version of Google Chrome or Microsoft Edge.\u003c/li\u003e\n\u003cli\u003eThe browser\u0026rsquo;s V8 engine attempts to execute the attacker-controlled JavaScript code.\u003c/li\u003e\n\u003cli\u003eDue to the type confusion vulnerability, the V8 engine misinterprets the type of a JavaScript object.\u003c/li\u003e\n\u003cli\u003eThis misinterpretation leads to memory corruption within the browser process.\u003c/li\u003e\n\u003cli\u003eThe attacker leverages the memory corruption to overwrite critical data structures within the browser\u0026rsquo;s memory space.\u003c/li\u003e\n\u003cli\u003eThe attacker gains control of the browser process\u0026rsquo;s execution flow.\u003c/li\u003e\n\u003cli\u003eThe attacker executes arbitrary code on the victim\u0026rsquo;s machine within the security context of the browser process, potentially leading to information disclosure, data theft, or further system compromise.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful exploitation of CVE-2026-7337 allows an attacker to execute arbitrary code within the context of the user\u0026rsquo;s browser. This could lead to sensitive information being stolen, such as cookies, browsing history, and stored credentials. Attackers could also potentially use this vulnerability to install malware or gain further access to the victim\u0026rsquo;s system. Given the widespread use of Chromium-based browsers, this vulnerability poses a significant threat to a large number of users.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eApply the latest security updates for Google Chrome to address CVE-2026-7337. Refer to the Google Chrome Releases blog for details.\u003c/li\u003e\n\u003cli\u003eApply the latest security updates for Microsoft Edge (Chromium-based) to address CVE-2026-7337 as described in the MSRC advisory.\u003c/li\u003e\n\u003cli\u003eImplement a web proxy with content filtering to block access to known malicious websites that may attempt to exploit this vulnerability.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-03T12:00:00Z","date_published":"2024-01-03T12:00:00Z","id":"/briefs/2024-01-cve-2026-7337-v8-type-confusion/","summary":"CVE-2026-7337 is a type confusion vulnerability in the V8 JavaScript engine that affects Google Chrome and Microsoft Edge (Chromium-based).","title":"CVE-2026-7337 Type Confusion Vulnerability in Chromium V8 Engine","url":"https://feed.craftedsignal.io/briefs/2024-01-cve-2026-7337-v8-type-confusion/"},{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Elastic Defend","Slack","WebEx","Teams","Discord","WhatsApp","Zoom","Outlook","Thunderbird","Grammarly","Dropbox","Tableau","Google Drive","MSOffice","Okta","OneDrive","Chrome","Firefox","Edge","Brave","GoogleCloud Related Tools","Github Related Tools","Notion"],"_cs_severities":["medium"],"_cs_tags":["masquerading","defense-evasion","initial-access","malware","windows"],"_cs_type":"advisory","_cs_vendors":["Elastic","Slack","Cisco","Microsoft","Discord","Zoom","Mozilla","Grammarly","Dropbox","Tableau","Google","Okta","Brave","GitHub","Notion"],"content_html":"\u003cp\u003eAttackers often attempt to trick users into downloading and executing malicious executables by disguising them as legitimate business applications. This tactic is used to bypass security measures and gain initial access to a system. These malicious executables, often distributed via malicious ads, forum posts, and tutorials, mimic the names of commonly used applications such as Slack, WebEx, Teams, Discord, and Zoom. The executables are typically unsigned or signed with invalid certificates to further evade detection. This allows the attacker to execute arbitrary code on the victim\u0026rsquo;s machine, potentially leading to further compromise. This campaign aims to target end-users who are less security-aware, and this makes social engineering attacks like this very effective.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eThe user visits a compromised website or clicks on a malicious advertisement.\u003c/li\u003e\n\u003cli\u003eThe user is prompted to download an installer file masquerading as a legitimate business application (e.g., Slack, Zoom, Teams) from a download directory.\u003c/li\u003e\n\u003cli\u003eThe downloaded executable is placed in the user\u0026rsquo;s Downloads folder (e.g., C:\\Users*\\Downloads*).\u003c/li\u003e\n\u003cli\u003eThe user executes the downloaded file.\u003c/li\u003e\n\u003cli\u003eThe executable, lacking a valid code signature, begins execution.\u003c/li\u003e\n\u003cli\u003eThe malicious installer may drop and execute additional malware components.\u003c/li\u003e\n\u003cli\u003eThe malware establishes persistence, potentially using techniques such as registry key modification.\u003c/li\u003e\n\u003cli\u003eThe malware performs malicious activities, such as data exfiltration or lateral movement.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eSuccessful execution of a masqueraded business application installer can lead to a complete system compromise. The attacker gains initial access and can deploy various malware payloads, including ransomware, keyloggers, and data stealers. This can result in data breaches, financial loss, and reputational damage. Although the specific number of victims and sectors targeted are not detailed, the widespread use of the applications being spoofed (Slack, Zoom, etc.) suggests a broad potential impact.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eImplement the Sigma rule \u003ccode\u003ePotential Masquerading as Business App Installer\u003c/code\u003e to detect unsigned executables resembling legitimate business applications in download directories.\u003c/li\u003e\n\u003cli\u003eEnable process creation logging to capture the execution of unsigned executables.\u003c/li\u003e\n\u003cli\u003eEducate users on the risks of downloading and executing files from untrusted sources.\u003c/li\u003e\n\u003cli\u003eImplement application whitelisting to restrict the execution of unauthorized applications.\u003c/li\u003e\n\u003cli\u003eRegularly update endpoint detection and response (EDR) tools to detect and prevent the execution of known malware.\u003c/li\u003e\n\u003cli\u003eMonitor process execution events for processes originating from the Downloads folder that lack valid code signatures.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2024-01-02T12:00:00Z","date_published":"2024-01-02T12:00:00Z","id":"/briefs/2024-01-masquerading-business-apps/","summary":"Attackers masquerade malicious executables as legitimate business application installers to trick users into downloading and executing malware, leveraging defense evasion and initial access techniques.","title":"Masquerading Business Application Installers","url":"https://feed.craftedsignal.io/briefs/2024-01-masquerading-business-apps/"}],"language":"en","title":"CraftedSignal Threat Feed — Chrome","version":"https://jsonfeed.org/version/1.1"}