Advertisement
Singapore markets open in 1 hour 24 minutes
  • Straits Times Index

    3,187.66
    +32.97 (+1.05%)
     
  • S&P 500

    5,011.12
    -11.09 (-0.22%)
     
  • Dow

    37,775.38
    +22.07 (+0.06%)
     
  • Nasdaq

    15,601.50
    -81.87 (-0.52%)
     
  • Bitcoin USD

    63,474.11
    +2,177.64 (+3.55%)
     
  • CMC Crypto 200

    1,314.29
    +428.75 (+48.42%)
     
  • FTSE 100

    7,877.05
    +29.06 (+0.37%)
     
  • Gold

    2,395.00
    -3.00 (-0.13%)
     
  • Crude Oil

    82.58
    -0.15 (-0.18%)
     
  • 10-Yr Bond

    4.6470
    +0.0620 (+1.35%)
     
  • Nikkei

    38,079.70
    +117.90 (+0.31%)
     
  • Hang Seng

    16,385.87
    +134.03 (+0.82%)
     
  • FTSE Bursa Malaysia

    1,544.76
    +4.34 (+0.28%)
     
  • Jakarta Composite Index

    7,166.81
    -7,130.84 (-49.87%)
     
  • PSE Index

    6,523.19
    +73.15 (+1.13%)
     

One of Linux's most important commands had a glaring security flaw

Sudo fix my vulnerability.

If you've used the command line in Linux or a Unix-based platform like macOS, you're probably familiar with the "sudo" command -- it lets you run tasks with different (usually elevated) permissions than you'd otherwise have. It's powerful, but it was apparently too powerful until now. Developers have fixed a flaw in sudo that let you claim root-level access even if the configuration explicitly forbids it. So long as an intruder had enough access to run sudo in the first place, they could perform any action they wanted on a given machine.

The quirk revolved around sudo's treatment of user IDs. If you typed the command with a user ID of -1 or its unsigned equivalent 4294967295, it would treat you as if you had root access (user ID 0) even as it recorded the actual user ID in the log. The user IDs in question don't exist in the password database, either, so the command won't require a password to use.

Linux users can update to a newer sudo package (1.8.28 or later) to fix the flaw. You might not be immediately vulnerable, as any attacker will need to have command line control over your system before they can even consider exploiting the flaw -- at that point, you probably have larger problems. Still, it's not entirely comforting to know that such an important command was vulnerable.