Shellshock Bash vulnerabilities

Forums Forums iLive Forums iLive general discussions Shellshock Bash vulnerabilities

This topic contains 7 replies, has 5 voices, and was last updated by Profile photo of SteffenR SteffenR 6 years, 11 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #42557
    Profile photo of JakobExton
    JakobExton
    Participant

    Hi Guys
    I service a iLive system that is a part of a hotels conference services.
    The hotels IT department noticed that the iLive OS is Linux based and since they are reviewing the hotels IT security setup they asked for a review of if and how the iLive might be vulnerable to the Shellshock Bash Bug that can now affect Linux IT systems.
    Although I know that we do not need to fear that bug affecting iLive I am now looking for a quotable informative answer for the IT records… My “trust me, itยดs Ok” just doesn’t cut it ๐Ÿ™‚

    Anyone able to help me out?

    #42595
    Profile photo of tylermartin86
    tylermartin86
    Participant

    After some research, it seems like the iLive will not be vulnerable to the Shellshock bug.

    Regardless, it is mostly a “best practices” thing to not have your sound network connected to the internet. There is no reason for it. You should have separate wires and wireless router for your iLive network.

    #42597
    Profile photo of GCumbee
    GCumbee
    Participant

    Tyler is right. It should not have been or still be online. No reason to be.

    #42602
    Profile photo of JakobExton
    JakobExton
    Participant

    True.
    I would not expose the system to the internet. We however have it set up on a separate IP network dedicated for equipment control and monitoring. There we have stuff like audio DSP, AMX control systems, video matrix switcher, IPTV and various other gizmos. I can not guaranty that some of the In house staff have not brought something on a USB stick to one of the many computers on that network. That possibility is what raised the red flag…

    #42631
    Profile photo of SteffenR
    SteffenR
    Participant

    com on guys, Jakob needs a real answer

    I guess you have to ask direct in the software department,
    maybe Nicola could forward this if you send him a personal message.

    #42635
    Profile photo of tylermartin86
    tylermartin86
    Participant

    I thought my answer was a real answer… But steffen is right. The only true way to be 100% sure of this is to talk to the software department.

    But from my research, the Shellshock bug needs an attacker, not just a USB stick.

    I would still very highly recommend putting the iLive on its own separate network. You wouldn’t want more traffic on the iLive network than you need. If the traffic on the network becomes too much, it may start slowing down the iLive traffic. It all depends on what the router sees as more important.

    #42651
    Profile photo of Nicola A&H
    Nicola A&H
    Keymaster

    This is what I got from our Software team, hope it helps.

    iLive and GLD aren’t running any of the typical exploitation vectors for shellshock. The SSH Server is disabled in normal operation, there is no web server installed, likewise no DHCP or mail server.

    The only TCP port we open for rendezvous is within our firmware control and not bash based.

    The virtual consoles are all password protected.

    We believe this makes an attack very unlikely.

    #42656
    Profile photo of SteffenR
    SteffenR
    Participant

    That’s an answer… ๐Ÿ™‚

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.