cross-posted from: https://lemmy.pt/post/5733711

A severe vulnerability in OpenSSH, dubbed "regreSSHion" (CVE-2024-6387), has been discovered by the Qualys Threat Research Unit, potentially exposing

  • tmpod@lemmy.pt
    hexagon
    ·
    3 months ago

    musl isn't vulnerable, as per https://fosstodon.org/@musl/112711796005712271

    The exploit isn't that practicable, since it takes a very long time on 32 bit systems, which are ever rarer to see.

    • Telorand@reddthat.com
      ·
      3 months ago

      They could get RasPis below 4th gen running outdated software, I guess. I think I read elsewhere that Debian already had a patch out some time ago, so that number is also likely diminishingly small.

  • dino@discuss.tchncs.de
    ·
    3 months ago

    Question if I update my server and it has the new SSH (patched) package. Is that enough or do I have to restart the server as well? How can I check if the old SSH is in use currently?

    • fakeaustinfloyd@ttrpg.network
      ·
      3 months ago

      For anyone in RHEL / Fedora land (or using dnf somewhere else), try dnf needs-restarting to list executables that have mismatched files on disk vs memory. The -r flag will hint if a reboot is needed (due to things like kernel or glibc changes)

    • lengau@midwest.social
      ·
      edit-2
      3 months ago

      The packages in most distros will also restart the server for you. Any existing SSH sessions will technically be running in vulnerable versions, but if I'm understanding the vulnerability correctly this isn't a problem, as they won't be trying to authenticate a user.

      If you want to be sure, you can manually restart the ssh server yourself. On most distros sudo systemctl restart sshd should do it.

  • ssm@lemmy.sdf.org
    ·
    3 months ago

    Worth noting this only affects the portable release of OpenSSH, so OpenBSD (or anyone else using the native release) are unaffected.