Severe flaw in WPA2 - cracked

  • 34
  • Question
  • Updated 1 year ago
  • Answered
Photo of Marko Teklic

Marko Teklic

  • 1 Post
  • 0 Reply Likes

Posted 2 years ago

  • 34
Photo of Mike Swedoski

Mike Swedoski

  • 2 Posts
  • 2 Reply Likes
The agent I spoke to had no idea there was an issue, nor any idea if there would even be a response.  I had him create a ticket at priority 2 and I am waiting on an engineer to call me back.

This is rather frustrating.
Photo of David Ogden

David Ogden

  • 3 Posts
  • 2 Reply Likes
Agreed. Especially since this has been a known issue for the manufacturers for a while now. Certainly they should have been quicker at patching the flaw.
Photo of Brad Nance

Brad Nance

  • 3 Posts
  • 1 Reply Like
I opened a case and called our Rep and was told there will be a patch by the end of the day.
Photo of David Ogden

David Ogden

  • 3 Posts
  • 2 Reply Likes
Maybe thats why the Ruckus website is absent of any mentioning the security flaw - probably not posting anything until they have a fix. Pretty damn late to the party if you ask me.

Maybe switching our campus wifi infrastructure to Ruckus was a BAD idea last year. Fortunately I only started with a few buildings. If they don't put out a patch ASAP, it's good riddance Ruckus and Hello Aruba or someone else.
Photo of Kari Hyvönen

Kari Hyvönen

  • 25 Posts
  • 7 Reply Likes
Too bad they didn't tell by the end of which day..
Photo of David Buhl

David Buhl

  • 10 Posts
  • 11 Reply Likes
Chatted with a rep who said there will be a "response" by the end of the day.

I, too, don't understand how you can have 2.5 months to come up with something and "wait til the end of the day" is what they came up with.  

You KNOW there is a MAJOR issue.  You KNOW your customers and competitors will be looking at your response.  You know exactly WHEN the announcement will be made.  And yet, you have NOTHING available.  

"At Ruckus Support, we value Security above all else.  The WPA2 vulnerabilities were just released to the public, but Ruckus engineers have had this information for much longer and have been working tirelessly to address, correct, and test patches for all of our systems.  We will have these available very soon.  Thank you for your patience, we want to make sure we get this one right."

There, took me 2 minutes.
Photo of Brad Nance

Brad Nance

  • 3 Posts
  • 1 Reply Like
I'll bet they copy and paste that for email replies...... 
Photo of SupMang

SupMang

  • 3 Posts
  • 3 Reply Likes
You're hired!
Photo of JC

JC

  • 3 Posts
  • 0 Reply Likes
Dear
Please help with a firmware update for the ZF7363 and ZF7321 models for this new vulnerability found in WPA-2. Is there any way to contact them or all those who are registered will we get an email automatically when they have the update to know that is already available?
Photo of Brad Nance

Brad Nance

  • 3 Posts
  • 1 Reply Like
You will probably want to open a case or check back here to see if they get one out today.

Brad 
(Edited)
Photo of JC

JC

  • 3 Posts
  • 0 Reply Likes
ok, thanks
Photo of JC

JC

  • 3 Posts
  • 0 Reply Likes
Dear
Please help with a firmware update for the ZF7363 and ZF7321 models for this new vulnerability found in WPA-2. Is there any way to contact them or all those who are registered will we get an email automatically when they have the update to know that is already available?
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
Hello!  Let's please use this one thread to communicate until formal Ruckus response is posted please, thanks.

Here is what I can tell you after all the other Wi-Fi company announcements that should elliviate some concerns.
(Edited)
Photo of AJ Schuck

AJ Schuck

  • 1 Post
  • 1 Reply Like
What other thread? that is this thread...
Photo of JesseJ

JesseJ

  • 16 Posts
  • 21 Reply Likes
I am literally face-palming at this point.
Photo of Mike Swedoski

Mike Swedoski

  • 2 Posts
  • 2 Reply Likes
Two+ months to get something together and this guy can't even reply in the right thread.
Photo of David Ogden

David Ogden

  • 3 Posts
  • 2 Reply Likes
So what is it you can tell us? I'm confused by your statement.
Photo of JesseJ

JesseJ

  • 16 Posts
  • 21 Reply Likes
Edited for more face-palm. Are you guys serious right now?
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
The issue is related to 802.11r (fast bss-transition) to enhance roaming, which if disabled on WLANs
eliminates vulnerability to attack of AP-to-client traffic.  The krackattacks.com site describe it as:
“it works by exploiting a four-way handshake that's used to establish a key for encrypting traffic. During the third step, the key can be resent multiple times. When it's resent in certain ways, a cryptographic nonce can be reused in a way that completely undermines the encryption.”

