7 ms·
iOS does not allow the modification or generation of new executable code (at least, it will not at this stage of an exploit). So they are likely creating a weir
by saagarjha 5y ago
iOS does not allow the modification or generation of new executable code (at least, it will not at this stage of an exploit). So they are likely creating a weird machine to patch various data and then redirecting control flow with the altered state by overwriting a function pointer.
- onphonenow 5y agoRight, and they get there of a decomp pass on totally untrusted input over the network. This is why it's so crazy that apple has this huge attack surface. My own suggestion. Ascii only messages if contact is not in address book or is a contact you've communicated with in your message history (however long you keep that) up to 1 year. Once you reply these untrusted saudi contacts can send you the gif meme's.
- snovv_crash 5y ago"Hello this is the state police, your mother just got in a car accident, please respond"
- rhizome 5y ago[calls phone number]
- ls612 5y agoIn the US if something serious like this happens the police will physically notify the next of kin of it, not send you a text.
- onphonenow 5y agoThe "police" already email and call me about my overdue IRS bill and my imminent arrest. I ignore all that crap. Never interacted, maybe ascii only. Interacted, allow unicode and some other features (basic emojies? / photos?). Full contact? Allow the app integrations, heart sensor, animated images, videos etc.
- colejohnson66 5y agoAh yes, let’s just force ASCII so that anyone using a language that’s not English has to suffer.
- inkyoto 5y ago> […] then redirecting control flow with the altered state by overwriting a function pointer. The analysis calls this out specifically: > Conveniently since JBIG2Bitmap inherits from JBIG2Segment the seg->getType() virtual call succeed even on devices where Pointer Authentication is enabled Which is disturbing. Was the code compiled for the arch64e architecture in the first place, or it is a bug in the LLVM compiler toolchain? The armv8.3 authenticated pointers have been invented to preclude this from happening, but that is not the case with the exploit.
- saagarjha 5y agoPointer authentication cannot protect against all pointer substitutions, because doing so to arbitrary C++ code would violate language guarantees. https://github.com/apple/llvm-project/blob/next/clang/docs/PointerAuthentication.rst https://github.com/apple/llvm-project/blob/next/clang/docs/P... is a good overview of which things can and can’t be signed because of standards compliance.