No OS can completely prevent exploitation. GrapheneOS however has not been known to be vulnerable and nobody has claimed to have done. GrapheneOS has much more advanced exploit mitigations to protect against targeted attacks including hardened_malloc and hardware memory tagging support.
Everyone on GrapheneOS has hardened_malloc and our other baseline exploit protections. hardened_malloc has great support for hardware memory tagging to provide a form of memory safety for memory unsafe code with a mix of deterministic guarantees and randomized general protection.
Production hardware memory tagging is currently exclusive to GrapheneOS running on 8th Gen Pixels. OS wide inclusive of our browser/webview Vanadium.
Our Auditor app can also be used to verify that it's a genuine GrapheneOS install.
If an attacker does exploit the device, they need to persist their access through persistent data due to verified boot, and then exploit the device again on each boot from there. This means wiping data from recovery removes access. Auditor is there to help discover compromise.
This makes Auditor useful for checking persistent state such as whether an accessibility service is enabled, which could be hidden from the user by the accessibility service if the user tried to check on the device itself via the Settings app, etc.
You are more secure on GrapheneOS.
MetropleX [GrapheneOS] ⚡🟣
npub1gd3…cn8c
2023-12-20 19:13:59
in reply to nevent1q…x3aq
Author Public Key
npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8cPublished at
2023-12-20 19:13:59Event JSON
{
"id": "a37c5d318206a914c2f42ba84ffcb56e258a63876ae3a7e1c4408de83433c2b0",
"pubkey": "43637a311a15f1c253b5d60778ab7544ac639b88e168e7224a900d4a41283183",
"created_at": 1703096039,
"kind": 1,
"tags": [
[
"e",
"c3c6a4e55beaa9e1e841223970af056ae433cd9c83da2e12a72e0c01d0e15149",
"",
"root"
],
[
"e",
"91f66f9bf76750c5bccbdab085cee7098b543ee1b09f630d97e4f838ec3ec85c",
"",
"reply"
],
[
"p",
"ac3f6afe17593f61810513dac9a1e544e87b9ce91b27d37b88ec58fbaa9014aa"
],
[
"p",
"40ecf59b56009813ea4c3081b19d9d525f76dbf251a5a0389b4bea27c3a6b98f"
]
],
"content": "No OS can completely prevent exploitation. GrapheneOS however has not been known to be vulnerable and nobody has claimed to have done. GrapheneOS has much more advanced exploit mitigations to protect against targeted attacks including hardened_malloc and hardware memory tagging support. \n\nEveryone on GrapheneOS has hardened_malloc and our other baseline exploit protections. hardened_malloc has great support for hardware memory tagging to provide a form of memory safety for memory unsafe code with a mix of deterministic guarantees and randomized general protection.\n\nProduction hardware memory tagging is currently exclusive to GrapheneOS running on 8th Gen Pixels. OS wide inclusive of our browser/webview Vanadium.\n\nOur Auditor app can also be used to verify that it's a genuine GrapheneOS install.\n\nIf an attacker does exploit the device, they need to persist their access through persistent data due to verified boot, and then exploit the device again on each boot from there. This means wiping data from recovery removes access. Auditor is there to help discover compromise.\n\nThis makes Auditor useful for checking persistent state such as whether an accessibility service is enabled, which could be hidden from the user by the accessibility service if the user tried to check on the device itself via the Settings app, etc. \n\nYou are more secure on GrapheneOS.",
"sig": "49cec70e5c6eebc0efafc4412a500aa3512950ea088e42b6319926028e4ac7a13e1750f0e91221b6c1e70cb76a4cff866354e4cc7d15170c9a1a9d2169df6a0a"
}