Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Mobile

11/7/2016
11:00 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

4G Cellular Networks At Risk Of DoS Attacks

Black Hat Europe researcher shows how hackers can conduct denial-of-service attacks on 4G cellular devices around the world.

Just because you're on a 4G/LTE mobile network doesn't mean you're immune to security issues.

A researcher last week at Black Hat Europe detailed how denial-of-service (DoS) attacks can be waged against 4G/LTE users. In her session "Detach Me Not - DOS Attacks Against 4G Cellular Users Worldwide From Your Desk," Dr. Silke Holtmanns, security specialist at Bell Labs Nokia, explained the state of security in 4G/LTE mobile networks.

Following the revelation of global surveillance and exploits targeting the backend of mobile communication, mobile network operators rushed to upgrade their 2G and 3G networks to 4G/LTE.

The misuse of technical features in mobile networks, like Signaling System 7 (SS7), led to the disclosure of several ways to locate, follow, and manipulate users' cellular activity. Some SS7 incidents included eavesdropping, SMS interception, fraud, credential theft, and data session hijacking.

Diameter protocol, the successor to SS7 used to send signals in LTE networks, promised more protection for networks and users. Many mobile network operators were under the impression that all their security problems would be fixed with LTE/diameter-based protocol.

But security problems still exist; they're just different ones, according to Holtmanns. The diameter protocol includes several functionalities and characteristics of the SS7 network.

Holtmanns explained how hackers can abuse shared traits between diameter and SS7 to conduct DoS attacks like location tracking through the diameter-based interconnection. Some of these attacks can cut mobile phone users from their networks and interfere with network nodes.

Dark Reading's all-day virtual event Nov. 15 offers an in-depth look at myths surrounding data defense and how to put business on a more effective security path. 

 

Holtmanns described several types of DoS attacks that can affect any platform or device on mobile LTE networks: phones, tablets, and gadgets connected to the IoT like connected cameras. Researchers explored different options for DoS attacks using a test setup.

These are a few of the attack methods they discovered:

  • DoS using Cancel Location Request (CLR): This is sent by the home subscriber service (HSS) to the mobile management entity (MME) to wipe a user from the network.
  • DoS using Insert Subscriber Data Request (IDR): These are sent from the HSS to the MME to update and/or request user data like location and/or state information. This attack on the MME, which covers a broad area (for context, Holtsmann noted that London has two), has an impact on any users located in the affected region.
  • DoS using Update Location Request (ULR): This is sent by the MME to the HSS to inform of a user's change in location. The user may be kicked outside the network, but there are no major side effects. Users can fix the problem by switching off their phone and reconnecting.

Holtsmann noted that IPSec for diameter is standardized, so many security pros will assume this is the best protective route to take. It's not that easy, however, she said, and there are a few practical considerations to bear in mind.

Not all traffic is IP, for starters, as some is part of SS7 or work with it. There is also the question of who will host or create root certificates, and there is no interconnection service provider; only hop-by-hop security. IPSec also doesn't protect against hacked nodes, bribed employees, governmental ties, or partners renting out to "service companies," according to Holtsmann.

Preparation is "an important part of the puzzle," she noted, because there is a good chance these DoS attacks will occur.

"Diameter attacks will come as tech moves on in a major way," she explained. "Now is the time to prepare for diameter attacks. You need to investigate potential weaknesses and countermeasures before they happen."

Bearing in mind that DoS attacks are likely, she continued, but there are several countermeasures to mitigate the risk. These include monitoring network traffic, tenant equipment, and firewalls.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.