WPA2/AES - attacker can decrypt and replay wi-fi packets.
WPA2/Auto-TKIP - attacker can decrypt, replay and inject frames

It requires that the attacker be physically in range of your APs, performing a man-in-the-middle impersonation
of a true AP mac address.

WLAN configuration options on WLANs, default setting is 802.11r Fast Roaming disabled. (SZ 3.5.1).

This is a Client vulnerability issue.  A man-in-the-middle with AP sending your SSID and using your AP
MAC address.  If one of your clients joins this malicious AP, there is a hole in the client that allows the
client to connect even if the passphrase is not correct(!). 

After this happens this, and only this single client, can be sniffed.

Our product is designed to alert Admins if such a rogue AP is present.  Only AP manufacturers who use their
APs as RAPs in Mesh (ie connecting to Guest WLAN) are vulnerable (as Aruba stated).

Things to think about:
1) all current certs and Wi-Fi passwords are still secure (attacker doesn't get the pw)
2) AES does not allow for code injection (tkip does, don't use it).
3) Android 6 has more issues that might make this attack easier.
4) Disabling 802.11r will mitigate the attack
5) Patching either side (client or distribution system) stops the attack from happening on WLAN
6) MITM attacks can happen if attacker inserts a new cert, end user is prompted with cert error.
7) Do not move to WEP

Still waiting for a corporate Security message I can post to Support and will share here.  Thanks.
(Edited)
Photo of JesseJ

JesseJ

  • 16 Posts
  • 21 Reply Likes
Given the information above, it does not constitute waiting 6 of your PDT working hours (2PM PDT) to produce what was given. There isn't enough clarification given to soundly say simply disabling 802.11r on a Ruckus products will fix the issue either - this was not the full scope of the vulnerability. At this point in the day I am worried about the dismissive tone and action to the issue. I hope the formal security message doesn't ring this way as well.

Put simply, most other vendors have a fix or at the very least a statement as of hours ago on this. Regardless of how critical other vendors thought this would be they have addressed their end. I don't resonate with updating our endpoints instead, turning off the 802.11r feature on our devices, or anything other than fixing the vulnerability through firmware. You should have already deployed your new firmware/patches and put your obligation to rest. It's concerning this is not remotely the case.
Photo of Scott Savarese

Scott Savarese

  • 1 Post
  • 0 Reply Likes
Has anyone thought about the possibility that they might not have been notified until today? Has anyone seen evidence that RW was notified 2 months ago? This whole thread seems to expect that given 8 hours notice a company can analyze a vulnerability, patch code, do complete regression testing, and release patches. 
Photo of David Buhl

David Buhl

  • 10 Posts
  • 11 Reply Likes
They are a major player in the wireless market.  They've said all major players were notified a couple of months ago.  I can't see any possibility where someone forgot a company in the top 5, based on market share.
(Edited)
Photo of James Hudson

James Hudson

  • 1 Post
  • 4 Reply Likes
https://www.kb.cert.org/vuls/byvendor?searchview&Query=FIELD+Reference=228519&SearchOrder=4

They were given notice at the same time as every other company.
Photo of Charles Sprickman

Charles Sprickman

  • 21 Posts
  • 10 Reply Likes
And even if they work, there should be at LEAST one security nerd there who would have seen the initial announcement and started salivating at figuring out what the root of the vulnerability was.  As has been noted, some vendors even broke "embargo" and fixed this more than a month ago (OpenBSD was scolded, Mikrotik apparently was not).  If Ruckus doesn't have one of "those guys", god help us.

Here's what the message to management should be, and it should STING:
  • Ubiquiti had a fix before you
  • Ubiquiti sent an email blast to customers before you informing them of the vulnerability and the fix
  • Mikrotik had a fix before you - yes, the Latvians beat you too
  • Both companies called out above are seen as barely beyond consumer grade stuff in some circles (and in some Ruckus sales pitches)
  • All the enterprise vendors had a fix out before you (but Ubiquiti is the one that should embarrass you)
  • Many of your customers read about this elsewhere and are aware that you had the information about this problem in-hand back in August
Photo of Delroy McLean

Delroy McLean

  • 1 Post
  • 1 Reply Like
Any updates on a timeline for this patch?  My customers are screaming!
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
The first official advisory is from our Cloudpath ES Security product team:

