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.

Risk

5/21/2009
02:49 PM
50%
50%

Tech Road Map: 3G Security Is Getting Better, But It's Still Incomplete

Safeguarding wireless traffic in transit is only part of the equation. Pay attention to devices and endpoints, too.

With more organizations using mobile broadband networks, IT managers should be very concerned about security. Safeguarding data as it travels the airwaves may be only part of a mobile security policy -- enterprises must secure their devices and the data they store -- but the airwaves are a good place to start.

The good news about wireless security is that today's mobile broadband networks have some enhanced security functions built in. The latest 3G technologies, including WiMax, have robust encryption options. AT&T and T-Mobile provide High Speed Packet Access with a 128-bit Kasumi encryption algorithm. CDMA2000, offered by Sprint and Verizon, sports 128-bit Advanced Encryption Standard encryption. WiMax also uses AES.

InformationWeek Reports

Encryption Not Guaranteed
The bad news is that there are major shortfalls with AES. One is that AES activation is largely optional on the part of operators. AT&T says its Kasumi encryption is always on, but Verizon wouldn't say whether that's the case for its encryption option. Moreover, even if your operator uses encryption, your users may roam onto a network that doesn't. And a 2G connection has much less robust encryption mechanisms than 3G, which are considered easy to defeat.

Finally, channel encryption only extends to an intermediate point within the cellular network. After that, data travels unencrypted until it reaches the far end of a connection, where most communication is again locked down.

DIG DEEPER
Go Mobile
Figuring out 3G/4G mobile broadband is worth the effort.
Some operators offer network VPNs or private circuits, e.g., frame relay, for the unencrypted portion of your data's journey, so there are some options on the back end if you have a lot of data business with an operator. But these options can be complicated. Even if your radio link is reasonably secure, there's the problem of users connecting via other access networks, such as unprotected Wi-Fi hotspots. Wi-Fi capability is the norm for laptops and increasingly is available on smartphones.

Previous
1 of 3
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...