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.

Infrastructure Security //

DNS

12/15/2017
09:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Russian DNS Gobbling Up Internet Traffic

BGPMON researchers have found that Russian DNS servers redirected Internet traffic through Russia several times earlier this month. The question is whether it's a test or a harbinger of things to come.

Two incidents that occurred over three hours on December 12 showed how vulnerable the Internet remains to misrouting.

Security firm BGPMON found that for the two incidents of three minutes each, traffic for 80 high-volume sites such as Facebook , Google (Nasdaq: GOOG), Microsoft Corp. (Nasdaq: MSFT) and Apple Inc. (Nasdaq: AAPL) were rerouted to Russia before being transmitted out. Researchers posted notice of this occurrence on their blog.

This unusual routing was done by rewriting the global Border Gateway Protocol (BGP) routing tables used by the Domain Name System (DNS) to push Internet traffic through itself. The BGP makes routing decisions based on paths, network policies or rule-sets that are configured by a network administrator, who is involved in making core routing decisions.

What happened was significant since it was picked up by a large number of other routing ISPs that connected to this rogue path, and several new more specific prefixes that are not normally seen on the Internet were generated by it.

High-volume prefixes were being broadcast; the kind that would attract high levels of traffic.

Now, the Origin Autonomous System (AS) 39523 (DV-LINK-AS) hasn't been seen announcing any prefixes for many years, except for one incident involving Google and Verizon that was also strange. The incident had traffic on its way to Verizon routed through Google, which can't handle it. There were some massive outages because of it.

BGPMON described the node's behavior at that time in this way:

In August Google learned a path to 66.232.224.0/24 (Kohls Department store) with origin 39523. Without knowing more about this prefixes, it looks strange and unexpected for Google to learn a 'Kohls Department store' Prefix via this path.

Now, this latest incident may have been some sort of test run. Considering the already announced plan by Russia to have its own "backup" DNS servers, this current effort could have been some sort of proof of concept that was run to see if the country could do it.

It did.

All of this shows that the connecting ISPs will have to accept that they can never totally trust the DNS routing tables they may get, but will have to add their own filters to the stream. Mistakes can happen due to Intent or from human error. The DNS system is based on trust, and that trust may be fraying.

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
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5615
PUBLISHED: 2020-08-04
Cross-site request forgery (CSRF) vulnerability in [Calendar01] free edition ver1.0.0 and [Calendar02] free edition ver1.0.0 allows remote attackers to hijack the authentication of administrators via unspecified vectors.
CVE-2020-5616
PUBLISHED: 2020-08-04
[Calendar01], [Calendar02], [PKOBO-News01], [PKOBO-vote01], [Telop01], [Gallery01], [CalendarForm01], and [Link01] [Calendar01] free edition ver1.0.0, [Calendar02] free edition ver1.0.0, [PKOBO-News01] free edition ver1.0.3 and earlier, [PKOBO-vote01] free edition ver1.0.1 and earlier, [Telop01] fre...
CVE-2020-5617
PUBLISHED: 2020-08-04
Privilege escalation vulnerability in SKYSEA Client View Ver.12.200.12n to 15.210.05f allows an attacker to obtain unauthorized privileges and modify/obtain sensitive information or perform unintended operations via unspecified vectors.
CVE-2020-11583
PUBLISHED: 2020-08-03
A GET-based XSS reflected vulnerability in Plesk Obsidian 18.0.17 allows remote unauthenticated users to inject arbitrary JavaScript, HTML, or CSS via a GET parameter.
CVE-2020-11584
PUBLISHED: 2020-08-03
A GET-based XSS reflected vulnerability in Plesk Onyx 17.8.11 allows remote unauthenticated users to inject arbitrary JavaScript, HTML, or CSS via a GET parameter.