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.

Endpoint Security

5/24/2019
10:25 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Zscaler Finds Security Issues Galore in IoT Traffic

The use of plain-text HTTP communication, outdated libraries and weak default credentials all rang alarm bells.

Zscaler's ThreatLabZ took a look at one month of data for IoT device footprints which were based in the Zscaler cloud. They came up with a reportthat they have released this week which is a snapshot of the protocols the devices used, the locations of the servers with which they communicated, and the frequency of their inbound and outbound communications.

This idea was to see what was going on with IoT traffic patterns. Showing how widespread IoT adoption has become, the devices that they found passing information around were sort of prosaic in their functions.

The IoT devices seen most often in the Zscaler cloud were set-top boxes (generally used for decoding video), followed by smart TVs, smart watches, media players and printers.

They saw 109 different set-top box device profiles from 68 manufacturers, including AerialBox, Alfawise, Amazon, Amlogic, Apple, Beelink, BenQ, Bomix, Bqeel, Foxtel Now and Google.

The enterprise -- somewhat surprisingly -- also had a strong presence in DVR traffic. Here, a DVR is defined as a network-connected smart device used for recording and playing back digital videos. They found three manufacturers: TVT, EverFocus, and DIRECT TV.

Looking at just transactions, data collection terminals were the most active devices across all the categories. The terminals made up more than 80% of the IoT traffic that Zscaler found. The report identified a total of 20 unique data collection terminals from five manufacturers: Chainway, Coppernic, Honeywell, Motorola and Zebra.

If the terminals are ignored, printing devices became the most active category of devices in the transaction analysis. The report found that more than 51% of the remaining IoT transactions were coming from this single category.

They also found devices used for different types of industrial control systems and associated instrumentation (including the devices and systems used to operate and automate industrial processes) present in the enterprise.

Smart industrial networking devices from IXON, Netbiter and Synology were found in the analyzed enterprise logs.

Security practices were found to be uneven in the depth of execution. There were four major classes of security issues they observed, specifically:

      1. Plain-text HTTP communication to a server for firmware or package updates

 

      2. Plain-text HTTP authentication

 

      3. Use of outdated libraries

 

    4. Weak default credentials

Additionally, they found that approximately 91.5% of transactions were occurring over a plain text channel whereas only 8.5% were using SSL.

But, 18% of the total devices used SSL exclusively to communicate. Forty-one percent of devices were using partial SSL ("partial" meaning that there was some communication over SSL and some is over non-SSL channels), while the same percentage (41%) of devices were found to be using no SSL at all for any of their communications. The report also saw that because default IoT device passwords tend to be unchanged following installation, brute-force attacks remained effective.

The top destinations that were connected to by the IoT malware families observed were the US (66%), Canada (12%), France (2.5%), Greece (2.2%) and Russia (2%).

Security concerns need to be addressed by the well-known methods, and the enterprise needs to gain visibility of the shadow IoT devices that are already sitting inside the network so they can address them.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

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...