Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM Version 9.352-6 and 9.318-5 released (Do not install!!)

DO NOT INSTALL - THE UPDATES ARE FAULTY (Read this thread through!)

News

· Security Update
Remarks

· System will be rebooted
Bugfixes

36115 WebAdmin reflective XSS Vulnerability
36126 OpenSSL security update 1.0.1q



This thread was automatically locked due to age.
  • I pulled the trigger on 9.353004 on Friday night and have not noticed or had any issues reported to me as of Monday morning.
  • Myself as well, went from 9.315-2 to latest on 2 UTM's in HA.
  • after the previous botched update, i reinstalled my utm and restored the config, i was hoping the sequence from 9.351-3 to 9.353-4 would be stable, but...
    backend connection errors are back
    flow monitor broken

    does anyone have a quick rollback guide, i dont want to do the whole utm again (vm)
  • Did you try a couple of different browsers? What browser are you using now?
  • yes, both chrome and IE are exhibiting this same issue
    If I open flowmonitor it does not display any info apart from the basic page layout with 'No data available in table' displayed, and then it starts spewing a bunch of 'Backend connection failed, please click Shift-Reload to try again' popups;
    I am about to roll back to 9.351-3 as this is my last working version
  • followup here guys, might help some of you
    i connected to my utm from wan side and the flow monitor works with no backend errors...
    need to confirm if its sorted itself out or if the issue is exhibited internally only

    update:

    been playing around, and have discovered the following:

    connecting to the utm internally (LAN) via my internal DNS nameing causes flow monitor to break and backend connection errors follow shortly after that

    connecting to the utm internally (LAN) via utm's IP address seemingly works fine, flow monitor works and no backend connection errors.

    connectng to the utm using external (WAN) IP and external DNS resolution works fine, FLow monitorw orks and no backend connection errors

    Hope this helps guys out in some way, either in keeping their current builds or in actually tracking down the issues