The following releases are out today (or will be) according to an email from SonicWall overnight. They include “critical security fixes” and “should be applied immediately” according to the message.
• 6.5.4.4-44v-21-2457 (for Gen6 NSv)
• 7.0.1-5161 (Gen7)
• 7.1.1-7058 (Gen7)
• 7.1.2-7019 (Gen7)
Yet I can’t find anything about the issues that have been addressed. Will create a support case to obtain more information, but that will take who knows how much time. Anyone have links to CVEs that have been addressed, or other information?
That’s weird because I upgraded to 7.1.1-7058 last week, and it had already been released for a couple of weeks. I just looked in MySonicwall and I don’t see version 7.1.2-7019 AT ALL. Last firmware I show is 7.1.1-7058 that was released on June 19
Updated and all the routes vanished, so had to reimport the config after updating… Then shortly after traffic stops flowing, then starts again, and stops again. Rolling back now, as its unusable.
Following. I saw the update available for our TZ270, but I’m not seeing it available for NSA4700. When I checked locally on the TZ, it showed as no firmware being available. I’m installing now on the TZ to test…
Now I’m new to SonicWall NSM, having just moved to the SaaS product from our old on-prem GMS server which was rickety and failing. Let’s not talk about the cost of NSM (it’s ridiculous but necessary to manage our fleet of TZs and NSa’s), let’s just look at the management capabilities… and… wait a second…
Where the f@&k is the new firmware in NSM?! We’re practically BEGGED to apply these updates the day before they’re released, sight unseen, and now as I’m paying through the nose for this SaaS management service I’m supposed to manually download each model’s firmware and upload them to the service to pass to my firewalls? HOW IS THIS BETTER THAN GMS?!
/rant off
But seriously, SonicWall, today has basically nailed your coffin closed for us. We will not be renewing any of the licensing for our 55 firewalls. The MSP we’re merging with has an investment in WatchGuard and Cisco. We were toying with sticking to SW but not now. Ludicrous pricing, lack of features, terrible reporting, and now this mess… just too much to ask of us.
Interesting, so possible to mitigate this by editing the inbound IKE rule to only allow connections from IP addresses to/from which there are IPSEC tunnels in use, I guess?
These disappeared after you upgraded? If so, what version did you upgrade to, out of curiosity? I never knew about these options until now, and I’d sure like to have them if possible.