manual/misc/security_tips.html

	security_tips.html revision 8ea6a26406513706b84fbb279a1b3faf54760d6f
d176f84ce5ca2073f4dfbafb457b9c74f6bf0d76Timo Sirainen<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
863f2bc9983c33221f5936421fc9c06caf21639aTimo Sirainen<HTML>
d176f84ce5ca2073f4dfbafb457b9c74f6bf0d76Timo Sirainen<HEAD>
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<TITLE>Apache HTTP Server: Security Tips</TITLE>
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen</HEAD>
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<BODY
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen BGCOLOR="#FFFFFF"
d176f84ce5ca2073f4dfbafb457b9c74f6bf0d76Timo Sirainen TEXT="#000000"
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen LINK="#0000FF"
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen VLINK="#000080"
863f2bc9983c33221f5936421fc9c06caf21639aTimo Sirainen ALINK="#FF0000"
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen>
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<!--#include virtual="header.html" -->
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<H1 ALIGN="CENTER">Security Tips for Server Configuration</H1>
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen<HR>
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen<P>Some hints and tips on security issues in setting up a web server. Some of
ca44a6ba994aaa3231a20ef6e046dfd97a8dcd2dTimo Sirainenthe suggestions will be general, others specific to Apache.
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<HR>
8dec8eab222cb7a0b4ef5e066cb1d7dac8a526d1Timo Sirainen
8dec8eab222cb7a0b4ef5e066cb1d7dac8a526d1Timo Sirainen<H2><A name="serverroot">Permissions on ServerRoot Directories</A></H2>
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<P>In typical operation, Apache is started by the root
ca44a6ba994aaa3231a20ef6e046dfd97a8dcd2dTimo Sirainenuser, and it switches to the user defined by the <A
a64adf62fa33f2463a86f990217b0c9078531a40Timo SirainenHREF="/mod/core.html#user"><STRONG>User</STRONG></A> directive to serve hits.
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo SirainenAs is the case with any command that root executes, you must take care
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainenthat it is protected from modification by non-root users.  Not only
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainenmust the files themselves be writeable only by root, but so must the
1358e2c58ce29231485a5cfa454756d429ad3d2cTimo Sirainendirectories, and parents of all directories.  For example, if you
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainenchoose to place ServerRoot in <CODE>/usr/local/apache</CODE> then it is
c1847a38dfbc8bad29547d96432ef9d707dbd345Timo Sirainensuggested that you create that directory as root, with commands
b28a1c61a5d262fd16b46bebe47dbfb90ac9c5fcTimo Sirainenlike these:
c1847a38dfbc8bad29547d96432ef9d707dbd345Timo Sirainen
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen<BLOCKQUOTE><PRE>
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen    mkdir /usr/local/apache
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen    cd /usr/local/apache
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen    mkdir bin conf logs
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen    chown 0 . bin conf logs
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen    chgrp 0 . bin conf logs
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen    chmod 755 . bin conf logs
cd18d7bb3e8d5921c3c852bd0a27fbeff9a9babbTimo Sirainen</PRE></BLOCKQUOTE>
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen
a64adf62fa33f2463a86f990217b0c9078531a40Timo SirainenIt is assumed that /, /usr, and /usr/local are only modifiable by root.
a64adf62fa33f2463a86f990217b0c9078531a40Timo SirainenWhen you install the httpd executable, you should ensure that it is
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainensimilarly protected:
149089b97827554ffd17dbf0cbc990b2301703f3Timo Sirainen
149089b97827554ffd17dbf0cbc990b2301703f3Timo Sirainen<BLOCKQUOTE><PRE>
149089b97827554ffd17dbf0cbc990b2301703f3Timo Sirainen    cp httpd /usr/local/apache/bin
149089b97827554ffd17dbf0cbc990b2301703f3Timo Sirainen    chown 0 /usr/local/apache/bin/httpd
1358e2c58ce29231485a5cfa454756d429ad3d2cTimo Sirainen    chgrp 0 /usr/local/apache/bin/httpd
c1847a38dfbc8bad29547d96432ef9d707dbd345Timo Sirainen    chmod 511 /usr/local/apache/bin/httpd
b28a1c61a5d262fd16b46bebe47dbfb90ac9c5fcTimo Sirainen</PRE></BLOCKQUOTE>
149089b97827554ffd17dbf0cbc990b2301703f3Timo Sirainen
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<P>You can create an htdocs subdirectory which is modifiable by other
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainenusers -- since root never executes any files out of there, and shouldn't
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainenbe creating files in there.
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen
a64adf62fa33f2463a86f990217b0c9078531a40Timo Sirainen<P>If you allow non-root users to modify any files that root either
9f0f2de10e4ea0c99052bf4b2bef8179f2536228Timo Sirainenexecutes or writes on then you open your system to root compromises.
a64adf62fa33f2463a86f990217b0c9078531a40Timo SirainenFor example, someone could replace the httpd binary so that the next
time you start it, it will execute some arbitrary code.  If the logs
directory is writeable (by a non-root user), someone
could replace a log file with a symlink to some other system file,
and then root might overwrite that file with arbitrary data.  If the
log files themselves are writeable (by a non-root user), then someone
may be able to overwrite the log itself with bogus data.
<P>
<HR>
<H2>Server Side Includes</H2>
<P>Server side includes (SSI) can be configured so that users can execute
arbitrary programs on the server. That thought alone should send a shiver
down the spine of any sys-admin.<P>