https://support.ruckuswireless.com/documents/2039-faq-security-advisory-cp-101617-802-11r-vulnerabil...
(Edited)
Photo of David Buhl

David Buhl

  • 10 Posts
  • 11 Reply Likes
I don't mean to pile-on, now that there is an official response, but...

This advisory is full of grammatical errors, contradictions, and the very first line expresses doubt this is even a problem.  Waiting all this time to come out with this just furthers the idea that there was no plan and someone started slapping this response together at 8am this morning.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
New updated copy received from PM and posted, thanks.
Photo of Abhi Maras

Abhi Maras, Employee

  • 22 Posts
  • 14 Reply Likes
Thanks for the comments David. Please note this is a Cloudpath response and Cloudpath is not involved in the 4 way WPA2 handshake. Please do look out for a more comprehensive update that will cover Access Points and Controllers soon.
Photo of Network Infrastructure

Network Infrastructure

  • 1 Post
  • 1 Reply Like
Is there an ETA for the update to be posted?
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
Photo of David Buhl

David Buhl

  • 10 Posts
  • 11 Reply Likes
Michael, maybe you can clear up some confusion for me on this.  In the bulletin above, Ruckus is saying: "No Ruckus products are affected unless deployed in Mesh or Point-to-Point topologies, or 802.11r is enabled."  

However, a blog post, also from Ruckus, says the following:
  1. Vulnerabilities exist on both sides of the 4-way handshake relationship (client and AP) and both sides need to be patched.
  2. Until client vendors provide updates, disabling 802.11r can help mitigate the attack by eliminating one source of vulnerability (Fast BSS Transitions, otherwise known as 802.11r roaming).
Does turning off 802.11r mitigate the issue, or does it eliminate the issue?  Semantics, but extremely important semantics. 

If vulnerabilities exist on both sides of the 4-way handshake, and vendors need to patch them to make them secure (and Ruckus uses WPA)... ???  The blog post and the official statement appear to be contradicting each other.  I'd prefer NOT to go back and tell my bosses that I was wrong with what I told them last night.

Thanks,
Photo of Chris W

Chris W

  • 1 Post
  • 1 Reply Like
So do users need to have some support contract to work with a ZD1105?
Photo of tech support

tech support

  • 7 Posts
  • 14 Reply Likes
Ruckus, where are the firmware updates?! This is a pathetic response.
Almost every other manufacturer has firmware fixes available and you don’t. Even Netgear does for their consumer routers!
It is beyond belief that you clearly did not take this seriously, and STILL don’t it would seem.
Time to dump Ruckus. This is not an enterprise product, and certainly not enterprise level support.
Photo of Robert Lowe

Robert Lowe

  • 218 Posts
  • 50 Reply Likes
My issue is more a fact that the advisory doesn't state when a fix will be available. How can i go to my customers with anything unless i can give them a timescale on firmware patch?
Photo of Kari Hyvönen

Kari Hyvönen

  • 25 Posts
  • 7 Reply Likes
This is my first touch with Ruckus.
A month ago, I inherited a position in a company where the wireless network is done with 6x Ruckus R500 Wireless APs.
Yesterday I contacted Ruckus support and they promised firmware by the end of the day. I have to say, that first impression I got from Ruckus is not an enterprise class and will probably move to ubiquiti.
Photo of Ruben Herold

Ruben Herold

  • 7 Posts
  • 15 Reply Likes
I don't think he is too harsh here, cause the are sitting on it since july.  Yes he should blame cisco also but we are here about ruckus.  As I wrote I have some expection to an enterprise support:


1. No out of office notification if someone mails to your security contact ([email protected])
   This E-mail has to go to an high priorized and monitored queue in an ticket
   system,

2. That your support people and partners would inform one or two day's before
   the public disclosure.

3. That you have the right communication for all your customers ready and put
   it in the right time on the right places (webside, newsletter, twitter...)

4. That you have your firmware fixes ready to deploy and if it is possible
   some advanced monitoring ready for this issue and for broken clients.

and nothing had happened. If they would know from the problem since yesterday we can discuss, but not sitting since months on it....
Photo of Kari Hyvönen

Kari Hyvönen

  • 25 Posts
  • 7 Reply Likes
Yesterday I opened a support case about poor wifi performance after upgrading to the latest firmware. A tech promised to call me today at 3pm. Well, no call at 3pm, 4pm or 5pm. Replied to email I got ([email protected]) and guess what? Got out of office reply! I'm speechless.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
Sorry Kari, bad TSE!  Don't make promises you can't keep, but if something did come up today, out of office should direct all current customers to please contact us and ask to be re-queued to TSEs currently on shift to take over!
Photo of Steven Veron

