<?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>Security-Mitigation — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/security-mitigation/</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, 30 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/security-mitigation/feed.xml" rel="self" type="application/rss+xml"/><item><title>Apple's App Translocation Security Mechanism</title><link>https://feed.craftedsignal.io/briefs/2024-01-app-translocation/</link><pubDate>Tue, 30 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-app-translocation/</guid><description>Apple's App Translocation in macOS v10.12 mitigates Gatekeeper bypasses (CVE-2015-3715, CVE-2015-7024) by creating a read-only DMG, impacting applications accessing external resources.</description><content:encoded><![CDATA[<p>Apple introduced App Translocation in macOS v10.12 as a response to Gatekeeper bypasses, specifically CVE-2015-3715 and CVE-2015-7024. The core issue was that external content, referenced relatively to a verified application, was not being verified. App Translocation addresses this by creating a read-only DMG image at a randomized location when an application downloaded from the internet is launched. Only the application bundle is included in this DMG. This prevents the application from accessing external resources in the same directory, thus thwarting bypasses that abuse relatively external content. This mechanism relies on the com.apple.quarantine extended attribute to identify downloaded applications. The goal is to generically thwart all Gatekeeper bypasses that abuse relatively external content. This re-architecting of Gatekeeper required changes to numerous OS components and can cause issues for legitimate applications attempting to modify their components post-launch.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker crafts a malicious installer package (e.g., ZIP archive or unsigned DMG) containing a signed, Gatekeeper-approved application vulnerable to dylib hijacking.</li>
<li>The package also includes a malicious, unsigned dynamic library (dylib) or executable placed alongside the signed application (e.g., &ldquo;ibtoold&rdquo; next to &ldquo;ictool&rdquo;).</li>
<li>User downloads the malicious package from the internet. The downloaded archive is tagged with the <code>com.apple.quarantine</code> extended attribute.</li>
<li>User extracts the application from the downloaded package and double-clicks the signed application to execute it.</li>
<li>App Translocation intercepts the execution attempt and creates a read-only DMG image on the fly, containing <em>only</em> the signed application bundle, at a randomized location.</li>
<li>The translocated copy of the application is executed from the read-only DMG.</li>
<li>The signed application attempts to load or execute the external, malicious dylib or executable using a relative path.</li>
<li>Due to App Translocation, the external content is no longer present in the randomized location. The attack fails because the application cannot find the unverified external content.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>App Translocation was designed to prevent attackers from bypassing Gatekeeper by exploiting signed applications that load external, unvalidated content. Without this mitigation, attackers could execute arbitrary code, potentially leading to malware installation, data theft, or system compromise. The security mechanism has negatively affected legitimate applications that rely on modifying their components or accessing external files in the same directory, requiring developers to find workarounds.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor for the presence of the <code>com.apple.quarantine</code> extended attribute on downloaded files to identify applications potentially subject to App Translocation using file_event logs.</li>
<li>Deploy the &ldquo;Detect App Translocation Bypass via File Access&rdquo; Sigma rule to identify applications attempting to access files in their original download location after being translocated.</li>
<li>Audit applications that modify their own binaries or metadata after launch, as App Translocation can prevent these operations. Consider refactoring these applications to comply with App Translocation or explore alternative distribution methods.</li>
<li>Consider applications that are affected by App Translocation, potentially breaking auto-update or other legitimate features.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>app-translocation</category><category>gatekeeper</category><category>macos</category><category>security-mitigation</category></item></channel></rss>