One solution is to disable that part of SSI. To do that you use the
IncludesNOEXEC option to the <A HREF="/mod/core.html#options">Options</A>
directive.<P>

<HR>

<H2>Non Script Aliased CGI</H2>
<P>Allowing users to execute <STRONG>CGI</STRONG> scripts in any directory should only
be considered if;
<OL>
 <LI>You trust your users not to write scripts which will deliberately or
accidentally expose your system to an attack.
 <LI>You consider security at your site to be so feeble in other areas, as to
make one more potential hole irrelevant.
 <LI>You have no users, and nobody ever visits your server.
</OL><P>
<HR>

<H2>Script Alias'ed CGI</H2>
<P>Limiting <STRONG>CGI</STRONG> to special directories gives the admin control over
what goes into those directories. This is inevitably more secure than
non script aliased CGI, but <STRONG>only if users with write access to the
directories are trusted</STRONG> or the admin is willing to test each new CGI
script/program for potential security holes.<P>

Most sites choose this option over the non script aliased CGI approach.<P>

<HR>
<H2>CGI in general</H2>
<P>Always remember that you must trust the writers of the CGI script/programs
or your ability to spot potential security holes in CGI, whether they were
deliberate or accidental.<P>

All the CGI scripts will run as the same user, so they have potential to
conflict (accidentally or deliberately) with other scripts e.g.
User A hates User B, so he writes a script to trash User B's CGI
database.  One program which can be used to allow scripts to run
as different users is <A HREF="/suexec.html">suEXEC</A> which is
included with Apache as of 1.2 and is called from special hooks in
the Apache server code.  Another popular way of doing this is with
<A HREF="http://wwwcgi.umr.edu/~cgiwrap/">CGIWrap</A>.  <P>

<HR>


<H2>Stopping users overriding system wide settings...</H2>
<P>To run a really tight ship, you'll want to stop users from setting
up <CODE>.htaccess</CODE> files which can override security features
you've configured. Here's one way to do it...<P>

In the server configuration file, put
<BLOCKQUOTE><CODE>
&lt;Directory /&gt; <BR>
AllowOverride None <BR>
Options None <BR>
allow from all <BR>
&lt;/Directory&gt; <BR>
</CODE></BLOCKQUOTE>

Then setup for specific directories<P>

This stops all overrides, Includes and accesses in all directories apart
from those named.<P>
<HR>
<H2>
 Protect server files by default
</H2>
<P>
One aspect of Apache which is occasionally misunderstood is the feature
of default access.  That is, unless you take steps to change it, if the
server can find its way to a file through normal URL mapping rules, it
can serve it to clients.
</P>
<P>
For instance, consider the following example:
</P>
<OL>
 <LI><SAMP># cd /; ln -s / public_html</SAMP>
 </LI>
 <LI>Accessing <SAMP>http://localhost/~root/</SAMP>
 </LI>
</OL>
<P>
This would allow clients to walk through the entire filesystem.  To work
around this, add the following block to your server's configuration:
</P>
<PRE>
 &lt;Directory /&gt;
     Order deny,allow
     Deny from all
 &lt;/Directory&gt;
</PRE>
<P>
This will forbid default access to filesystem locations.  Add
appropriate
<A
 HREF="/mod/core.html#directory"
><SAMP>&lt;Directory&gt;</SAMP></A>
blocks to allow access only
in those areas you wish.  For example,
</P>
<PRE>
 &lt;Directory /usr/users/*/public_html&gt;
     Order deny,allow
     Allow from all
 &lt;/Directory&gt;
 &lt;Directory /usr/local/httpd&gt;
     Order deny,allow
     Allow from all
 &lt;/Directory&gt;
</PRE>
<P>
Pay particular attention to the interactions of
<A
 HREF="/mod/core.html#location"
><SAMP>&lt;Location&gt;</SAMP></A>
and
<A
 HREF="/mod/core.html#directory"
><SAMP>&lt;Directory&gt;</SAMP></A>
directives; for instance, even if <SAMP>&lt;Directory /&gt;</SAMP>
denies access, a <SAMP>&lt;Location /&gt;</SAMP> directive might
overturn it.
</P>
<P>
Also be wary of playing games with the
<A
 HREF="/mod/mod_userdir.html#userdir"
>UserDir</A>
directive; setting it to something like <SAMP>&quot;./&quot;</SAMP>
would have the same effect, for root, as the first example above.
If you are using Apache 1.3 or above, we strongly recommend that you
include the following line in your server configuration files:
</P>
<DL>
 <DD><SAMP>UserDir&nbsp;disabled&nbsp;root</SAMP>
 </DD>
</DL>

<HR>
<P>Please send any other useful security tips to The Apache Group
by filling out a
<A HREF="http://www.apache.org/bugdb.cgi">problem report</A>, or by
sending mail to
<A HREF="mailto:apache-bugs@mail.apache.org">apache-bugs@mail.apache.org</A>
<P>
<HR>

<!--#include virtual="footer.html" -->
</BODY>
</HTML>