No announcement yet.

A New Release Of GRUB 2.0 Fixes Security Issue

  • Filter
  • Time
  • Show
Clear All
new posts

  • A New Release Of GRUB 2.0 Fixes Security Issue

    Phoronix: A New Release Of GRUB 2.0 Fixes Security Issue

    It was just about two weeks ago that GRUB 2.0 moved closer to release with version 1.97 finally making it out the door after being just shy of two years without a new release. GRUB 1.97 brought Mac OS X kernel support, EXT4 file-system support, support for RAID 4/6/10, high-resolution timer support, support for loading FreeBSD/NetBSD/OpenBSD kernels, and many other changes...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    GNU/Hurd support, just what I need!

    But no, good thing it got patched swiftly for that fun exploit


    • #3
      Correction for the article

      Originally posted by phoronix View Post
      log-in just entering "p" or "nix" or any other part of the string -- even just one character
      The bug report says differently.

      Originally posted by
      GRUB accepts user input as valid password as long as user enters some first
      characters of password correctly.
      Not any part of the string will do, only those which are a valid prefix of the string are valid input.

      Ex, if the password is phoronix,
      valid input is

      but not "nix" or "ron" or any other part.


      • #4
        Worst strcmp implementation ever

        I read this story, and though, ok, who thought it was a good idea to write their own strcmp. And how do you make that kind of mistake? Well, it turns out you make that kind of mistake by starting with a really convoluted loop in the first place:

        Here's the first commit that tried to fix the bug, where you can see the old

        corrected to, since it was using ptr2 uninitialized.

        The loop looks like its trying to do something if the user types more characters than the stored password. I still don't see how anyone came up with that mess, and haven't made the effort to figure out exactly how it behaves for every input. I'm a fan of the trinary operator, but that loop just made my eyes glaze over.

        Fortunately Robert Millan rewrote Vladimir Serbinenko's grub_auth_strcmp function the sane way

        while adding a delay to defend against passwd guessing

        So now it's just basically
        return strcmp(input, template);
        like it should have been in the first place! Don't write complicated logic when you can use standard string functions. Even in a stand-alone program like GRUB where you have to provide your own strcmp.