• Articles
    • Editorial Articles
    • Research Articles
    • WatchGuard Articles
  • The 443 Podcast
  • Threat Landscape
  • About
    • About Us
    • Contact Us
    • Contribute to Secplicity

Secplicity - Security Simplified

Powered by WatchGuard Technologies

Linux Vulnerability: sudo Configuration File

October 16, 2019 By Emil Hozan

Joe Vennix of Apple Information Security discovered a vulnerability pertaining to the ever popular “sudo” command used in Linux systems. If you’re not aware of what sudo is used for, sudo allows non-administrative users (e.g., normal, unprivileged users) to execute commands as another user or, most commonly, the superuser (i.e., root). This is sometimes necessary to have access to system resources that requires root access. One example would be running a tcpdump command to capture network traffic.

CVE-2019-14287 is a security policy bypass issue that attackers could use to execute arbitrary commands. The CVE information states that if users have sudo privileges to run commands except as root, then the following command would effectively allow them to bypass the security mechanisms in place:

sudo -u#-1 id -u 

OR

sudo -u#4294967295 id -u

 

Seclists.org provided an example of a user configuration setting within the /etc/sudoers configuration file as:

myhost bob = (ALL, !root) /usr/bin/vi 

This configuration allows the user (“bob”) to run the “vi” command as any user EXCEPT for root (“!root”). That said, calling the sudo command with the above parameters would allow “bob” to run the “vi” command as root. Here is a YouTube video demonstrating this vulnerability.

 

Key Takeaways

Systems are only vulnerable if and only if a user is configured with the “ALL” keyword within the parenthesis; a.k.a. the “Runas” specifier. For example, the following entry wouldn’t allow a user to bypass the security mechanisms in place:

emil = /usr/bin/id

The above example would allow that user (“emil”) to run the “id” command only as root. Attempting to use the command as any other user will be denied.

Lastly, this isn’t really any issue if you don’t have users specified in the sudoers configuration file. Regardless if this doesn’t apply to you, I suggest updating sudo to be on the safe side.

Share This:

Related

Filed Under: Editorial Articles Tagged With: linux, security bypass, sudo

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

The 443 Podcast

A weekly podcast featuring the leading white-hat hackers and security researchers. Listen Now
the 443 podcast

Threat Landscape

Filter and view Firebox Feed data by type of attack, region, country, and date range. View Now
threat landscape

Top Posts

  • US National Cybersecurity Strategy
  • Here Come The Regulations
  • Successfully Prosecuting a Russian Hacker
  • Cybersecurity’s Toll on Mental Health

Email Newsletter

Sign up to get the latest security news and threat analysis delivered straight to your inbox

By signing up you agree to our Privacy Policy.


The views and opinions expressed on this website are those of the authors and do not necessarily reflect the policy or position of WatchGuard Technologies.

Stay in Touch

Recent Posts

  • An Update on Section 230
  • Here Come The Regulations
  • US National Cybersecurity Strategy
  • Cybersecurity News: Free Cybersecurity Training, TrickBot Group Exposed, Major GoDaddy Breach, and Russia to Legalize cybercrime?!
  • Cybersecurity’s Toll on Mental Health
View All

Search

Archives

Copyright © 2023 WatchGuard Technologies · Cookie Policy · Privacy Policy · Terms of Use