CVE-2023-32407 is a logic flaw in Apple platforms caused by improper state management in privacy preference handling. Apple indicates that an application may be able to bypass Privacy preferences, meaning the vulnerable logic can allow an app to circumvent user-configured privacy controls. The issue was corrected through improved state management in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, iOS 15.7.6, iPadOS 15.7.6, macOS Big Sur 11.7.7, macOS Monterey 12.6.6, iOS 16.5, and iPadOS 16.5.
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 contains an exploit for CVE-2023-32407, a macOS TCC (Transparency, Consent, and Control) bypass vulnerability. The main exploit logic is implemented in 'lateralus.py', a Python script that orchestrates a race condition to overwrite the TCC.db file, which controls app permissions on macOS. The exploit works by creating symlinks and rapidly swapping directories while launching the Music app, exploiting timing to gain write access to the protected TCC.db file. The script then overwrites this file with attacker-controlled data, potentially granting unauthorized permissions to applications. The exploit also restarts the tccd service to apply changes and demonstrates access by listing the user's Documents directory. The 'misc/resettcc.sh' script is a helper to reset the TCC database and restart the tccd service. The repository is operational and provides a working exploit for local privilege escalation on macOS systems.
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.
2 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.