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/22/2019
08:10 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Suppliers Cut Off Huawei

If Android is to 'fork' following Huawei's isolation, the enterprise needs to begin adjusting the threat models used around employee device use.

It's easy to dismiss last week's Executive Order as posturing in a complicated game of US-China trade relations. Imposed tariffs can always be revoked at a later date.

But the Executive Order issued last Friday bans the sale of many products to the entire Huawei 70-company complex as well. One is not allowed to do business with them, period.

And, by the way, it's not just them. ZTE (which previously paid a massive fine to remain in US business) is also on the "Entity List." Even though the enforcement mechanism for this EO is yet to be released, some major players have reacted to the policy swing with a snap in their step.

Bloomberg reports that, "Chipmakers including Intel Corp., Qualcomm Inc., Xilinx Inc. and Broadcom Inc. have told their employees they will not supply Huawei till further notice, according to people familiar with their actions. Alphabet Inc.'s Google cut off the supply of hardware and some software services to the Chinese giant, another person familiar said, asking not to be identified discussing private matters."

The swiftness of the response as well as the aspect of actually not selling product means those players knew this was coming. They are showing a lack of reactive, flubbering surprise in what they do as well as a uniformity in their common actions. They're serious about this.

Android will no doubt fracture if Huawei has to use the open source flavor of the operating system in its upcoming handsets. Even though the handset maker points to their OS work since 2012, the services which connect to that OS have to mesh for the best performance. And Google will see that they don't by withholding updates.

A new, less secure off-shoot OS must inevitably result when an OS has been fractured/forked from the main body of code. Should it survive and the variant gain usage (these guys have sold a lot of hardware), unpatched OS vulns can skyrocket unless they are controlled. The need for extra security support falls on the Chinese. How well they will perform this task remains an open question, but it's a real security risk to just hope that there will not be problems. Android has faced this kind of fracture problem before, and Google implemented a version control system that eventually got patches installed.

But Google is only committed to servicing existing product. Open source-flavor Android means it won't be put into a position where it has to provide support.

The Android account tweeted that, "We assure you while we are complying with all US gov't requirements, services like Google Play & security from Google Play Protect will keep functioning on your existing Huawei device."

For now.

The enterprise needs to begin adjusting the threat models used around employee device use to take this upcoming Android change into account. It may happen quickly, even though the EO's enforcement details currently remain opaque.

Huawei has delivered security updates for its customers in the past, and it seems that the EO means it will have to continue to do so. Bugs may yet get squashed over time by the world's currently second-largest handset maker.

But the effort needed to deal with another OS variant (bug patched or not) controlling devices that are routinely used by employees for their business can only complicate enterprise security procedures.

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