Steven Veron

  • 20 Posts
  • 4 Reply Likes
I can say from experience, that sometimes other reps get copied on your case with Ruckus and I have gotten an out-of-office reply and still got answered. 
Photo of Kari Hyvönen

Kari Hyvönen

  • 25 Posts
  • 7 Reply Likes
Sorry Michael, didnt have any reply from Ruckus and could not wait longer. I went ahead and downgraded firmware of my APs. Very very bad mark for Ruckus.
https://forums.ruckuswireless.com/ruckuswireless/topics/r500-slow-troughput-high-latency-high-packet...
Photo of Ruben Herold

Ruben Herold

  • 7 Posts
  • 15 Reply Likes
hi,

I have read the Ruckus Security Advisory and also
https://theruckusroom.ruckuswireless.com/wi-fi/2017/10/16/commonsense-approach-uncommon-problem/ and many other stuff.

This all show ruckus in a very bad light. Can we still trust?

Ruckus was informed many weeks/months ago about this issue and the disclosure date.

But the customers was left alone!!

I was informed since two day's (CET timezone) about this issue. I waited for
the public disclosure yesterday and opened a case at ruckus cause no information
about it was found online.

All other major vendors did have the updates ready and informed their customers
at the same time the issue was going public. They had their communication ready
and send it out to their partners and customers at the right time.

Ruckus didn't they don't even inform the partners!!

What I as customer with contract and as partner has expected:

1. No out of office notification if someone mails to your security contact ([email protected])
   This E-mail has to go to an high priorized and monitored queue in an ticket
   system,

2. That your support people and partners would inform one or two day's before
   the public disclosure.

3. That you have the right communication for all your customers ready and put
   it in the right time on the right places (webside, newsletter, twitter...)

4. That you have your firmware fixes ready to deploy and if it is possible
   some advanced monitoring ready for this issue and for broken clients.

What I now expect:

1. really fast update availability, even for older systems and without contract*

2. transparent communication what went wrong and why

3. better documentation and reporting how to fix the problem in our company's,
   not even on the wireless system side:

    * How to detect clients with this problem
    * For which clients are updates available


I'm located in germany, the public  disclosure was now nearly 24hour away,
even the radio stations here  broadcast informations about this issue faster
then you.

At this morning the German Federal Office for Information Security has send out
an public announcement that all people should update their clients and
accesspoints / routers if possible or contact their vendors for updates.

The phones are ringing with customers, cto's and so on. All want to have a
status about this issue and a dead line then it is fixed.

Yes the major problem are the client's, but the accespoints and controllers
should be fixed also and I expect that I get some help from my wireless system
to detect the problem on the clients if I have a managed wireless solution
not one single accesspoint.

Our company has already rolled out the patcheѕ for our clients.
Even microsoft has the patches already in place.

For me it looks like ruckus has ignored the advisory and now the
try to react on it. This has nothing todo with enterprise support!!

There is absolute no excuse for this!!

For me the trust in your security support is gone, and there must
be very good arguments that we will stay with ruckus after our contract
ended.


* cause how it was happend (see what I expected)
Photo of alexf

alexf

  • 34 Posts
  • 9 Reply Likes
btw there is github repo maintaining a list of vendor responses: https://github.com/kristate/krackinfo . Go to Vendor Response Matrix and see client updates.

Regards, 
Alex
Photo of Ruben Herold

Ruben Herold

  • 7 Posts
  • 15 Reply Likes
I think there should be a way, have you taken a look what other vendors do:

Q:  Can I detect if someone is attacking my network or devices?

A:  Aruba software checks for replay counter mismatches on a per
client basis and will produce a log message if detection is triggered. The log message begins with “Replay Counter Mismatches“, followed by additional details.

Aruba has also released new RFProtect (WIDS) features and signatures to help detect attacks.

for example.

Also it should be no problem to build a list with patches for the major systems
and publish them.

If I read this right:

"Here, the client will install an all-zero encryption key instead of reinstalling the real key."

They work with an all-zero key can this not be detected from the wirless system?
Photo of JesseJ

JesseJ

  • 16 Posts
  • 21 Reply Likes
"Be professional ... If you have customers that rely on WPA only, then they deserve to be under attack."

Wow Jakob, do you work at Ruckus?

