Thursday, July 5, 2012

Linux Advanced File Permissions - SUID,SGID and Sticky Bit

In this tutorial we will discuss about advanced file permissions i.e the the Sticky, SUID and SGID bits.
I'll write about them because one of my readers told me that it would be a good idea to write about these bits.
After you have worked for a while with Linux you discover probably
that there is much more to file permissions than just the "rwx" bits.
When you look around in your file system you will see "s" and "t"
$  ls -ld /tmp
drwxrwxrwt 29 root root 36864 Mar 21 19:49 /tmp

$  which passwd


$  ls -l /usr/bin/passwd
-rwsr-xr-x 1 root root 22984 Jan  6  2007 /usr/bin/passwd

 What is this "s" and "t" bit? The vector of permission bits is really
4 * 3 bits long. Yes there are 12 permission bits,not just 9.The first
three bits are special and are frequently zero. And you almost always
learn about the trailing 9 bits first.Some people stop there and never
learn those first three bits.

 The forth permission bit is used only when a special mode of a file
needs to be set. It has the value 4 for SUID, 2 for SGID and 1 for the
sticky bit. The other 3 bits have their usual significance.

 Here we will discuss about the 3 special attributes other than the
common read/write/execute:

        1.Set-User-Id (SUID)
        2.Set-Group-Id (SGID)
        3.Sticky Bit
Set-User_Id (SUID):

 By default, when a user executes a file, the process which results in
this execution has the same permissions as those of the user. In fact,
the process inherits his default group and user identification.

 If you set the SUID attribute on an executable file, the process res-
ulting in its execution doesn't use the user's identification but the
user identification of the file owner.

 The SUID mechanism,invented by Dennis Ritchie,is a potential security
hazard. It lets a user acquire hidden powers by running such a file
owned by root.
$ ls -l /etc/passwd /etc/shadow /usr/bin/passwd
-rw-r--r-- 1 root root  2232 Mar 15 00:26 /etc/passwd
-r-------- 1 root root  1447 Mar 19 19:01 /etc/shadow

 The listing shows that passwd is readable by all, but shadow is unre-
adable by group and others. When a user running the program belongs to
one of these two categories (probably, others), so access fails in the
read test on shadow. suppose normal user wants to change his password,
How can he do that? He can do that by running /usr/bin/passwd. Many
UNIX/Linux programs have a special permission mode that lets users
update sensitive system files –like /etc/shadow --something they can't
do directly with an editor. This is true of the passwd program.
$ ls -l /usr/bin/passwd
-rwsr-xr-x 1 root root 22984 Jan  6  2007 /usr/bin/passwd

The s letter in the user category of the permission field represents a
special mode known as the set-user-id (SUID). This mode lets a process
have the privileges of the owner of the file during the instance of
the program. Thus when a non privileged user executes passwd, the eff-
ective UID of the process is not the user's, but of root's – the owner
of the program. This SUID privilege is then used by passwd to edit
What is effective user-id:

 Every process really has two user IDs: the effective user ID and the
real user ID. (Of course, there's also an effective group ID and real
group ID.Just about everything that's true about user IDs is also true
about group IDs) Most of the time,the kernel checks only the effective
user ID. For example, if a process tries to open a file, the kernel
checks the effective user ID when deciding whether to let the process
access the file.

  Save the following script under the name and make it
