ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    OpenSSH Critical Update to Patch Roaming Vulnerability

    News
    ssh openssh security eweek open source
    5
    6
    1.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • mlnewsM
      mlnews
      last edited by

      The OpenSSH project has released a critical patch for their open source network encryption technology to address a flaw that could enable remote access to sensitive systems. Be sure to check your systems for updates immediately.

      stacksofplatesS 1 Reply Last reply Reply Quote 3
      • AmbarishrhA
        Ambarishrh
        last edited by

        Red Hat Enterprise Linux 4, 5 and 6 are not affected by this flaw as they include OpenSSH versions that are older than 5.4; Red Hat Enterprise Linux 7 is affected, i guess that applies to same versions of CentOS

        1 Reply Last reply Reply Quote 1
        • JaredBuschJ
          JaredBusch
          last edited by

          I have zero systems with public access to SSH.

          Definitely want to get this patch in though.

          1 Reply Last reply Reply Quote 0
          • stacksofplatesS
            stacksofplates @mlnews
            last edited by

            I guess it's time for some work when I get to the hotel.

            1 Reply Last reply Reply Quote 0
            • dafyreD
              dafyre
              last edited by

              FTA, this looks like it only affects the SSH clients... Right?

              stacksofplatesS 1 Reply Last reply Reply Quote 0
              • stacksofplatesS
                stacksofplates @dafyre
                last edited by

                @dafyre said:

                FTA, this looks like it only affects the SSH clients... Right?

                "The problem involved a bug that exposed a memory leak to a malicious SSH server," Cox explained. "Because the data in question didn't cross any trust or execution boundaries, the malicious server could get the client to possibly leak sensitive authentication key data."

                I think it's both. I ran my update playbook and everything was patched within about 3 minutes 🙂

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post