<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Privacy-Bypass — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/privacy-bypass/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 26 May 2026 07:44:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/privacy-bypass/feed.xml" rel="self" type="application/rss+xml"/><item><title>macOS TCC Database Modification for Privacy Control Bypass</title><link>https://feed.craftedsignal.io/briefs/2026-05-tcc-db-modification/</link><pubDate>Tue, 26 May 2026 07:44:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-tcc-db-modification/</guid><description>Adversaries may attempt to bypass macOS privacy controls by directly modifying the Transparency, Consent, and Control (TCC) SQLite database using sqlite3, potentially gaining unauthorized access to sensitive resources.</description><content:encoded><![CDATA[<p>Attackers may attempt to evade macOS privacy controls by directly modifying the TCC (Transparency, Consent, and Control) database. The TCC database manages application permissions for sensitive resources like the camera, microphone, address book, and calendar. By using tools like <code>sqlite3</code> to manipulate this database, adversaries can grant themselves unauthorized access to these resources. This technique has been observed in previous bypasses of the TCC framework, such as the vulnerability described in CVE-2020-9934. This is a post-exploitation technique that can be used to expand access after initial compromise.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial access is gained to the macOS system through an unrelated exploit (e.g., phishing, software vulnerability).</li>
<li>The attacker executes a shell (e.g., <code>bash</code>, <code>zsh</code>) or scripting language (e.g., <code>osascript</code>, <code>python</code>) on the target system.</li>
<li>The attacker uses <code>sqlite3</code> to interact with the TCC database located at <code>/*/Application Support/com.apple.TCC/TCC.db</code>.</li>
<li>The <code>sqlite3</code> process modifies entries in the TCC database to grant unauthorized access to protected resources (camera, microphone, contacts, etc.).</li>
<li>The attacker then executes an application that leverages the newly granted TCC permissions.</li>
<li>The application accesses previously restricted resources without prompting the user for consent.</li>
<li>The attacker exfiltrates the sensitive data obtained through unauthorized access.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthorized access to sensitive user data protected by macOS privacy controls. This can lead to data theft, privacy violations, and further compromise of the system. This is a local privilege escalation, giving the attacker access to resources normally protected by TCC.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect TCC Database Modification via sqlite3</code> to identify suspicious processes using <code>sqlite3</code> to modify the TCC database.</li>
<li>Investigate any process execution events where <code>sqlite3</code> is used with arguments targeting the TCC database (<code>/*/Application Support/com.apple.TCC/TCC.db</code>).</li>
<li>Monitor for unusual parent processes of <code>sqlite3</code> such as scripting environments (<code>osascript</code>, <code>bash</code>, <code>zsh</code>, <code>Terminal</code>, <code>Python*</code>) as highlighted in the rule.</li>
<li>Investigate processes accessing protected resources (camera, microphone, contacts) without prior user consent.</li>
<li>Enable Elastic Defend integration to collect process execution data required for the detection rules.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>privacy-bypass</category><category>defense-evasion</category><category>macos</category></item></channel></rss>