Possible Container Escape via Working Directory Under proc CVE-2024-21626

ATT&CK techniques

Priv Esc

Recon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
- T1068Exploitation for Privilege Escalation
- T1611Escape to Host
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule detects a process whose current working directory resides under a /proc/<pid>/cwd path. CVE-2024-21626 known as Leaky Vessels abuses a runc file descriptor leak so that a container process starts with its working directory pointing into the host filesystem via /proc. A process running with such a working directory indicates an attempted container breakout.

Reporting behind it

Related detections9 linkedT1068 — drag to rearrange

Possible Sudo Heap Overflow Exploitation via sudoedit (CVE-2021-3156)

Suspicious dirty_sock Local Account Artifact From Snapd Privilege Escalation (via process_creation)

Malicious Container Escape via Nsenter Host Namespace Entry

Suspicious Modification of Privileged Authentication Binaries via Kernel LPE

Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)

Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)

Suspicious EDRKillShifter Vulnerable Driver Load from User Temp Directory (via image_load)

Suspicious Process Explorer Kernel Driver Dropped as PED.sys via File Creation (via file_event)

Malicious Payload Download From copy.fail Exploit Host on Linux (via process_creation)

Possible Container Escape via Working Directory Under proc CVE-2024-21626

Pivot detection · T1068 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.

Full detection rule

Unlock this rule to view and copy it

The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.

Sign in for 3 free unlocks

Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.

Also included

Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.

See it run on a free rule →Convert your own rule →