<story><title>Get root on macOS 13.0.1 the macOS Dirty Cow bug</title><url>https://worthdoingbadly.com/macdirtycow/</url></story><parent_chain></parent_chain><comment><author>MaxLeiter</author><text>The project zero bug linked in the post (which I recommend reading first) has more details on the exploit&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;project-zero&amp;#x2F;issues&amp;#x2F;detail?id=2337&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;project-zero&amp;#x2F;issues&amp;#x2F;detail?id=23...&lt;/a&gt;</text></comment>
<story><title>Get root on macOS 13.0.1 the macOS Dirty Cow bug</title><url>https://worthdoingbadly.com/macdirtycow/</url></story><parent_chain></parent_chain><comment><author>MichaelZuo</author><text>&amp;quot;Will this be useful for jailbreak?
Probably not.&lt;p&gt;This - as far as I can tell - affects userspace processes only. Jailbreaks require a kernel exploit. (The Apple Security release notes says that this bug may allow “arbitrary code with kernel privileges”, but I can’t see how.)&lt;p&gt;You might still do something cool on iOS with this, but I’m not sure what you’d overwrite: codesigning should protect all executables and libraries. (I have not tested this: let me know if you find anything!)&amp;quot;&lt;p&gt;Looks like system integrity protection? or some other mechanism preventing this?</text></comment>