A number of security problems can be created by commands given carelessly in the configuration file. Such problems can be serious because sendmail starts to run as root, provided that it has not been given an unsafe command-line switch (such as -C; see -C) or an unsafe option (Section 24.2.4). It can continue as root until it delivers mail, whereupon it generally changes its identity to that of an ordinary user. When sendmail reads its configuration file, it can do so while it is still root. Consequently, as we will illustrate, when sendmail is improperly configured, it might be able to read and overwrite any file.
The file form of the F configuration command (Section 22.1.2) can be used to read sensitive information. That command looks like this in the configuration file:
This form is used to read class macro entries from files. It can cause problems through a misunderstanding of the scanf(3) pattern pat. The /path is the name of the file, and the optional pat is a pattern to be used by scanf(3) (Section 188.8.131.52).
To illustrate the risk of the pat, consider the following configuration file entry:
Normally, the F command reads only the first whitespace-delimited word from each line of the file. But if the optional pattern pat is specified, the F command instead reads one or more words from each line based on the nature of the pattern. The pattern is used by scanf(3) to extract words, and the specific pattern used here [^#] causes scanf(3) to read everything up to the first comment character (the #) from each line. This pat allows multiple hostnames to be conveniently listed on each line of the file. Now assume that a new administrator, who is not very familiar with sendmail, decides to add an F command to gather a list of UUCP hosts from the /etc/uucp/Systems file. Being a novice, the new administrator copies the existing entry for use with the new file:
This is the same pattern that was correctly used for /etc/myhostnames. Unfortunately, the Systems file contains more than just host entries on each line:
linda Any ACU 2400 5551212 "" \d\n in:-\r-in: Uourhost word: MublyPeg hoby Any ACU 2400 5551213 "" \d\n in:-\r-in: Uourhost word: FuMzz3.x
A part of each line (the last item in each) contains nonencrypted passwords. Prior to V8.12, an unscrupulous user, noticing the mistaken [^#] in the configuration file, could run sendmail with a -d36.5 debugging switch and watch each password being processed. For example:
% /usr/lib/sendmail -d36.5 -bt < /dev/null ... some output deleted STAB: hoby 1 entered STAB: Any 1 entered STAB: ACU 1 entered STAB: 2400 1 entered STAB: 5551213 1 entered STAB: "" 1 type 1 val 0 0 200000 0 STAB: \d\n 1 entered STAB: in:-\r-in: 1 entered STAB: Uourhost 1 entered STAB: word: 1 entered STAB: FuMzz3.x 1 entered note STAB: local 3 type 3 val 34d00 0 0 0 STAB: prog 3 type 3 val 34d80 0 0 0
Note the third line from the bottom, where the password for the UUCP login into the host hoby is printed. Also note that this is no longer possible with V8.12 and above if sendmail is installed non-set-user-id as recommended.
This example illustrates two rules about handling the configuration file:
Avoid using the F command to read a file that is not already publicly readable. To do so can reveal sensitive information. Even if the scanf(3) option is correct, a core dump can be examined for sensitive information from otherwise secured files.
 Most versions of Unix disallow core dumps of set-user-id root programs.
Avoid adding a new command to the configuration file by blindly copying and modifying another. Try to learn the rules governing the command first.
Another form of the F (File) configuration command is the program form, which looks like this:
Here, the | prefix to the /path tells sendmail that /path is the name of a program to run. The output produced by the program is appended to the class, here X.
To illustrate another potential security risk, consider a configuration file that is group-writable, perhaps by a few administrators who share the job of postmaster. To break into root, the attacker needs to assume the identity of only one of those users and, under that identity, edit the configuration file. Consider the following bogus entry added by an attacker to that configuration file:
Consider further a change to the DefaultUser option (DefaultUser) that causes the default uid and gid to become those of root:
With these changes in place, the program (actually a shell script) called /tmp/.sh is run by sendmail to fill the class X with new values. All this seems harmless enough, but suppose /tmp/.sh does the unexpected:
#!/bin/sh cp /bin/sh /tmp/.shell chmod u+s /tmp/.shell
Here, the Bourne shell is copied to /tmp/.shell, and the set-user-id root bit is set. Now, any user at all can run sendmail and become root:
% ls -l /tmp/.shell /tmp/.shell not found % /usr/lib/sendmail -bt < /dev/null % ls -l /tmp/.shell -rwsr-xr-x 1 root 122880 Sep 24 13:20 /tmp/.shell
The program form of the F configuration command can clearly be dangerous. The sendmail configuration file must never be writable by anyone other than root. It should also live in a directory, every path component of which is owned by and writable only by root. (We'll discuss this latter point in greater detail soon.) If the configuration file is created with the m4 technique, care must be taken to ensure that only root can write to the mc file, and that only root can use that mc file to install the configuration file.
Just as the program form of the F command can pose a security risk if the configuration file is poorly protected, so can the M delivery agent definition. Specifically, the P= equate for a delivery agent (P=) can be modified to run a bogus program that gives away root privilege. Consider the following modification to the local delivery agent:
Mlocal, P=/bin/mail, F=rlsDFMmnP, S=10, R=20, A=mail -d $u becomes Mlocal, P=/tmp /mail, U=0 , F=S rlsDFMmnP, S=10, R=20, A=mail -d $u note note
Here, local mail should be delivered with the /bin/mail program, but instead it is delivered with a bogus frontend, /tmp/mail. If /tmp/mail is carefully crafted, users will never notice that the mail has been diverted. The S flag in the F= equate (F=S) causes sendmail to retain its default identity when executing the bogus /tmp/mail. The U=0 equate (U=) causes that default to become the identity of root.
Delivery agent P= equates must be protected by protecting the configuration file. As an additional precaution, never use relative pathnames in the P= equate.
The F=S and U=0 are especially dangerous. They should never appear in your configuration file unless you have deliberately placed them there and are 100 percent certain of their effect. For example, the local_lmtp feature (FEATURE(local_lmtp)) correctly sets them for the local delivery agent because the mail.local program is no longer set-user-id root.
When sendmail attempts to record its delivery agent statistics (Section 5.4.1), it checks for the existence and write permissions of the file specified by the StatusFile option (StatusFile). Prior to V8.9, sendmail did not care where that file lived or what permissions it hadonly that it existed.
A security problem could arise if one is tempted to locate the statistics file in a spool or temporary area. Consider the following location, for example:
Here, the administrator sets the StatusFile option to locate the statistics file in the /usr/tmp directory. The intention is that the file can be easily created by anyone who wishes to gather statistics for a while, then removed. Unfortunately, the /usr/tmp directory is usually world-writable.
Thus, prior to V8.9, any unhappy or malicious user could bring the system to its knees:
% cd /usr/tmp % ln -s /vmunix statistics
Here, sendmail clobbers the disk copy of the kernel. Nothing bad might happen at first, but the machine will require manual intervention to boot in the future. Clearly, precautions must be taken. For example, any file that sendmail writes to (such as the StatusFile option statistics file or the aliases database files) must be writable only by root and live in a directory, every path component of which is writable only by root.
 Programs that need kernel symbols, such as ps(1), will cease to work or will produce garbage output.
 The savvy administrator can still boot off the network or from a CD-ROM and quickly install a new kernel.