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.

Network Security

11/14/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Google Data Center Traffic Rerouted to Nigeria, China & Russia

For over an hour this week, some Internet traffic from Google's data centers was rerouted through a Nigerian ISP and possibly sent to Russia and China.

For 74 minutes on Monday, November 12, traffic from Google's data centers was hijacked, essentially a de facto distributed denial-of-service attack.

BGPmon, a firm which tracks the path of Internet traffic, was the first to report the hijacking. The firm observed as a Nigerian ISP -- MainOne -- electronically told other nodes in its network that it was now hosting a number of IP addresses that belonged to Google's data center. This was, of course, not true.

However, the routing announcement had the effect of diverting traffic that should have been sent to Google to be sent to MainOne.

Since MainOne has a "peering" relationship with China Telecom, the incorrect routes were propagated from China Telecom through TransTelecom to NTT and other transit ISPs. MainOne also has a peering relationship with Google -- through a relationship with IXPN in Lagos -- and direct routes to Google, which leaked into China Telecom as well.

ThousandEyes, another traffic monitoring firm, was also observing the situation. Researchers there noted in their blog that "the outage not only affected G Suite, but also Google Search as well as Google Analytics."

The specific path of the data raised eyebrows as well. First, the traffic to Google was getting dropped by the edge routers at China Telecom. Additionally, a Russian entity -- the TransTelecom ISP mentioned previously -- was found to be in the traffic path.

As ThousandEyes detailed it:

This also put valuable Google traffic in the hands of ISPs in countries with a long history of Internet surveillance. Overall ThousandEyes detected over 180 prefixes affected by this route leak, which covers a vast scope of Google services.

In the last few weeks, concern has been prevalent regarding China Telecom's past history of Border Gateway Protocol (BGP) takeovers, as delineated in a Naval War College article. The article has political overtones in its analysis, but the major findings have since been confirmed by Oracle's Internet Intelligence Division.

This existing concern created a high anxiety about the routing problem, especially since it was cutting Google's business services off from a large chunk of the world's users.

In its own blog post, Google noted: "Throughout the duration of this issue Google services were operating as expected and we believe the root cause of the issue was external to Google."

MainOne finally confessed to the world on Twitter on November 13.

In other words: "Move along, internet. Nothing to see here but a bad filter."

The way that the Internet routes traffic through itself is based on a protocol developed in the 1980s that has no security embedded. It is long overdue for a revamp. This latest episode shows how one node in the net can functionally take everything down by a simple mistake.

Related posts:

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