Loading vulnerability…
In iTerm2 versions 3.5.x before 3.5.2, the terminal fails to properly filter escape sequences used to report window titles when the built-in tmux integration feature is enabled (default setting). This allows an attacker to inject arbitrary code into the terminal session by crafting malicious escape sequences, leading to code execution within the user's environment. This vulnerability is distinct from CVE-2024-38395.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) exploit for CVE-2024-38396 and CVE-2024-38395, targeting macOS terminal emulators that improperly handle certain escape sequences. The repository contains three files: a Dockerfile, a README.md, and a text file ('simpler-poc-title-report-code-execution.txt') containing the exploit payload. The payload is a crafted terminal escape sequence that, when displayed in a vulnerable terminal (e.g., by running 'cat simpler-poc-title-report-code-execution.txt'), will execute the command 'open -aCalculator', opening the Calculator app on macOS. The Dockerfile provides a containerized way to demonstrate the exploit by copying the PoC file to '/etc/' and displaying it. There are no network endpoints or remote attack vectors; exploitation requires local access to a vulnerable terminal emulator. The exploit demonstrates code execution via terminal escape sequences, highlighting the risk of viewing untrusted files in terminal emulators.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.