Apple only releases Rapid Security Response updates for the latest versions of its operating systems [1]. So any devices running iOS 16.4.X or MacOS 13.3.X won't see one, and anything before that didn't support Rapid Security Response updates. Unfortunately there's not enough information available to know if older releases are vulnerable.
Betas don't need a rapid response; people running beta can wait.
Though for all you know this bug doesn't even exist in the newer versions. Or the mitigation was already in the beta but this rapid response required an extra day for testing as it is being shipped to users.
recently the pixels had a remote exploit just by being connected to a 4g network. we got two victims in our group in the 3wk google took to patch (it was the first late security update on the same time)... and we did warn everyone to turn radio off (or limit to 3g if out of the us)... nobody cares and they just use the device thinking they won't be a target.
I remember just after this announcement was the first super-critical update for ventura. It was about 31 days before older OS versions got the patch, even though they were identified as vulnerable at the time of the ventura update. :(
Persisting in the fs is much harder than just getting code execution. Not impossible (nothing is) but much harder (and thus likely less common), due to signature checking
Forensic approach is to get a disk image(iOS just has backups) and analyze that. You can't ever be 100% sure. Can't prove a negative (no compromise) you can only prove positives based on the state of the device you can measure.
Personally, I only use mobile devices for internet browsing and using apps like uber, I only have like one app I should probably stop using but to the most part I always assume any mobile device out there is or can readily be compromised.
Would be pretty difficult to find an exploit that avoids the boot chain attestation features. Good reason why a lot of exploits require you to reapply them every reboot.
27 comments
[ 13.8 ms ] story [ 220 ms ] thread[1] https://support.apple.com/en-us/HT201224
Assume YES.
Though for all you know this bug doesn't even exist in the newer versions. Or the mitigation was already in the beta but this rapid response required an extra day for testing as it is being shipped to users.
recently the pixels had a remote exploit just by being connected to a 4g network. we got two victims in our group in the 3wk google took to patch (it was the first late security update on the same time)... and we did warn everyone to turn radio off (or limit to 3g if out of the us)... nobody cares and they just use the device thinking they won't be a target.
I remember just after this announcement was the first super-critical update for ventura. It was about 31 days before older OS versions got the patch, even though they were identified as vulnerable at the time of the ventura update. :(
How do you know that an attacker is not persisting in the system if you click a bad link before a patch gets applied?
Personally, I only use mobile devices for internet browsing and using apps like uber, I only have like one app I should probably stop using but to the most part I always assume any mobile device out there is or can readily be compromised.