CVE-2024-54498 is a macOS sandbox escape vulnerability caused by improper path handling. Apple indicated that the issue was addressed through improved validation, implying that insufficient validation of path-related input could allow an application to access resources outside the boundaries intended by the sandbox. The vulnerability affects macOS prior to Sequoia 15.2, Sonoma 14.7.2, and Ventura 13.7.2.
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 exploit for CVE-2024-54498, targeting macOS (specifically macOS 13.5) and demonstrating a sandbox escape via the sharedfilelistd service. The project is structured as an Xcode Objective-C application, with the main exploit logic implemented in ViewController.m. The exploit works by hooking the sandbox_extension_consume function (using the Dobby hooking framework), then performing actions that should be restricted by the sandbox: reading the user's shell history file (~/.zsh_history), writing a file to the Desktop, and manipulating the system's shared file list (adding/removing the root directory from Favorites Volumes). The entitlements file grants the app the necessary permissions to test the exploit. The code demonstrates the vulnerability by showing that these restricted actions can be performed from a sandboxed app, thus escaping the intended security boundaries. No network endpoints are involved; the attack vector is local privilege escalation via a macOS service.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.