Please wait while the page is being loaded Skip this advertisement >
ARN

Researchers caution against TCP/IP weakness

After keeping the flaw quiet for years, the researchers hope that going public will help accelerate the creation of a solution.
Brenno de Winter (WebWereld Netherlands)  01 October, 2008 11:42:00

Researchers at Finnish security firm Outpost 24 claim to have discovered a flaw in the Internet Protocol that can disrupt any computer or server. After keeping the flaw quiet for years, the researchers hope that going public will help accelerate the creation of a solution.

The flaw allows attackers to cripple computers and servers by sending a few specially formed TCP/IP packets. The result can be compared to a denial of service attack, in which networks are flooded with traffic. But in the case of the newly revealed flaw, only a minimum of traffic is required. "We're talking 10 packets per second to take down one service," Jack Lewis, a senior researcher with Outpost24 told Webwereld, an IDG affiliate.

Researchers at Fox-IT, a Dutch security firm, confirm the issue. "Based on the available information, this vulnerability may be a serious problem for system availability," observed Erwin Paternotte, a researcher with Fox-IT. "If the technical details are publicly disclosed, performing a denial-of-service attack will become relatively trivial."

The problem surfaced during a test scan of 67 million Internet hosts. The researchers were alerted when a test caused some hosts to become unresponsive. Further investigation led to an issue in the TCP/IP stack. After a connection is successfully made, important system resources are at the attacker's disposal.

Each operating system is affected by the flaw, although different systems respond in different ways. "Each operating system does behave differently, of course. You might notice with OS X that a couple attacks that don't seem to bother too much completely devastate Windows XP and the other way around," said Lewis.

The researchers have crafted proof-of-concept code that demonstrates the issues. They claim that they haven't seen a single implementation of TCP/IP that wasn't vulnerable. Systems furthermore will remain unresponsive after an attack. "After the attack is over, the system never seems to recover until it is rebooted," said Robert Lee, Outpost24's chief security officer.

Firewalls or intrusion prevention systems are unable to mitigate the flaw, because they too support TCP/IP and are therefore a potential attack target.

The researchers so far have conceived five different attack scenarios, but they argue that as many as 30 would feasible. "You basically have to sit there and stare through code and figure out what stages you can get to," Lewis said.

The researchers are publicizing their finding after keeping quiet for three years, although they don't plan to fully disclose all the flaw's details. "We hope we can raise awareness and get more people that are smarter than us involved in looking for a solution," Lee said. Just because we can't think of a solution doesn't mean there isn't one, just that we haven't thought of it yet."

But there is another reason. Lee and Lewis see the migration toward IPv6 as a risk that could aggravate the situation. IPv6 "only makes the issue bigger, because the address space is bigger," Lee said.

The Finnish CERT is coordinating research into the security issue and education to software vendors affected by the flaw.

Lee and Lewis will present their findings on Oct. 17 at the T2 security conference in Helsinki.

A podcast interview in English with the researchers can be found on De Beveiligingsupdate.

Comments

Some minor corrections...

1) Outpost24 is a Swedish company, though we do have a Finnish office.

2) Jack's last name is spelled Louis.

3) "The researchers were alerted when a test caused some hosts to become unresponsive."

What actually happened: After performing a large scale test trying to complete a 3-way handshake with and pull down the website content from millions of hosts, certain systems became overly responsive. They kept sending responses to us over and over again until those systems were rebooted. We were not launching an attack against millions of hosts.

4) "Systems furthermore will remain unresponsive after an attack"

That is only true in very specific circumstances. The more universal case is that the service under attack will remain unresponsive as long as the attack continues.

The podcast (http://debeveiligingsupdate.nl/audio/bevupd_0003.mp3) is still the most complete public source of information for these findings.

Also the blog - http://blog.robertlee.name will be updated with more information over time.

Post new comment

Users posting comments agree to the ARN comments policy.
Login or register to link comments to your user profile, or you may also post a comment without being logged in.
The content of this field is kept private and will not be shown publicly.
Enter the fully qualified URL, eg. http://www.example.com/
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

Syndicate content
 
ARN Vendor Directory
ARN Community Comments
ARN Library

RSA - Where Online Fraud is Going

Where Online Fraud is Going: An Insight into Emerging Threats and Changing Fraud Patterns The basic workings of online fraud can be directly correlated to “ real-world” crime.

Subscribe to ARN

ARN has been the premier provider of information to the Australian IT channel for more than 12 years. As the only weekly publication dedicated to the channel, ARN produces timely, accurate news and analysis about IT business issues, products and services, new technology and market opportunities.
Sponsored Links