That doesn't make an iPhone 7 impregnable, but it should inform any analysis you do of stories about phones being tampered with "starting in 2008"; that's a little like talking about SMTP server security "starting in 1993".
That doesn't make an iPhone 7 impregnable, but it should inform any analysis you do of stories about phones being tampered with "starting in 2008"; that's a little like talking about SMTP server security "starting in 1993".
[0] https://www.theiphonewiki.com/wiki/0x24000_Segment_Overflow
We should not 'stop worrying about the CIA' just because Apple came to the rescue and already fixed the bugs.
We should, in fact, continue to apply pressure to such vendors of digital enslavement as Apple, and the rest of the sordid gang, to provide real evidence that "Things are Okay™", when asked.
I have no idea how you would begin to demonstrate that a body of source code as big (in both lines of code and length / size of the development project) as iOS, Android/Replicant/Lineage, or any other modern operating system contains zero backdoors, especially when your threat model involves the software authors helping you over a period of many years to weave those backdoors into the OS and obfuscate them as much as necessary.
I also have no idea how to audit a physical phone I have received from an Apple Store to make sure that the hardware and firmware faithfully implement what they are supposed to be implementing.
The encrypted by default iOS 4 and the whole design around passcode handling in that release was the start of a very strong security posture for Apple and their iOS devices.
Apparently $1,500[1]:
"Cellebrite's CAIS now supports lawful unlocking and evidence extraction of iPhone 4S/5/5C/5S/6/6+ devices (via our in-house service only)."[2]
[1] https://www.macrumors.com/2017/02/24/cellebrite-lawful-unloc...
As recently as last April, the FBI was claiming they could not access 5S or newer models[1] (at least with the hack they reportedly bought for over $1 million[2]).
[1] https://9to5mac.com/2016/04/07/fbi-iphone-hack-method-secure...
[2] http://www.cnn.com/2016/04/21/politics/san-bernardino-iphone...
Btw, these don't mention 6S or later models, or even the iPhoneSE.
Guessing the exploits are dependent on chipset or older version of the OS.
backup and wipe your phone before you travel. there are several stories now of customs compelling you to unlock the phone before allowing you to leave.
https://www.theatlantic.com/technology/archive/2017/02/a-nas...
It's very important to understand the silent-exploit threat model! That's the model used when someone is being investigated as a terrorist (or freedom fighter) and the government doesn't want to make them aware they're being surveilled, because they might change their plans.
In particular, the 3G is going to be highly vulnerable to silent exploits because of the lack of software updates, but that's not your concern at the border. Your concern is the lack of Secure Enclave on the 3G. That means that if they take your phone from you, they can image the contents of it fairly easily, without needing a fingerprint or passcode from you. If you get a newer phone, enable encryption, and use a strong passcode instead of a fingerprint, you can reboot the phone before a border crossing, and then the data is strongly protected unless you choose to give up your passcode.
For the customs threat model, you might also want to bring a different phone with limited data when traveling. It might make sense to have a powered-off phone with a Secure Element somewhere separate from you (e.g., shipped via post), and just use the 3G for contacting folks while in transit, wiping all interesting data from it. In theory, this means your secure phone could get confiscated but you can't be compelled to unlock it (since you're not physically with it). I'm curious if other folks on this forum think this is a reasonable plan.
... Also, the easy vulnerability to silent exploits is probably a huge threat for you for non-government attackers, which are a much more common attack.