I appreciate they finally took the time to tell us not to worry about anything unless you use features that are turned off by default, or mesh networking </sarcasm>. Thanks for assuming most costumers don't care as they would rarely deploy a mesh network, right?

https://www.ruckuswireless.com/rucktionary/mesh-networking-and-smartmesh
http://www.ruckussecurity.com/Smart-Mesh-Networking.asp
http://ruckus-www.s3.amazonaws.com/pdf/appnotes/bpg-wireless-mesh.pdf

You can't flaunt it and be proud of this as a value add, and then chastise customers for using it when there's a security issue you have no urgency to address.
Photo of Charles Sprickman

Charles Sprickman

  • 19 Posts
  • 9 Reply Likes
That blog post ("the ruckus room") is embarrassing.  They don't even mention if they have a fix in the pipeline.  Telling their customers who use "mesh" to "turn it off" is stupid.  It's a feature, don't be surprised if people use it.
Photo of Charles Sprickman

Charles Sprickman

  • 19 Posts
  • 9 Reply Likes
That blog post ("the ruckus room") is embarrassing.  They don't even mention if they have a fix in the pipeline.  Telling their customers who use "mesh" to "turn it off" is stupid.  It's a feature, don't be surprised if people use it.
Photo of John Taylor

John Taylor

  • 8 Posts
  • 1 Reply Like
Does anyone know how 7731 bridges are affected by this?
Photo of Michael Brado

Michael Brado, Official Rep

  • 2793 Posts
  • 393 Reply Likes
For 7731, P300, and mesh deployments, there is noknown workaround for CVE-2017-13077, CVE-2017-13078, CVE-2017-13079,CVE-2017-13080, and CVE-2017-13081.  However, because Ruckus products useCCMP for Mesh and bridging connectivity, exploitation of these vulnerabilities ismade significantly difficult, as per Section 6.1 of the KeyReinstallation Attacks: Forcing Nonce Reuse in WPA2 report.  
Photo of Magnus Söderbom

Magnus Söderbom

  • 2 Posts
  • 1 Reply Like
Regarding 7731: So there goes an otherwise fully functional, still going strong, work horse bridge between our two offices? Discontinued product = no patch?

Or..?

 
Photo of John Taylor

John Taylor

  • 8 Posts
  • 1 Reply Like
The 7731 has reached End of Sale but has NOT reached the End of Software Development.  Ruckus owes us a patch for the 7731's.
Photo of Steven Veron

Steven Veron

  • 20 Posts
  • 4 Reply Likes
I would like an update on this for the 7731 as well. The Security Advisory only mentions a patch for the P300, nothing about the 7731. 
Photo of Chad Sarvis

Chad Sarvis

  • 2 Posts
  • 1 Reply Like
They've updated the bulletin to include the 7731. No date set for the fix but it is on the list.
https://ruckus-www.s3.amazonaws.com/pdf/security/faq-security-advisory-id-101617-v1.2.txt
Photo of Pete

Pete

  • 3 Posts
  • 5 Reply Likes
Open-Mesh announced they will have a firmware upgrade this afternoon (10/17/2017). Open-Mesh, the product which gives a you free lifetime license for their cloud controller, you just need to purchase the hardware. Not sure why it's taking Ruckus so long.
Photo of Phil Lochner

Phil Lochner

  • 12 Posts
  • 4 Reply Likes
Ruckus, you better get your crap together and resolve this. You're already being snickered at in a few of the sysadmin mailing lists I'm part of.

In a couple more days those snickers are going to turn into turn into something much more damaging. Because you're such a big player in the wifi market, you're already getting mocked for not having a fix ready when it was announced, but at least right now you're lumped in with tons of other companies.

As the days go on those other companies are going to deliver their patches and you're going to be left out in the rain, tossing excuses and copy pasta to frustrated sysadmins with leftover end of year budgets they'll rightfully decide to spend somewhere else.

We love our Ruckus products but your lack of progress in this matter means to be secure, we may have to turn off our products, and we can't have that in our organization, so we're simply forced to switch vendors.
Photo of Affant Communication

Affant Communication

  • 1 Post
  • 4 Reply Likes
Is it safe to assume that Ruckus doesn't give a damn about their paying customers right? Since the patches are no were to be seen... I would like to ask the community for Ubiquity recommendations since we'll most likely be moving over. 
Photo of Todd

Todd

  • 65 Posts
  • 17 Reply Likes
