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

4/23/2019
07:00 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Networks in Danger as Global BGP Routing Table Reaches Capacity

The Internet is going to run out of address space sometime this month.

In 2014, the Internet came to a shuddering halt because the hardware used in switching packets around the wired networks which connect it all together had no memory left to hold the secret decoder ring it used to handle where those packets were supposed to end up.

Industry players like Microsoft, eBay, LastPass, BT, LiquidWeb, Comcast, AT&T, Sprint, and Verizon all had major hissy-fits.

At that time, the routers normally used could only hold 512K of the global BGP routing table. This is what describes the IPv4 addresses of all the known Internet-connected networks.

Well, after everything came crashing down there were emergency patches made along with the yelling and screaming. They increased the address space to 768,000 routes.

Guess what? The Internet is going to hit that number sometime this month.

A Twitter bot named BGP4-Table has been watching the actual number. As of April 22, 2019 it says "I see 768132 IPv4 prefixes. This is 336 more prefixes than 6 hours ago and 1012 more than a week ago. 57.36% of prefixes are /24. There are 64255 unique originating ASNs. 47612 of these ASNs originate IPv4 only."

If we aren't there, it's a really thin slice away.

But we may not see the rampant outages that occurred last time this happened.

First, sysadmins have known it is coming and proactively changed their equipment.

Secondly, some systems will just pass upstream the addresses they can't handle, like 24-bit prefix routes.

But there are still a lot of older and smaller networks that use Cisco 6509 SUP-720 gear, which are the kind that died in 2014 and would be expected to pull the same stunt this time around. These legacy networks may not escape unscathed.

So, if everything stops working for you real soon consider the network that you are attached to. One element of it may be crippled, and it won't be fixed until firmware gets re-flashed.

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