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

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

  • dino@discuss.tchncs.deEnglish
    14·
    5 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?

    • Kusimulkku@lemm.ee
      6·
      5 months ago

      Some package managers have a command to see if anything is in need of restart. Zypper has ps -s for example. I’d restart to be sure though.

      • dino@discuss.tchncs.deEnglish
        2·
        5 months ago

        My server tells me a restart would be required because of:

        linux-base linux-image-6.1.0-22-amd64

        Does that have anything to do with the SSH package?

        • Kusimulkku@lemm.ee
          2·
          5 months ago

          It sounds like it’s the kernel but whether it has anything to do with ssh, I really don’t know. Sometimes parts work together in surprising ways, as I learned with the recent sshd/systemd/xz exploit.

          You might be fine and this was the most alarming exploit since it’s very inconvenient, but personally I’d restart just to be sure.

    • fakeaustinfloyd@ttrpg.network
      1·
      5 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)