I'm sure this will not be a popular comment but, I think some of these comments are blown way out of proportion.  I also am not happy about Ruckus's delay of response and available firmware updates given the lead time they've been given.  But they don't have it.  I wouldn't apply the new code immediately anyway until some of you bled on it.  I'm willing to bet that most of us have bigger security issues to deal with than a proof of concept hack on a single device, which requires them to be physically on-site, setup a rogue AP and write there own code for the exploit, as the code to exploit the vulnerablity isn't in the wild, then they might gain access to someones facebook feed.  LOL

In addition can I borrow some of your budget dollars so I can jump vendors whenever I'm unhappy with their performance.  Thats a luxury that I cannot afford, time or money wise.   :)
Photo of Jakob Peterhänsel

Jakob Peterhänsel

  • 90 Posts
  • 29 Reply Likes
Jesse,
All I'm saying is: If security is that important for your customers, that they are calling you even before the scope of this vulnerability is out in the open (it's still a lab case), then they should already be using Apps that use SSL communication directly between the client app and the backend.
Oh, and if you've read the krack site, it's mostly a clientside issue
Photo of Steven Veron

Steven Veron

  • 20 Posts
  • 4 Reply Likes
I work at a university. Should I tell all our students to use VPN? While for sensitive information requiring VPN use should be done, it's not practical in all situations. 

I think another aspect of this is the PR side. When the CIO says they have people asking "does this affect us" it shouldn't require a long explanation of "yes, but only if you're not using VPN, not using secure apps, etc etc. 
Photo of JesseJ

JesseJ

  • 16 Posts
  • 21 Reply Likes
Jakob,

You can play Ruckus' cards all you want. "It's still a lab case..." Really? If I could prove there was another WPA2 vulnerability to where you could steal the PSK, but it wasn't in the wild yet, would you expect Ruckus to have a patch before somebody packaged up in a nice little tool for script kiddies? Would you care if you could just update Windows to mitigate the new threat? Apparently you wouldn't, and that makes you incompetent and naive in network security. I won't address your other noise again about apps using SSL.

Nobody is arguing that we shouldn't have to patch our clients, but even they have stated to patch BOTH. Well we can't do that yet. According to the latest word that will be two weeks away at the earliest for 'some' devices. Now we are waiting on a managers response about how everything is just fine, so long as 'xyz' is in place, or not in use. That's not acceptable. If you wanted to reassure everyone of the risks to certain features and the network safety otherwise, that should have been in the day one security brief assuring us of this with an ETA date on the firmware releases and which models.

An example of how to respond correctly (even spelling out which things aren't effected if that's your stance):
https://help.ubnt.com/hc/en-us/articles/115013737328-Ubiquiti-Devices-KRACK-Vulnerability
Photo of Jakob Peterhänsel

Jakob Peterhänsel

  • 90 Posts
  • 29 Reply Likes
Playing Ruckus' card - Really? Gezus..
All I'm saying is: keep the perspective! This thread is going nuts over how all wifi is suddenly useless, when facts is, it's not!This thread is going nuts over how all security is suddenly compromised and peoples highly secret communications is at risk, and I'm simply pointing out: It the communications it that secret, you should have other security measures in place!
I'm not fond if how Ruckus is handling this either, but stop making the world come to and end over this, when in fact it's not.
Photo of JesseJ

JesseJ

  • 16 Posts
  • 21 Reply Likes
I wouldn't say 'the world', I'd say Ruckus' reputation.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
Thank you valued Customers and Partners for your patience as final action plans have been worked out.

(In response to questions such as “where is my patch” and “why is this taking so long”?)

 

Providing patches for affected products is our first concern and we understand its urgency to your business. We expect patches for most firmware releases to be available on October 30th, with all patches to be completed by November 15th. In the interim, the following steps will minimize risk:

-  Disable 802.11rwherever enabled. This step eliminates the short-term need for patches to Ruckus infrastructure in all but the two scenarios described below.

-  Enable rogue detectionmechanisms and ensure clients connecting to a rogue AP are de-authenticated.

-  Patch client devices asthose patches become available. Unpatched clients will continue to be a risk tonetwork security, regardless of what other steps are taken.

 

With the above steps taken, two Ruckus use cases and products continue to pose a network security risk: meshed APs and point-to-point links. That risk is minimized through use of rogue AP detection and subsequent corrective action.

 

Full protection against KRACK will be assured once all infrastructure software has been updated (and 802.11r re-enabled) and all clients have been updated.

 

Note: Ruckus will provide software updates to anyone requesting them, regardless ofsupport contract status.
(Edited)
Photo of Daniel M

Daniel M

  • 52 Posts
  • 12 Reply Likes
