{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata — refreshed continuously.","feed_url":"https://feed.craftedsignal.io/products/crowdstrike.fdr/","home_page_url":"https://feed.craftedsignal.io/","items":[{"_cs_actors":[],"_cs_cves":[],"_cs_exploited":false,"_cs_products":["Elastic Defend","sentinel_one_cloud_funnel","crowdstrike.fdr"],"_cs_severities":["high"],"_cs_tags":["container-escape","privilege-escalation","linux"],"_cs_type":"advisory","_cs_vendors":["Elastic","SentinelOne","Crowdstrike"],"content_html":"\u003cp\u003eThis detection rule monitors for a specific sequence of commands on Linux systems that could indicate an attempt to escape a containerized environment. The attack involves first mounting a file system, typically targeting the host\u0026rsquo;s root file system, and then using the \u003ccode\u003echroot\u003c/code\u003e command to change the root directory. This combination, if successful, allows an attacker inside a container to gain unauthorized access to the host system. The rule is designed to identify this uncommon behavior pattern, which is a strong indicator of malicious activity. The rule is applicable to environments utilizing Elastic Defend, SentinelOne Cloud Funnel, and Crowdstrike FDR. The detection looks for this sequence occurring within a 5-minute timeframe.\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 container, possibly through exploiting a vulnerability or misconfiguration in the application running within the container.\u003c/li\u003e\n\u003cli\u003eThe attacker attempts to mount the host\u0026rsquo;s root filesystem within the container using the \u003ccode\u003emount\u003c/code\u003e command, often targeting \u003ccode\u003e/dev/sd*\u003c/code\u003e devices. This requires sufficient privileges within the container, or the exploitation of a container escape vulnerability to gain such privileges.\u003c/li\u003e\n\u003cli\u003eThe \u003ccode\u003emount\u003c/code\u003e command is executed with arguments specifying the device to mount and the mount point within the container\u0026rsquo;s file system.\u003c/li\u003e\n\u003cli\u003eThe attacker then executes the \u003ccode\u003echroot\u003c/code\u003e command, changing the root directory of the current process to the mounted host\u0026rsquo;s root filesystem.\u003c/li\u003e\n\u003cli\u003eAfter successfully executing \u003ccode\u003echroot\u003c/code\u003e, the attacker\u0026rsquo;s perspective shifts to the host\u0026rsquo;s file system, allowing them to access and modify sensitive files and configurations.\u003c/li\u003e\n\u003cli\u003eThe attacker uses their newly acquired access to install backdoors, create new user accounts with elevated privileges, or modify system configurations to establish persistence.\u003c/li\u003e\n\u003cli\u003eThe attacker may attempt to move laterally to other containers or systems within the network, leveraging their compromised position on the host.\u003c/li\u003e\n\u003cli\u003eThe final objective is to gain complete control over the host system and potentially the entire infrastructure, leading to data exfiltration, system disruption, or other malicious activities.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eA successful container escape can have severe consequences, potentially leading to complete compromise of the host system and the data it contains. Depending on the environment, this could affect a single server or spread to many hosts. The compromise of containerized environments can lead to data breaches, service disruption, and reputational damage. Given the sensitive nature of data often processed within containers, the impact can range from financial losses to regulatory penalties.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eDeploy the Sigma rules in this brief to your SIEM and tune for your environment to detect potential container escapes.\u003c/li\u003e\n\u003cli\u003eEnable Elastic Defend integration to collect process data, and ensure Session View data is enabled to enhance visibility as mentioned in the setup guide.\u003c/li\u003e\n\u003cli\u003eReview and harden container configurations to minimize privileges granted to containerized processes, reducing the attack surface for escape attempts.\u003c/li\u003e\n\u003cli\u003eImplement network segmentation to limit the potential for lateral movement following a successful container escape.\u003c/li\u003e\n\u003cli\u003eMonitor process execution logs for unusual mount and chroot command sequences within container environments using Elastic Defend, SentinelOne, and Crowdstrike logs.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-05-02T12:45:21Z","date_published":"2026-05-02T12:45:21Z","id":"/briefs/2024-01-chroot-container-escape/","summary":"The rule detects a potential chroot container escape via mount, which involves a user within a container mounting the host's root file system and using chroot to escape the containerized environment, indicating a privilege escalation attempt.","title":"Potential Chroot Container Escape via Mount","url":"https://feed.craftedsignal.io/briefs/2024-01-chroot-container-escape/"}],"language":"en","title":"CraftedSignal Threat Feed — Crowdstrike.fdr","version":"https://jsonfeed.org/version/1.1"}