Attacks/Breaches
1/7/2010
05:53 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Critical Juniper Router Flaw Triggers Prompt Patching

Vulnerability causes routers to crash and reboot

Juniper Networks yesterday issued a patch for a serious and exploitable flaw in its router operating system that could cause a router to crash altogether.

The critical security alert issued to Juniper customers and partners set off a rare flurry of router-patching last night, security experts say. "It's not atypical to not apply low-criticality patches to core routers. Now that this has been classified as 'critical,' people seem to be reacting," says Daniel Kennedy, a partner with Praetorian Security Group, which has been studying the vulnerability and says it heard many ISPs were already applying the patches last night.

Organizations don't routinely patch routers; they typically don't have the resources to do so, nor is patching a router as high a priority as patching a server, for instance. Some avoid patching because a major breach is less likely than the possibility of an unintentional outage from applying a router update.

And many organizations incorrectly assume their customized router configurations aren't as big of a target. But security experts -- such as Felix "FX" Lindner, who has conducted groundbreaking research on Cisco router vulnerabilities -- have demonstrated that exploiting routers isn't as hard as was once thought.

Dan Kaminksy, director of penetration testing for IOActive, says this Juniper vulnerability should be patched--and fast: "A remote kernel panic on most versions of the second most popular routing platform on the Internet is significant. IT admins should take this threat to their infrastructure seriously, and patch immediately," Kaminsky says.

There has been no sign of an active exploit for the Juniper router vulnerability yet, but the attack works like this: When the router receives a TCP header with a crafted options field, JUNOS, Juniper's router operating system kernel, crashes and the OS reboots. JUNOS' firewall filter is unable to filter the packet, either. Juniper's JUNOS versions 3, 4, 5, 6, 7, 8, and 9 series routers are all affected by the flaw, which basically results in a denial-of-service attack.

"So JUNOS versions released after January are reported to crash upon receiving a TCP packet that ACL filtering will not stop. Per Juniper, there is no real effective workaround, just application of the provided patch," Kennedy says.

Juniper had fixed the problem about a year ago, he says, but apparently discovered recently that the flaw was exploitable while working on an interoperability issue.

The advisory, which was among seven posted and available only to Juniper customers and partners, included a patch and workarounds, according to Barry Greene, director of Juniper's security incident response team. "These are all scheduled security advisories as part of a monthly schedule (similar to Microsoft's Patch Tuesday). All have fixed code available and feasible workarounds which can be used and deployed immediately by our customers," Greene said in a statement.

Meanwhile, Praetorian today tested all 256 instances of the TCP option field in the header, Kennedy says, and found the one that causes the router to crash. "The exploit is thus confirmed," he says.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message. Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3341
Published: 2014-08-19
The SNMP module in Cisco NX-OS 7.0(3)N1(1) and earlier on Nexus 5000 and 6000 devices provides different error messages for invalid requests depending on whether the VLAN ID exists, which allows remote attackers to enumerate VLANs via a series of requests, aka Bug ID CSCup85616.

CVE-2014-3464
Published: 2014-08-19
The EJB invocation handler implementation in Red Hat JBossWS, as used in JBoss Enterprise Application Platform (EAP) 6.2.0 and 6.3.0, does not properly enforce the method level restrictions for outbound messages, which allows remote authenticated users to access otherwise restricted JAX-WS handlers ...

CVE-2014-3472
Published: 2014-08-19
The isCallerInRole function in SimpleSecurityManager in JBoss Application Server (AS) 7, as used in Red Hat JBoss Enterprise Application Platform (JBEAP) 6.3.0, does not properly check caller roles, which allows remote authenticated users to bypass access restrictions via unspecified vectors.

CVE-2014-3490
Published: 2014-08-19
RESTEasy 2.3.1 before 2.3.8.SP2 and 3.x before 3.0.9, as used in Red Hat JBoss Enterprise Application Platform (EAP) 6.3.0, does not disable external entities when the resteasy.document.expand.entity.references parameter is set to false, which allows remote attackers to read arbitrary files and have...

CVE-2014-3504
Published: 2014-08-19
The (1) serf_ssl_cert_issuer, (2) serf_ssl_cert_subject, and (3) serf_ssl_cert_certificate functions in Serf 0.2.0 through 1.3.x before 1.3.7 does not properly handle a NUL byte in a domain name in the subject's Common Name (CN) field of an X.509 certificate, which allows man-in-the-middle attackers...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Dark Reading continuing coverage of the Black Hat 2014 conference brings interviews and commentary to Dark Reading listeners.