Researchers disclose a 55-year-old vulnerability affecting macOS, Windows and Linux. Exploitation is trivial and requires no special tools. No patch exists.
  • Taleya@aussie.zoneEnglish
    4·
    18 minutes ago

    Saw this scrolling All, took me a sec (it’s early am). Just about shat meself, i just finished fucking patching 350 deb boxes for the goddamn PHP cve and CA debacles

    • jj4211@lemmy.world
      2·
      10 minutes ago

      Thanks, I changed my bank account to have 100 million dollars with that one weird trick.

  • jj4211@lemmy.world
    12·
    5 hours ago

    Don’t even joke, I would not be surprised if our security team latched onto this unironically.

    • ozymandias117@lemmy.worldEnglish
      4·
      3 hours ago

      That’s kind of the point. Security teams have stopped doing any risk assessment after Heartbleed, and now all it takes is a pretty website to have a “real” vulnerability

  • silenium_dev@feddit.org
    4·
    5 hours ago

    Jokes on you, my server has no terminal, not even a shell (I use Talos, everything is managed via mTLS protected API)

  • printf("%s", name);@piefed.blahaj.zoneEnglish
    5·
    11 hours ago

    This does however make me wonder if it’s possible to interact with a Linux system without first logging in. Some bootloaders have a shell and I think there’s also a UEFI shell? No idea what they are capable of, though.

    • Err(()).unwrap()@lemmy.worldM
      7·
      10 hours ago

      Not directly. UEFI itself only supports mounting a minimal set of filesystems. That’s why your EFI system partitiion needs to be FAT32, for example, and why the kernel and initial ramdisk are also located there. UEFI mounts the ESP and executes the bootloader, which then loads the kernel (located at ESP/vmlinuz-linux on Arch) and initial ramdisk (ESP/initramfs-linux.img) into memory. The initial ramdisk is a compressed image of an early root filesystem that contains the tools and drivers necessary to boot the full system, including the filesystem drivers for ext4/btrfs/whatever.

      You could build an EFI program that natively supports different filesystems, though.

    • stoy@lemmy.zipEnglish
      2·
      11 hours ago

      I mean you can easily edit grub at boot and boot straight into single user mode without logging in.