Thread

Replies (3)

🛡️
Yes. Apple (finally) incorporated memory tagging into their latest iPhones and called it Memory Integrity Enforcement because of that. Their article provided examples on how memory tagging and secure allocators mitigated PoC exploit chains. image
🛡️
Apple use can manufacture the latest ARM processors and so they have the latest iteration of ARM memory tagging (FEAT_MTE4) which they call Enhanced MTE (EMTE). Currently Pixels do not have that. If newer devices come out and add it, we can use it too. It is great they finally implemented it and with far greater coverage than stock Pixels, but they were behind on this for many years.
🛡️
Generally, they're bad on every platform . All the security companies and government agencies moved to recommending memory-safe languages and replacing unsafe legacy code with new code for a reason. They become a security liability. Take a look at the charts of a project's sizeand the amount of memory-unsafe code they have: image What comprises the most dangerous vulnerabilities for these big projects like Linux and Chromium? Memory corruption. Android uses Linux and many major vulnerabilities are inherited from it.