<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IOS Security on Matt Suiche</title><link>https://www.msuiche.com/categories/ios-security/</link><description>Recent content in IOS Security on Matt Suiche</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.msuiche.com/categories/ios-security/index.xml" rel="self" type="application/rss+xml"/><item><title>ELEGANTBOUNCER: When You Can't Get the Samples but Still Need to Catch the Threat</title><link>https://www.msuiche.com/posts/elegantbouncer-when-you-cant-get-the-samples-but-still-need-to-catch-the-threat/</link><pubDate>Sun, 24 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.msuiche.com/posts/elegantbouncer-when-you-cant-get-the-samples-but-still-need-to-catch-the-threat/</guid><description>&lt;h2 id="the-genesis-when-signatures-arent-enough"&gt;The Genesis: When Signatures Aren&amp;rsquo;t Enough &lt;a href="#the-genesis-when-signatures-arent-enough" class="anchor"&gt;🔗&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;In the world of mobile security research, there&amp;rsquo;s a recurring frustration that keeps many of us up at night: the most sophisticated exploits - the ones that really matter - are rarely shared. When &lt;a href="https://citizenlab.ca" target="_blank" rel="noopener"&gt;Citizen Lab&lt;/a&gt; and &lt;a href="https://blog.google/threat-analysis-group/" target="_blank" rel="noopener"&gt;Google TAG&lt;/a&gt; discover NSO Group&amp;rsquo;s latest 0-click exploits targeting journalists and activists, we get brilliant technical writeups, CVE numbers, and patches. What we don&amp;rsquo;t get? The actual samples.&lt;/p&gt;
&lt;p&gt;This isn&amp;rsquo;t a criticism - there are excellent reasons for limiting access to weaponized exploits. But it creates a fundamental problem: &lt;strong&gt;How do you protect against threats you&amp;rsquo;ve never seen?&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Detecting CVE-2025-43300: A Deep Dive into Apple's DNG Processing Vulnerability</title><link>https://www.msuiche.com/posts/detecting-cve-2025-43300-a-deep-dive-into-apples-dng-processing-vulnerability/</link><pubDate>Sat, 23 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.msuiche.com/posts/detecting-cve-2025-43300-a-deep-dive-into-apples-dng-processing-vulnerability/</guid><description>&lt;h2 id="the-discovery"&gt;The Discovery &lt;a href="#the-discovery" class="anchor"&gt;🔗&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;CVE-2025-43300 represents one of those subtle yet devastating vulnerabilities that security researchers dream (or have nightmares) about. According to &lt;a href="https://www.cve.org/CVERecord?id=CVE-2025-43300" target="_blank" rel="noopener"&gt;Apple&amp;rsquo;s official advisory&lt;/a&gt;, this out-of-bounds write issue was discovered in their implementation of JPEG Lossless Decompression code within the RawCamera.bundle, which processes Adobe&amp;rsquo;s DNG (Digital Negative) files.&lt;/p&gt;
&lt;p&gt;What elevates this from a typical vulnerability to a critical threat is Apple&amp;rsquo;s chilling acknowledgment: &lt;strong&gt;&amp;ldquo;Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals.&amp;rdquo;&lt;/strong&gt; This isn&amp;rsquo;t theoretical - it&amp;rsquo;s been weaponized.&lt;/p&gt;</description></item></channel></rss>