Ruhr University Bochum, Software Radio Systems, Radix Security, Radboud University
When our phone connects to a mobile network, it uses a certain standard aka a mobile generation. The most common standard at the moment is 4G, with 5G being rolled out more and more. Each new generation introduces improvements over the previous ones. This is possible because we try to learn from the mistakes of older technologies and improve the performance that once was the standard. From a security perspective, this means the more up-to-date a connection is, the more security we can expect from it. Things that have been broken in 3G are mostly fixed in 4G. And we try to do the same for 5G and beyond. In a downgrade attack, an adversary tries to force the connection to a less secure standard. That can be weaker encryption algorithms or even connections using an older mobile generation. Such bidding-down attacks can be very diverse and use many different characteristics of a mobile connection, which makes it very difficult to simply protect against all of them. In this project, you will find different examples of bidding-down attacks that demonstrate how it is a persisting problem that affects different mobile generations, different up-to-date smartphones, and commercial networks. The following will guide you through the most important findings and provide pointers to more technical details.
The goal of such an attack, no matter what type of attack is applied or what attack vector (a characteristic of the network that can be exploited by the adversary) is used, is to weaken the security. Enforcing a weaker connection opens the door for follow-up attacks in which the adversary can, for example, try to eavesdrop on the connection.
Bidding down the connection within a generation means that the default security characteristics of the connection get weakened. Let’s say a connection uses the latest encryption standard by default. Then an intra-generation attack forces the connection to use a weaker standard. What’s dangerous about these attacks within the generation is that they only lead to minor changes within the connection. Using a less secure connection is not visible to the user, however, once there is weak or no encryption in place it is easy to conduct follow-up attacks.
Bidding down a connection to a different generation means a switch from, let’s say, 4G to 3G. The consequences of such a switch are more far-reaching than before: The connection uses a whole different technology and inherits all weaknesses that are known to the generation. Such an attack might be less stealthy but also opens the door for even more follow-up attacks.
We have used the vulnerabilities in our findings to forge different types of bidding-down attacks. Note, that while we have carried out these attacks in our shielded laboratory environment, they require sophisticated radio hardware and significant effort in order to be executed in the real world.
We first present a 5G downgrade dance attack, which is an inter-generation bidding-down that enables an attacker to downgrade a phone from a 5G connection down to an insecure 2G connection. Once downgraded to 2G, the attacker can manipulate and eavesdrop on the entire connection as 2G offers no effective security mechanisms.
The second attack we present is a NEA0 bidding-down in a 5G NSA, an intra-generation attack aiming to disable the radio connection between the UE and the gNodeB. If the attack succeeds, the adversary can eavesdrop on the user data that is transported via this radio connection.
Our work appears at the Conference on Security and Privacy in Wireless and Mobile Networks ‘23 (WiSec’23). You can find the pre-print of our paper here.
@inproceedings{karakoc2023never, author = {Karakoc, Bedran and Fürste, Nils and Rupprecht, David and Kohls, Katharina}, title = {Never Let Me Down Again: Bidding-Down Attacks and Mitigations in 5G and 4G}, booktitle = {Proceedings of the 16th ACM Conference on Security and Privacy in Wireless and Mobile Networks}, series = {WiSec '23}, year = {2023}, url = {https://doi.org/10.1145/3558482.3581774}, doi = {10.1145/3558482.3581774}, }