This exploit may seem simple but it goes a little deeper than it would seem at first sight, after all we will fist need to define when we have sufficient cryptography before anything else. In normal operation we we encrypt/decrypt sensitive data but there are two ways in which this can go wrong. Either the wrong encryption algorithm can be used (too weak) or it may be implemented incorrectly like for example no encryption on any sensitive endpoints where there should be.
This vulnerability type is going to be most usefull for pentesters and programmers trying to identify these issues before they occur
We can either attempt to abuse this vulnerability with physicall acess to the victim's device or using malware that acts as an intermediatary. Whatever method we pick, we first have to identify all locations where data is stored on the device, this could be caching, local file storage, login data,...).
After we identify the locations data is stored we need to identify which of that data is sensitive (often in a meeting with business) before we can check the manner of encryption in which the data gets processed before being stored.
This vulnerability can have a number of different business impacts. Typically, broken cryptography will result in the following:
As you can see in the attack plan, for iOS breaking the encryption of any app is trivial and we should always assume that the attacker can bypass any OS level encryption.
Even if we encrypted the app properly there are still dangers we should avoid