bugtraq - RE: Sudo tricks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <003401c65358$beb7ecb0$648ea8c0@burtonstrauss.local>
Date: Wed, 29 Mar 2006 11:46:42 -0600
From: "Burton Strauss" <Security@...llNetSolutions.com>
To: <bugtraq@...urityfocus.com>
Subject: RE: Sudo tricks

Isn't the real meat of this issue the commands an unprivileged user is
permitted to execute via sudo?

Sudo isn't a blanket 'execute anything' unless it's set up that way.
Instead, you should carefully choose the specific command(s) that the user
needs to be allowed to execute.  That should involve execution from an
absolute path and a protected binary.

For example, if visudo contains this

/sbin/ifconfig eth0

Then all the user can execute is the ifconfig command from the protected
binary in /sbin/ifconfig to see the state of the interface.

Or this

/sbin/ifconfig eth0 *

Allows him/her full control of eth0 - but still from the protected binary in
/sbin/ifconfig.

If you specify this:

ifconfig eth0 *

Then all bets are off...

-----Burton