SecPod

Learn Search

Search across all Learn content

← Back to Expressions & POVs
ALERT: Superusers could run into Super trouble

ALERT: Superusers could run into Super trouble

Linux users, beware! One of the most powerful and well known command line utility, sudo, could aid users to gain superuser privileges in spite of the existing restrictions. With sudo being installed in almost all flavors of UNIX-like operating systems, a major number of users could possibly be affec...

Oct 14, 2019By Nitish B2 min read
credits: www.securityaffairs.co
credits: www.securityaffairs.co

Linux users, beware! One of the most powerful and well known command line utility, sudo, could aid users to gain superuser privileges in spite of the existing restrictions. With sudo being installed in almost all flavors of UNIX-like operating systems, a major number of users could possibly be affected. Who said security was easy? So, a vulnerability management solution is critical in such cases.

Right, let’s get down to business. sudo vulnerability assigned with CVE-2019-14287 and termed as Security Policy Bypass, the vulnerability lies in the Runas specification of sudo’s /etc/sudoers file. Any unprivileged user or a malicious application could make use of this security loophole and run root commands despite the fact that Runas specification disables root access. Auto patching can patch this sudo vulnerability.

Origin of Sudo:

The origin and meaning of the word ‘sudo’ is a bit archaic and stands for ‘superuser do’. sudo lets you run commands with privileges of other users and by default, superuser. The User Id (UID) of a superuser is 0.

Majority of the Linux systems with default configurations have ‘ALL‘ in the Runas specification. These machines remain unaffected. However, if sudo is configured to allow execution of commands as an arbitrary user. The user can still run commands as root.

Here’s how it works. Consider this configuration where the user secpod has the privileges to run ‘cat’ command as any other user except root.

plaintext
secpod = (ALL, !root) /usr/bin/cat

This disables execution of commands with superuser privileges for secpod. However, this bypassed by using the User ID “-1“. Or its unsigned equivalent “4294967295“.

plaintext
sudo -u#-1 cat /etc/saner/status.ini

Also, ss shown, the user secpod is able to gain root privileges. Whoops!

In a bid to fix the flaw. However, the vendor has released patches on all Linux platforms and strongly recommends updating to 1.8.28.

Also, please refer to this KB Article to apply the patches using SanerNow.

Featured Posts

Open Vulnerability Backlog Is not Just A Remediation Problem

Vulnerability Backlog Is not Just A Remediation Problem

Point of View

Vulnerability Backlog Is not Just A Remediation Problem

A growing vulnerability backlog is one of the biggest concerns for security leaders, and it has become even more pressing as AI accelerates vulnerability discovery. When organizations look for ways to reduce that backlog, the focus usually turns to remediation. The reasons are familiar. Patching tak

Sep 21, 2026

Open Application Vulnerability Assessment Explained
Application Vulnerability Assessment Explained

Point of View

Application Vulnerability Assessment Explained

Sep 18, 2026

Open Vulnerability Assessment Solutions Explained
Vulnerability Assessment Solutions Explained

Point of View

Vulnerability Assessment Solutions Explained

Sep 18, 2026

Open Choosing the Right Architecture for Continuous Cloud Protection
Choosing the Right Architecture for Continuous Cloud Protection

Point of View

Choosing the Right Architecture for Continuous Cloud Protection

Sep 18, 2026