Really? Sometime between October 30th and November 15th? Ruckus had known about this for how long? Has Ruckus bothered to see how quickly their competitors got patches out? Impressive to see how succinctly the ball has been dropped here.
Photo of Ruben Herold

Ruben Herold

  • 7 Posts
  • 15 Reply Likes
Hi Michael,

have you seen my statement to this issue.  I think your statement can be the seen as first step to bring it on track. Especially:

"
Note: Ruckus will provide software updates to anyone requesting them, regardless of support contract status."

Plese take a look at my posting:

https://t.co/uVikcz9kRF

Can you give some statements to this?

Now tthe problem exists that ruckus was not ready for this problem. So let us not do
the fingerpointing let us find solutions. As described in my posting I see some expections:


1. really fast update availability, even for older systems and without contract*

2. transparent communication what went wrong and why

3. better documentation and reporting how to fix the problem in our company's,
   not even on the wireless system side:

    * How to detect clients with this problem
    * For which clients are updates available


You have us shown point 1 about the speed we can discuss but it is
necessary that the patches are stable and working. So If you have startet with
the development too late the dates you announced are fine from my point if view.

Now my points 2 and 3 is missing. Can you tell us something about it and can you make it public please?

To get the trust from your userbase it is necessary to show us what went wrong and why and what will be take in place to prevent this happening the next time.
Photo of Luis Gustavo Coelho

Luis Gustavo Coelho

  • 1 Post
  • 0 Reply Likes
Note: Ruckus will provide software updates to anyone requesting them, regardless ofsupport contract status.

How exactly would this happen, should I open a ticket for our contract-less ZD5000 controllers, and Ruckus will provide update images?
Photo of M

M

  • 36 Posts
  • 5 Reply Likes
Disappointing response from Ruckus. If other major vendors were able release a patch after lifting the embargo, why can't Ruckus? Disabling 802.11r mitigates risk for now but I've deployed many Mesh APs on one of our clients because of structured cabling challenges.
Photo of Steven Veron

Steven Veron

  • 20 Posts
  • 4 Reply Likes
I'm just surprised they didn't push it off on a VAR to fix, that's what they have been doing for support at my company :D 
Photo of Jeff W

Jeff W

  • 16 Posts
  • 5 Reply Likes
@Michael Brado

As per your earlier statement "Note: Ruckus will provide software updates to anyone requesting them, regardless of support contract status"

Can you please explain the process of how to perform software updates on ZD's with expired contracts.  Who we may have to contact etc etc.

I have the following ZD's i'd like to upgrade when the patches are made available approx. Oct 30.
ZD 1106 9.8
ZD 1200 9.9
ZD 1200 9.13
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
Hello, our VP announced overnight that the ZD entitlement server will allow upgrades thru January 31st, 2018.

This should be active now Robert and community.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
Greetings,

 

      Ourdevelopers/QA beat the projected schedule for a WPA2 KRACK fixed version

of ZoneFlex for the 7731 PtMTPbridges.  These files are now available for download

from the Support portal at theseURLs.  The KRACK Support Resource Center has also

been updated with this releaseinformation. 

 

ZoneFlex 7731 Release9.2.0.0.181 (GA Refresh6) Release Notes:

https://support.ruckuswireless.com/products/20-zoneflex-7731#documents

 

ZF7731 Firmware 9.2.0.0.181(+WPA2 KRACK patches):

https://support.ruckuswireless.com/software/1546-zf7731-firmware-9-2-0-0-181-wpa2-krack-patches

 

Ruckus Wireless KRACK SupportResource Center:

https://support.ruckuswireless.com/krack-ruckus-wireless-support-resource-center
Photo of Magnus Söderbom

Magnus Söderbom

  • 2 Posts
  • 1 Reply Like
Cannot download the update from my guest support account due to :
"That file is only available to Premium Support users."

despite Ruckus statement "Note: Ruckus will provide software updates to anyone requesting them, regardless of support contract status".

Am I missing something or have Ruckus not made the file available?
Photo of Max O'Driscoll

Max O'Driscoll, AlphaDog

  • 349 Posts
  • 95 Reply Likes
I'm guessing you have to do the "requesting" bit.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
Hello, my mistake when I posted the 7731 code yesterday.  No premium support
contract required, but you do need to have a guest account / be registered. 

The access permissions are corrected now. Please try your download again.
Thanks and best regards.
(Edited)
Photo of Robert Lowe

Robert Lowe

  • 218 Posts
  • 50 Reply Likes
