A vulnerability in Termius prior to version 9.9.0 allows a local attacker to execute arbitrary code by leveraging the DYLD_INSERT_LIBRARIES environment variable. By supplying a crafted script, an attacker can inject a malicious dynamic library into the Termius process, leading to arbitrary code execution.
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 provides a proof-of-concept (POC) exploit for CVE-2024-55503, a local code injection vulnerability in the Termius App for macOS (versions before 9.9.0). The exploit leverages the DYLD_INSERT_LIBRARIES environment variable to inject a malicious dynamic library into the Termius process. The main exploit code (main8.m) is an Objective-C file that, when compiled as a dylib and loaded into Termius, executes a shell command to read the first 20 lines of /etc/passwd, demonstrating arbitrary code execution. The repository consists of a README.md explaining the vulnerability, usage instructions, and a reference to the CVE, and a single code file (main8.m) containing the exploit logic. The attack vector is local, requiring the attacker to execute Termius with a crafted environment. The endpoints identified include the target application binary and the /etc/passwd file accessed by the payload.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.