121

Terminal2Shell: Critical flaw grants instant shell access on every major OS

#linuxmemes
Terminal2Shell Terminal2Shell: Critical flaw grants instant shell access on every major OS Researchers disclose a 55-year-old vulnerability affecting macOS, Windows and Linux. Exploitation is trivial and requires no special tools. No patch exists. terminal2shell.com

check post at origin

12 comments

log in to comment.

  • @e0qdk@reddthat.com · 10 Nov 2026

  • @ArmoredThirteen@lemmy.zip · 10 Nov 2026

    Fuck that’s a lot of critical infrastructure that’s vulnerable!

  • @MoonManKipper@lemmy.world · 10 Nov 2026

    Type slower! That made me laugh

  • @Zomg@piefed.world · 11 Nov 2026

    They can’t keep getting away with this

  • @Vitaly@feddit.uk · 11 Nov 2026 · edited

    Ok gang, I guess we’re moving to ms paint 🤷

  • @Mercury1337@lemmy.world · 10 Nov 2026

    Got me for a second! 😅

  • @DmMacniel@feddit.org · 10 Nov 2026

    Me using HaikuOS and AmigaOS: ha suck it!

  • @akunohana@piefed.blahaj.zone · 10 Nov 2026

    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.

    • @lilith267@lemmy.blahaj.zone · 11 Nov 2026 · edited

      Well that is exactly what chroot’ing is, loading up another linux instance so you can modify the local (usually broken) one

      This is intentional behavior as you need physical access to the drive, and most sensitive information is either encrypted by your application(keyring, password manager, password protected files, etc), or you can choose to encrypt your whole drive

    • @stoy@lemmy.zip · 10 Nov 2026

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

    • @rtxn@lemmy.world · 10 Nov 2026

      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.

      • @libewa@feddit.org · 11 Nov 2026

        EFI has a mechanism for filesystem drivers, and the EfiFs project provides a lot of them under the GPL.