executable (chmod 755
# print real UID
print "Real UID: $<\n";
# print real GID
print "Real GID: $(\n";
# print effective UID
print "Effective UID: $>\n";
# print effective GID
print "Effective GID: $)\n";

check file permissions:

$ ls -l
-rwxr-xr-x 1 pankaj pankaj 203 Mar 24 10:40

Note: For security reasons the s-bit works only when used on binaries
(compiled code) and not on scripts (an exception are perl scripts).
Scripts,i.e. programs that cannot be executed by the kernel directory
but need an interpreter such as the Bourne shell or Java,can have
their setuid bit set, but it doesn't have any effect. There are some
platforms that honor the s bits even on scripts ( some System V vari-
ants, for example), but most systems don't because it has proven such
a security headache - most interpreters simply aren't written with
much security in mind. Set the SUID bit on shell script is useless,
that's why I am using perl script here.

 When you run the script you will see that the process that runs it
gets your user-ID and your group-ID:
$ ./
Real UID: 500
Real GID: 500 500
Effective UID: 500
Effective GID: 500 500

Note: If you get an error like this:
Can't do setuid (cannot exec sperl)

In Debian install perl-suid using following command:
apt-get install perl-suid

In Centos install perl-suidperl using following command:
yum install perl-suidperl

 Now change owner ship to  another user (Do it as an administrator).
# chown cloud /home/pankaj/
# ls -l /home/pankaj/
-rwxr-xr-x 1 cloud pankaj 203 Mar 24 10:40 /home/pankaj/

Now run the script again.
$ ./
Real UID: 500
Real GID: 500 500
Effective UID: 500
Effective GID: 500 500

 What you observed, the output of the program depends only on the user
that runs it and not the one who owns the file.
How to assign SUID permission:

 The SUID for any file can be set (mostly by the superuser) with a
special syntax of the chmod command. This syntax uses the character s
as the permission. Now add SUID permission to the script :

# chmod u+s /home/pankaj/     (Do it from root account)

Now return from the super user mode to the usual non privileged mode.
$ ls -l
-rwsr-xr-x 1 cloud pankaj 203 Mar 24 10:40

 To assign SUID in an absolute manner, simply prefix 4 to whatever
octal string you would otherwise use (like 4755 instead of 755).

 The file is owned by cloud and has the s-bit set where norma-
lly the x is for the owner of the file. This causes the file to be
executed under the user-ID of the user that owns the file rather than
the user that executes the file. If pankaj runs the program then this
looks as follows:
$ perl
Real UID: 500
Real GID: 500 500
Effective UID: 503
Effective GID: 500 500

 Effective user id of process is 503, this is not the pankaj's , but of
cloud's - the owner of the program. As you can see this is a very powe-
rful feature especially if root owns the file with s-bit set. Any user
can then do things that normally only root can do.

Caution:    When you write a SUID program then you must make sure that
it can only be used for the purpose that you intended it to be used.
As administrator, you must keep track of all SUID programs owned by
root that a user may try to create or copy. The find command easily
locate them:

# find /home -perm -4000 -print | mail root

  The extra octal bit (4) signifies the SUID mode, but find treats the
  "–" before 4000 as representing any other permissions.
Set-Group_Id (SGID):

 The set-group-id (SGID) is similar to SUID except that a program with
SGID set allows the user to have the same power as the group which
owns the program. The SGID bit is 2,and some typical examples could be
chmod g+s or chmod 2755
You can remove SGID bit using following commands:

$ chmod g-s
$ chmod 755 
      (Absolute manner)

 It is really useful in case you have a real multi-user setup where
users access each others files. As a single homeuser I haven't really
found a lot of use for SGID. But the basic concept is the same as the
SUID,Similar to SUID, SGID also grants privileges and access rights to
the process running the command, but instead of receiving those of the
file's owner it receives those of the file's group. In other words,the
process group owner will be set to the file's group.

 I explain it with an example. I have created two user accounts cloud
and pankaj with same home directory project. cloud belongs to cloud and
development groups, pankaj belongs to pankaj and development groups.
# groups cloud pankaj
cloud : cloud development
pankaj : pankaj development

pankaj's default group is pankaj and cloud's default group is cloud.

 Login as cloudand create  file again and make it executable
(using  chmod 755 .
$ id
uid=503(cloud) gid=503(cloud) groups=501(development),503(cloud)
$ ls -l
-rwxr-xr-x 1 cloud development 203 Mar 25 19:00

Now login as pankaj and run the program:
$ id
uid=501(pankaj) gid=504(pankaj) groups=501(development),504(pankaj)
$ perl
Real UID: 501
Real GID: 504 504 501
Effective UID: 501
Effective GID: 504 504 501

The effective GID of the process is the pankaj's,but not of the cloud's
-the owner of the program.

Now login as cloud and assign SGID bit to program:
$ chmod 2755; ls -l
-rwxr-sr-x 1 cloud development 203 Mar 25 19:00

Now login as pankaj and run the program:
$ perl
Real UID: 501
Real GID: 504 504 501
Effective UID: 501
Effective GID: 501 504 501

 Real GID and Effective GID are different,here Effective GID is the
cloud's - the owner of the program.
Set SGID on a directory:

 When SGID is set on a directory it has a special meaning. Files crea-
ted in a directory with SGID set will inherit the same group ownership
as the directory itself,not the group of the user who created the file.
If the SGID is not set the file's group ownership corresponds to the
user's default group.

 In order to set the SGID on a directory or to remove it, use the
following commands:
$ chmod g+s directory     or     $ chmod 2755 directory
$ chmod g-s directory     or     $ chmod 755 directory

 As I mentioned earlier pankaj and cloud's home directory is same that is /home/project. I changed group ownership of /home/project directory to development.
# ls -ld /home/project/
drwxrwxr-x 16 root development 4096 Mar 26 00:22 /home/project/

Now login as cloud and create a temp file.
$ whoami
$ pwd
$ touch temp; ls -l temp
-rw-r--r-- 1 cloud cloud 0 Mar 26 12:34 temp

 You can see from the ls output that the group owner for project is
development, and that the SGID bit has not been set on the directory
yet. When cloud creates a file in project, the group for the file is
cloud (cloud's primary gid).

 Set SGID bit on project directory. For that login as administrator
and set SGID bit using following command:
# chmod g+s /home/project/
# ls -ld /home/project/
drwxrwsr-x 15 root development 4096 Mar 26 12:34 /home/project/

 From the ls output above, you know the SGID bit is set because of the
s in the third position of the group permission set,which replaces the
x in the group permissions.

Now login as cloud and create temp2 file.
$ whoami
$ touch temp2; ls -l temp2
-rw-r--r-- 1 cloud development 0 Mar 26 13:49 temp2

 Notice the group ownership for temp2 file. It inherits group permiss-
ion from the parent directory.

 Enabling SGID on a directory is extremely useful when you have a
group of users with different primary groups worcloud on the same set
of files.

        For system security reasons it is not a good idea to set many
program's set user or group ID bits any more than necessary,since this
can allow an unauthorized user privileges in sensitive system areas.If
the program has a flaw that allows the user to break out of the inten-
ded use of the program, then the system can be compromised.

Sticky bit:

 The sticky bit(also called the saved text bit) is the last permission
bit remaining to be discussed. It applies to both regular files and
directories. When applied to a regular file, it ensures that the text
image of a program with the bit set is permanently kept in the swap
area so that it can be reloaded quickly when the program's turn to use
the CPU arrives. Previously, it made sense to have this bit set for
programs like vi and emacs. Today,machines with ultra-fast disk drives
and lots of cheap memory don't need this bit for ordinary files and
that is also useless.

 However, the sticky bit become a useful security feature when used
with a directory. The UNIX/Linux system allows users to create files
in /tmp, but none can delete files not owned by him. That's possible
because sticky bit set for /tmp directory.

 The /tmp directory is typically world-writable and looks like this
in a listing:
# ls -ld /tmp
drwxrwxrwt 32 root root 36864 Mar 27 12:38 /tmp

 Everyone can read,write and access the directory.The t indicates that
only the user (root and owner of the directory,of course) that created
a file in this directory can delete that file.

 In order to set or to remove the sticky bit, use the following
$ chmod +t directory     or    $ chmod 1754 directory
$ chmod -t directory     or    $ chmod  754 directory

 Note: 754 permissions for a directory are powerful enough to guard
your directories from intruders with malicious intentions, that's why
I used 754 as default,if yow want you can change it.


I logged in as cloud and created a temp file.
$ whoami
$ pwd
$ touch temp; ls -l
-rw-r--r-- 1 cloud  cloud           0 Mar 27 13:44 temp

Now logged in as pankaj and try to delete temp file.
$ whoami
$ rm temp
rm: remove write-protected regular empty file `temp'? Y
$ ls temp
ls: temp: No such file or directory

So what happened? pankaj deleted file owned by cloud.

Assign sticky bit to the project directory.As a owner of the directory
or administrator.
# chmod +t /home/project
# ls -ld /home/project/
drwxrwxr-t 15 root development 4096 Mar 27 13:46 /home/project/

 From the ls output above, you know the sticky bit is set because of
the t in the third position of the other permission set,which replaces
the x in the other permissions.

Now repeat same steps again,then you get the following message:
$ whoami
$ ls -l temp
-rw-r--r-- 1 cloud cloud 0 Mar 27 17:36 temp
$ rm temp
rm: remove write-protected regular empty file `temp'? y
rm: cannot remove `temp': Operation not permitted

Observation: Login as normal user and create a file.
[pankaj@localhost ~]$ touch sample
[pankaj@localhost ~]$ ls -l sample
-rw-rw-r-- 1 pankaj pankaj 0 Dec 21 03:41 sample

Now change permissions to 644

[pankaj@localhost ~]$ chmod 644 sample
[pankaj@localhost ~]$ ls -l sample
-rw-r--r-- 1 pankaj pankaj 0 Dec 21 03:41 sample

Now assign SUID permission.

[pankaj@localhost ~]$ chmod u+s sample
[pankaj@localhost ~]$ ls -l sample
-rwSr--r-- 1 pankaj pankaj 0 Dec 21 03:41 sample

After setting SUID, if you see 'S' then it means that the file has no
executable permissions for that user.

Now remove SUID permission and change permissions to 744. Then assign
SUID permission. You should see a smaller 's' in the executable permi-
ssion position.

[pankaj@localhost ~]$ chmod u-s sample
[pankaj@localhost ~]$ chmod 744 sample
[pankaj@localhost ~]$ chmod u+s sample
[pankaj@localhost ~]$ ls -l sample
-rwsr--r-- 1 pankaj pankaj 0 Dec 21 03:41 sample

Same is applicable for SGID and Stickybit.

1 comment: