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.

Risk

2/24/2008
12:00 AM
Commentary
Commentary
Commentary
50%
50%

A Bad Day at Pakistan Telecom

Sometimes I think I should have been a network engineer. I love all that "belly of the internet beast" stuff—giant high-speed routers, huge data pipes, and all things close to the backbone of the Internet. But then I remember my grades from my engineering classes, and why I dropped engineering, and switched my major to English. Perhaps the engineer who broke both YouTube and the Pakistani Internet yesterday should have switched his major, too, before it was too late. I mean, I

Sometimes I think I should have been a network engineer. I love all that "belly of the internet beast" stuff—giant high-speed routers, huge data pipes, and all things close to the backbone of the Internet. But then I remember my grades from my engineering classes, and why I dropped engineering, and switched my major to English. Perhaps the engineer who broke both YouTube and the Pakistani Internet yesterday should have switched his major, too, before it was too late. I mean, I wouldn't want to be that guy right now. Would you want to be the guy who kept Pervez Musharraf from getting to his MySpace page?

It all stems, of course, from Pakistan's recent directive to its country's ISPs to block YouTube because of videos of those supposedly blasphemous Dutch cartoons. Yes, that again. Won't die, will it? In a nutshell, when someone in Pakistan modified some routing tables to direct all Pakistani traffic to YouTube into a black hole, the routing information escaped national boundaries by way of Hong Kong, and began routing worldwide YouTube traffic to that Pakistani black hole. Whoopsie. I give credit to Ars Technica for a detailed and fascinating explanation of the underlying problem.

Apparently, the problem was corrected in a couple hours, and the consensus seems to be that it was an accident. If it was a concerted attack, or a test of attack methods, it certainly would have been a clumsy one, since it essentially resulted in a DDOS attack on the hypothetical attacker's own country. About as effective as a lit stick of dynamite strapped to a boomerang, really.

But that doesn't mean there isn't a huge vulnerability underlying this whole incident. It's conceivable that an attacking country (or other entity), if it were well prepared and didn't care all that much if innocent bystanders got cut off from the world, could use this routing vulnerability to strike at an enemy. It all depends on how desperate they are, and how willing they are to cripple the Internet as a whole. Gee, it doesn't seem too difficult to think of one or two groups who might fit that bill.

I suppose there's reason to hope that this incident will throw the spotlight back on a vulnerability that we've known about for years, but have never gotten around to fixing. That fix won't be easy, but clearly it's necessary.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31664
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-33185
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
CVE-2021-33186
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-31272
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.
CVE-2021-31660
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 85da504d2dc30188b89f44c3276fc5a25b31251f contains a buffer overflow which could allow attackers to obtain sensitive information.