actually at the time of the last fiasco, the current firmware had been vulnerable
but how anybody is still getting hit by this is amazing to me On Wed, Sep 7, 2016 at 7:56 PM, Mathew Howard <mhoward...@gmail.com> wrote: > They weren't necessarily backhauls... but a few firewall rules at the edge > of the network and/or not running ancient firmware would have prevented > it... > > On Wed, Sep 7, 2016 at 6:57 PM, Chris Wright <ch...@velociter.net> wrote: > >> This sums up the kind of person who programs a public IP into their >> backhauls. >> >> http://25.media.tumblr.com/tumblr_m8d8vusNcL1qa9jn1o2_500.gif >> >> Chris Wright >> Network Administrator >> Velociter Wireless >> 209-838-1221 x115 >> >> >> -----Original Message----- >> From: Af [mailto:af-boun...@afmug.com] On Behalf Of Josh Reynolds >> Sent: Wednesday, September 07, 2016 4:47 PM >> To: af@afmug.com >> Subject: Re: [AFMUG] Ubnt password hack with public IP radios >> >> Yep, it was widely talked about on the forum, the Brothers WISP podcast, >> and through direct emails from UBNT to customers who have basically ever >> sent them a working email address for anything.... >> amongst other places. >> >> https://community.ubnt.com/t5/airMAX-Updates-Blog/Important- >> Security-Notice-and-airOS-5-6-5-Release/ba-p/1565949 >> >> >> On Wed, Sep 7, 2016 at 6:42 PM, Jaime Solorza <losguyswirel...@gmail.com> >> wrote: >> > Seems like a local WISP got radios hacked and passwords changed. >> Someone >> > told him there is a virus that sniffs Ubnt radios with public IPs and >> > changes password to Moth3rfuck3r or something like that. Supposedly a >> > telnet script can remedy this matter.... Anyone know about this? Tak >> >> >> >> > -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.
