Mobile

11/7/2016
11:00 AM
Connect Directly
Twitter
LinkedIn
Google+
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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14981
PUBLISHED: 2018-08-17
Certain LG devices based on Android 6.0 through 8.1 have incorrect access control for SystemUI application intents. The LG ID is LVE-SMP-180005.
CVE-2018-14982
PUBLISHED: 2018-08-17
Certain LG devices based on Android 6.0 through 8.1 have incorrect access control in the GNSS application. The LG ID is LVE-SMP-180004.
CVE-2018-15482
PUBLISHED: 2018-08-17
Certain LG devices based on Android 6.0 through 8.1 have incorrect access control for MLT application intents. The LG ID is LVE-SMP-180006.
CVE-2018-15473
PUBLISHED: 2018-08-17
OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.
CVE-2018-15471
PUBLISHED: 2018-08-17
An issue was discovered in xenvif_set_hash_mapping in drivers/net/xen-netback/hash.c in the Linux kernel through 4.18.1, as used in Xen through 4.11.x and other products. The Linux netback driver allows frontends to control mapping of requests to request queues. When processing a request to set or c...