Researchers at Finnish security firm Outpost 24 claim to have discovered a flaw in the Internet Protocol that can disrupt any computer or server.
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.
After keeping the flaw quiet for years, the researchers hope that going public will help accelerate the creation of a solution. 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," observes 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 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," says 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," says 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 be feasible. "You basically have to sit there and stare through code and figure out what stages you can get to," Lewis says.
Another reason for revealing the flaw now is that 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 says.