1
<?xml version="1.0" encoding="ISO-8859-1"?>
2
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
4
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
5
This file is generated from xml source: DO NOT EDIT
6
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
8
<title>Security Tips - Apache HTTP Server</title>
9
<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
10
<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
11
<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
12
<link href="../images/favicon.ico" rel="shortcut icon" /></head>
13
<body id="manual-page"><div id="page-header">
14
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
15
<p class="apache">Apache HTTP Server Version 2.2</p>
16
<img alt="" src="../images/feather.gif" /></div>
17
<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
19
<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.2</a> > <a href="./">Miscellaneous Documentation</a></div><div id="page-content"><div id="preamble"><h1>Security Tips</h1>
21
<p><span>Available Languages: </span><a href="../en/misc/security_tips.html" title="English"> en </a> |
22
<a href="../ko/misc/security_tips.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
25
<p>Some hints and tips on security issues in setting up a web server.
26
Some of the suggestions will be general, others specific to Apache.</p>
28
<div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#uptodate">Keep up to Date</a></li>
29
<li><img alt="" src="../images/down.gif" /> <a href="#serverroot">Permissions on ServerRoot Directories</a></li>
30
<li><img alt="" src="../images/down.gif" /> <a href="#ssi">Server Side Includes</a></li>
31
<li><img alt="" src="../images/down.gif" /> <a href="#cgi">CGI in General</a></li>
32
<li><img alt="" src="../images/down.gif" /> <a href="#nsaliasedcgi">Non Script Aliased CGI</a></li>
33
<li><img alt="" src="../images/down.gif" /> <a href="#saliasedcgi">Script Aliased CGI</a></li>
34
<li><img alt="" src="../images/down.gif" /> <a href="#dynamic">Other sources of dynamic content</a></li>
35
<li><img alt="" src="../images/down.gif" /> <a href="#systemsettings">Protecting System Settings</a></li>
36
<li><img alt="" src="../images/down.gif" /> <a href="#protectserverfiles">Protect Server Files by Default</a></li>
37
<li><img alt="" src="../images/down.gif" /> <a href="#watchyourlogs">Watching Your Logs</a></li>
39
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
41
<h2><a name="uptodate" id="uptodate">Keep up to Date</a></h2>
43
<p>The Apache HTTP Server has a good record for security and a
44
developer community highly concerned about security issues. But
45
it is inevitable that some problems -- small or large -- will be
46
discovered in software after it is released. For this reason, it
47
is crucial to keep aware of updates to the software. If you have
48
obtained your version of the HTTP Server directly from Apache, we
49
highly recommend you subscribe to the <a href="http://httpd.apache.org/lists.html#http-announce">Apache
50
HTTP Server Announcements List</a> where you can keep informed of
51
new releases and security updates. Similar services are available
52
from most third-party distributors of Apache software.</p>
54
<p>Of course, most times that a web server is compromised, it is
55
not because of problems in the HTTP Server code. Rather, it comes
56
from problems in add-on code, CGI scripts, or the underlying
57
Operating System. You must therefore stay aware of problems and
58
updates with all the software on your system.</p>
60
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
62
<h2><a name="serverroot" id="serverroot">Permissions on ServerRoot Directories</a></h2>
66
<p>In typical operation, Apache is started by the root user, and it
67
switches to the user defined by the <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> directive to serve hits. As is the
68
case with any command that root executes, you must take care that it is
69
protected from modification by non-root users. Not only must the files
70
themselves be writeable only by root, but so must the directories, and
71
parents of all directories. For example, if you choose to place
72
ServerRoot in /usr/local/apache then it is suggested that you create
73
that directory as root, with commands like these:</p>
75
<div class="example"><p><code>
76
mkdir /usr/local/apache <br />
77
cd /usr/local/apache <br />
78
mkdir bin conf logs <br />
79
chown 0 . bin conf logs <br />
80
chgrp 0 . bin conf logs <br />
81
chmod 755 . bin conf logs
84
<p>It is assumed that /, /usr, and /usr/local are only modifiable by
85
root. When you install the <code class="program"><a href="../programs/httpd.html">httpd</a></code> executable, you
86
should ensure that it is similarly protected:</p>
88
<div class="example"><p><code>
89
cp httpd /usr/local/apache/bin <br />
90
chown 0 /usr/local/apache/bin/httpd <br />
91
chgrp 0 /usr/local/apache/bin/httpd <br />
92
chmod 511 /usr/local/apache/bin/httpd
95
<p>You can create an htdocs subdirectory which is modifiable by other
96
users -- since root never executes any files out of there, and shouldn't
97
be creating files in there.</p>
99
<p>If you allow non-root users to modify any files that root either
100
executes or writes on then you open your system to root compromises.
101
For example, someone could replace the <code class="program"><a href="../programs/httpd.html">httpd</a></code> binary so
102
that the next time you start it, it will execute some arbitrary code. If
103
the logs directory is writeable (by a non-root user), someone could replace
104
a log file with a symlink to some other system file, and then root
105
might overwrite that file with arbitrary data. If the log files
106
themselves are writeable (by a non-root user), then someone may be
107
able to overwrite the log itself with bogus data.</p>
109
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
110
<div class="section">
111
<h2><a name="ssi" id="ssi">Server Side Includes</a></h2>
115
<p>Server Side Includes (SSI) present a server administrator with
116
several potential security risks.</p>
118
<p>The first risk is the increased load on the server. All
119
SSI-enabled files have to be parsed by Apache, whether or not
120
there are any SSI directives included within the files. While this
121
load increase is minor, in a shared server environment it can become
124
<p>SSI files also pose the same risks that are associated with CGI
125
scripts in general. Using the "exec cmd" element, SSI-enabled files
126
can execute any CGI script or program under the permissions of the
127
user and group Apache runs as, as configured in httpd.conf.</p>
129
<p>There are ways to enhance the security of SSI files while still
130
taking advantage of the benefits they provide.</p>
132
<p>To isolate the damage a wayward SSI file can cause, a server
133
administrator can enable <a href="../suexec.html">suexec</a> as
134
described in the <a href="#cgi">CGI in General</a> section</p>
136
<p>Enabling SSI for files with .html or .htm extensions can be
137
dangerous. This is especially true in a shared, or high traffic,
138
server environment. SSI-enabled files should have a separate extension,
139
such as the conventional .shtml. This helps keep server load at a
140
minimum and allows for easier management of risk.</p>
142
<p>Another solution is to disable the ability to run scripts and
143
programs from SSI pages. To do this replace <code>Includes</code>
144
with <code>IncludesNOEXEC</code> in the <code class="directive"><a href="../mod/core.html#options">Options</a></code> directive. Note that users may
145
still use <--#include virtual="..." --> to execute CGI scripts if
146
these scripts are in directories desginated by a <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code> directive.</p>
148
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
149
<div class="section">
150
<h2><a name="cgi" id="cgi">CGI in General</a></h2>
154
<p>First of all, you always have to remember that you must trust the
155
writers of the CGI scripts/programs or your ability to spot potential
156
security holes in CGI, whether they were deliberate or accidental. CGI
157
scripts can run essentially arbitrary commands on your system with the
158
permissions of the web server user and can therefore be extremely
159
dangerous if they are not carefully checked.</p>
161
<p>All the CGI scripts will run as the same user, so they have potential
162
to conflict (accidentally or deliberately) with other scripts e.g. User
163
A hates User B, so he writes a script to trash User B's CGI database. One
164
program which can be used to allow scripts to run as different users is
165
<a href="../suexec.html">suEXEC</a> which is included with Apache as of
166
1.2 and is called from special hooks in the Apache server code. Another
167
popular way of doing this is with
168
<a href="http://cgiwrap.unixtools.org/">CGIWrap</a>.</p>
170
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
171
<div class="section">
172
<h2><a name="nsaliasedcgi" id="nsaliasedcgi">Non Script Aliased CGI</a></h2>
176
<p>Allowing users to execute CGI scripts in any directory should only be
180
<li>You trust your users not to write scripts which will deliberately
181
or accidentally expose your system to an attack.</li>
182
<li>You consider security at your site to be so feeble in other areas,
183
as to make one more potential hole irrelevant.</li>
184
<li>You have no users, and nobody ever visits your server.</li>
187
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
188
<div class="section">
189
<h2><a name="saliasedcgi" id="saliasedcgi">Script Aliased CGI</a></h2>
193
<p>Limiting CGI to special directories gives the admin control over what
194
goes into those directories. This is inevitably more secure than non
195
script aliased CGI, but only if users with write access to the
196
directories are trusted or the admin is willing to test each
197
new CGI script/program for potential security holes.</p>
199
<p>Most sites choose this option over the non script aliased CGI
202
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
203
<div class="section">
204
<h2><a name="dynamic" id="dynamic">Other sources of dynamic content</a></h2>
209
Embedded scripting options which run as part of the server itself,
210
such as mod_php, mod_perl, mod_tcl, and mod_python, run under the
211
identity of the server itself (see the <code class="directive"><a href="../mod/mpm_common.html#user">User</a></code> directive), and therefore
212
scripts executed by these engines potentially can access anything the
213
server user can. Some scripting engines may provide restrictions, but
214
it is better to be safe and assume not.</p>
216
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
217
<div class="section">
218
<h2><a name="systemsettings" id="systemsettings">Protecting System Settings</a></h2>
222
<p>To run a really tight ship, you'll want to stop users from setting
223
up <code>.htaccess</code> files which can override security features
224
you've configured. Here's one way to do it.</p>
226
<p>In the server configuration file, put</p>
228
<div class="example"><p><code>
229
<Directory /> <br />
230
AllowOverride None <br />
234
<p>This prevents the use of <code>.htaccess</code> files in all
235
directories apart from those specifically enabled.</p>
237
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
238
<div class="section">
239
<h2><a name="protectserverfiles" id="protectserverfiles">Protect Server Files by Default</a></h2>
243
<p>One aspect of Apache which is occasionally misunderstood is the
244
feature of default access. That is, unless you take steps to change it,
245
if the server can find its way to a file through normal URL mapping
246
rules, it can serve it to clients.</p>
248
<p>For instance, consider the following example:</p>
250
<div class="example"><p><code>
251
# cd /; ln -s / public_html <br />
252
Accessing <code>http://localhost/~root/</code>
255
<p>This would allow clients to walk through the entire filesystem. To
256
work around this, add the following block to your server's
259
<div class="example"><p><code>
260
<Directory /> <br />
261
Order Deny,Allow <br />
266
<p>This will forbid default access to filesystem locations. Add
267
appropriate <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> blocks to
268
allow access only in those areas you wish. For example,</p>
270
<div class="example"><p><code>
271
<Directory /usr/users/*/public_html> <br />
272
Order Deny,Allow <br />
273
Allow from all <br />
274
</Directory> <br />
275
<Directory /usr/local/httpd> <br />
276
Order Deny,Allow <br />
277
Allow from all <br />
281
<p>Pay particular attention to the interactions of <code class="directive"><a href="../mod/core.html#location">Location</a></code> and <code class="directive"><a href="../mod/core.html#directory">Directory</a></code> directives; for instance, even
282
if <code><Directory /></code> denies access, a <code>
283
<Location /></code> directive might overturn it</p>
285
<p>Also be wary of playing games with the <code class="directive"><a href="../mod/mod_userdir.html#userdir">UserDir</a></code> directive; setting it to
286
something like "./" would have the same effect, for root, as the first
287
example above. If you are using Apache 1.3 or above, we strongly
288
recommend that you include the following line in your server
289
configuration files:</p>
291
<div class="example"><p><code>
292
UserDir disabled root
295
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
296
<div class="section">
297
<h2><a name="watchyourlogs" id="watchyourlogs">Watching Your Logs</a></h2>
301
<p>To keep up-to-date with what is actually going on against your server
302
you have to check the <a href="../logs.html">Log Files</a>. Even though
303
the log files only reports what has already happened, they will give you
304
some understanding of what attacks is thrown against the server and
305
allows you to check if the necessary level of security is present.</p>
307
<p>A couple of examples:</p>
309
<div class="example"><p><code>
310
grep -c "/jsp/source.jsp?/jsp/ /jsp/source.jsp??" access_log <br />
311
grep "client denied" error_log | tail -n 10
314
<p>The first example will list the number of attacks trying to exploit the
315
<a href="http://online.securityfocus.com/bid/4876/info/">Apache Tomcat
316
Source.JSP Malformed Request Information Disclosure Vulnerability</a>,
317
the second example will list the ten last denied clients, for example:</p>
319
<div class="example"><p><code>
320
[Thu Jul 11 17:18:39 2002] [error] [client foo.bar.com] client denied
321
by server configuration: /usr/local/apache/htdocs/.htpasswd
324
<p>As you can see, the log files only report what already has happened, so
325
if the client had been able to access the <code>.htpasswd</code> file you
326
would have seen something similar to:</p>
328
<div class="example"><p><code>
329
foo.bar.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1"
332
<p>in your <a href="../logs.html#accesslog">Access Log</a>. This means
333
you probably commented out the following in your server configuration
336
<div class="example"><p><code>
337
<Files ~ "^\.ht"> <br />
338
Order allow,deny <br />
344
<div class="bottomlang">
345
<p><span>Available Languages: </span><a href="../en/misc/security_tips.html" title="English"> en </a> |
346
<a href="../ko/misc/security_tips.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
347
</div><div id="footer">
348
<p class="apache">Copyright 2006 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
349
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
b'\\ No newline at end of file'
added
removed
docs/manual/misc/security_tips.html.en