Interested to know if anyone has had any response from Ruckus about older versions of code and if patches will be available. Their official announcement on when a patch will be available only goes back to 9.10
https://support.ruckuswireless.com/krack-ruckus-wireless-support-resource-center?_ga=2.221041560.149...
Photo of Jakob Peterhänsel

Jakob Peterhänsel

  • 90 Posts
  • 29 Reply Likes
If they have 7025 AP's, it was End Of Sale'd on may 31 2015, end EOL'ed nov. 30 2014.That is 3 years ago.While 'the job they were bought to perform' might still be valid, you've known for 3 years that this product is EOL.Your luck, though, is that the model is still under support for another year - have they bought support? You write: No. 
If Ruckus put's out upgrades for systems without valid support contracts, they are in luck - but you've gotta admit:

1: They are on 3+ year old system2: They have not bought into support
How in the world do they think they can expect support?
Anyway, they 7025 does not even, as far as I know, support 802.11r, so they flaw is not even on their system!They have to make sure the clients are updated.
Photo of Jakob Peterhänsel

Jakob Peterhänsel

  • 90 Posts
  • 29 Reply Likes
Reg. 'written off'.
Here in Europe, at least, it's common practice to make sure IT equipment is written off within 3 years. You simply budget with a replacement after 3 years.You can hope not to have to spend the budget, but it's good practice to have the budget. 
Photo of Robert Lowe

Robert Lowe

  • 218 Posts
  • 50 Reply Likes
And will you be replacing all of the newly installed AC Wave 1 installations in 2 years time when Ruckus drops support for the full range after AX is released?

Whether they have support or not is irrelevant if the hardware is stopping them from upgrading. 

Jokob, i'm based in the UK and have worked enough around Europe to know that it is not common place at all. Maybe in certain verticals, large enterprise for example, yes. But a blanket statement that its common place for the budget to replace IT equipment every 3 years, especially if still functioning perfectly adequately, i find hard to believe.

There are other flaws that just 802.11r. There is Mesh and there is the option on the wireless vendor to introduce additional measures in AP firmware to mitigate client side vulnerabilities by rejecting variations in the replay counters from that stored by the AP for example. As far as I know Ruckus hasn't confirmed exactly what will be released as part of the patch yet. You cant always ensure all clients are updated especially with guest networks.  

Anyways, we are getting away from the point here, my question was simply to ask if anyone had had conversations with Ruckus about older versions of firmware that 9.10.  
(Edited)
Photo of Kari Hyvönen

Kari Hyvönen

  • 25 Posts
  • 7 Reply Likes
I find this discussion a bit hilarious :-) I've been working in IT in Finland for over 15 years, seen a wide variety of companies from small to large. It's highly unlikely to replace wlan APs every three years. Or switches, or storage arrays or servers. Laptops and mobile phones usually.

Anyways, I bought Asus RT-N56U for home in early 2011. At first it was missing some nice-to-have functions, which I emailed Asus. And guess what? After a while they released new FW with the featrures I had asked for. And FWs kept on coming. The latest FW was released in March 2017, over 6 years after I bough the device. 

Couple of weeks back I emailed Asus asking if they are releasing firmware to address WPA2 krack, and yes, they are although they couldn't give me the date yet. :-) Now that I call customer care. No registrations, no support agreements, just go to the website, download and update. No doubt, my next home AP will be Asus. Not because they'd be technically ahead of others, but because they listen and care about their customers.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2793 Posts
  • 393 Reply Likes
We have now posted WPA2 KRACK patched ZoneDirector 9.7.2, 9.8.3, and will have 9.9.1 by 10/22/17, as earlier than 10.x mentioned.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2803 Posts
  • 395 Reply Likes
With an update on this thread, see current WPA2 KRACK patch relase details on the Support
Resource Center page:

https://support.ruckuswireless.com/krack-ruckus-wireless-support-resource-center

There are SmartZone updates for 3.1.2, 3.2.1, 3.4.2, 3.5.1, ZoneDirector 9.7.2, 9.8.3,
9.9.1 (12/22/17), 9.10.2, 9.12.3, 9.13.3, 10.0.1, Unleashed 200.5, Ruckus Cloud 17.01b42
Xclaim 2.2.0.0.39, and P300 100.1 and yesterday zf7731 9.2.0.0.181 for Point to Point bridges.

We've also posted SmartZone AP CLI scripts to diable EAPOL retries in zone versions
3.1.2, 3.2.1, 3.4.2, 3.5.1, and 3.6.0 to provide protection to vulnerable wireless clients.

- Michael
(Edited)