Cisco and Juniper reveal DoS attack vulnerabilities

News

Cisco and Juniper reveal DoS attack vulnerabilities

Antony Savvas

Users of Cisco and Juniper equipment were facing the prospect of denial of service (DoS) attacks this week after the discovery of security flaws in their networking products.

Cisco, which issued patches this week to prevent DoS attacks via three of its phone systems, has now admitted serious flaws in a large number of its router products, which allow DoS attacks to crash customer networks.

Businesses using routers that support multi-protocol label switching (MPLS) to manage data traffic flow more efficiently are one of three groups facing the new threat.

Users of 2600, 2800, 3600, 3700, 3800, 4500 and 4700 series routers, and users of 5300, 5350 and 5400 series Access Servers are being urged to install a Cisco patch to close the security hole.

In addition, all Cisco users running Cisco’s Internetworking Operating System (IOS) with IP Version 6 (IPV6)-enabled routers face a DoS threat, as do IOS users running Cisco’s network traffic manager Border Gateway Protocol (BGP).

Cisco has issued patches for these customers too.

Juniper Networks has admitted that all customers who are using versions of its JUNOS router operating software created before 7 January - most JUNOS customers - are facing remotely triggered DoS attacks.

More details on the JUNOS vulnerability are available on the customer only part of the Juniper website.

More details on the Cisco vulnerabilities are available here:

http://www.cisco.com/en/US/products/products_security_advisories_listing.html


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.
 

COMMENTS powered by Disqus  //  Commenting policy