summaryrefslogtreecommitdiffstats
path: root/docs/html/security.html
blob: 8d1b047d06b01b627a6966ede270b59e4f731682 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
<HTML
><HEAD
><TITLE
>Bugzilla Security</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Groups and Group Security"
HREF="groups.html"><LINK
REL="NEXT"
TITLE="Template Customization"
HREF="cust-templates.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="groups.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="cust-templates.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="security"
></A
>5.6. Bugzilla Security</H1
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Poorly-configured MySQL and Bugzilla installations have
      given attackers full access to systems in the past. Please take these
      guidelines seriously, even for Bugzilla machines hidden away behind
      your firewall. 80% of all computer trespassers are insiders, not
      anonymous crackers.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>These instructions must, of necessity, be somewhat vague since
      Bugzilla runs on so many different platforms. If you have refinements
      of these directions for specific platforms, please submit them to 
      <A
HREF="mailto://mozilla-webtools@mozilla.org"
TARGET="_top"
>&#13;      mozilla-webtools@mozilla.org</A
>
      </P
></TD
></TR
></TABLE
></DIV
><P
>To secure your installation:
     
    <P
></P
><OL
TYPE="1"
><LI
><P
>&#13;        <EM
>There is no substitute for understanding the tools on your
        system!</EM
>

        Read 
        <A
HREF="http://www.mysql.com/doc/P/r/Privilege_system.html"
TARGET="_top"
>&#13;        The MySQL Privilege System</A
>
        until you can recite it from memory!</P
></LI
><LI
><P
>Lock down <TT
CLASS="filename"
>/etc/inetd.conf</TT
>. Heck, disable
        inet entirely on this box. It should only listen to port 25 for
        Sendmail and port 80 for Apache.</P
></LI
><LI
><P
>Do not run Apache as 
        <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>

        . This will require very lax permissions in your Bugzilla
        directories. Run it, instead, as a user with a name, set via your
        httpd.conf file. 
        <DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>

          is a real user on UNIX systems. Having a process run as user id 
          <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>

          is absolutely no protection against system crackers versus using
          any other user account. As a general security measure, I recommend
          you create unique user ID's for each daemon running on your system
          and, if possible, use "chroot" to jail that process away from the
          rest of your system.</P
></TD
></TR
></TABLE
></DIV
>
        </P
></LI
><LI
><P
>Ensure you have adequate access controls for the
        <TT
CLASS="filename"
>$BUGZILLA_HOME/data/</TT
> directory, as well as the
        <TT
CLASS="filename"
>$BUGZILLA_HOME/localconfig</TT
> file.
        The localconfig file stores your "bugs" database account password. 
        In addition, some
        files under <TT
CLASS="filename"
>$BUGZILLA_HOME/data/</TT
> store sensitive
        information.
        </P
><P
>Also, beware that some text editors create backup files in the
        current working directory so you need to also secure files like
        <TT
CLASS="filename"
>localconfig~</TT
>.
        </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Simply blocking <TT
CLASS="computeroutput"
>.*localconfig.*</TT
>
          won't work because the QuickSearch feature requires the web browser
          to be able to retrieve <TT
CLASS="filename"
>localconfig.js</TT
> and
          others may be introduced in the future (see 
          <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
TARGET="_top"
>bug
          186383</A
> for more information.
          </P
></TD
></TR
></TABLE
></DIV
><P
>Bugzilla provides default <TT
CLASS="filename"
>.htaccess</TT
> files
        to protect the most common Apache installations. However, you should
        verify these are adequate according to the site-wide security policy
        of your web server, and ensure that the <TT
CLASS="filename"
>.htaccess</TT
>
        files are allowed to <SPAN
CLASS="QUOTE"
>"override"</SPAN
> default permissions set
        in your Apache configuration files. Covering Apache security is beyond
        the scope of this Guide; please consult the Apache documentation for
        details.
        </P
><P
>If you are using a web server that does not support the
        <TT
CLASS="filename"
>.htaccess</TT
> control method, 
        <EM
>you are at risk!</EM
>

        After installing, check to see if you can view the file
        <TT
CLASS="filename"
>localconfig</TT
> in your web browser (e.g.: 
        <A
HREF="http://bugzilla.mozilla.org/localconfig"
TARGET="_top"
>&#13;        http://bugzilla.mozilla.org/localconfig</A
>

        ). If you can read the contents of this file, your web server has
        not secured your bugzilla directory properly and you must fix this
        problem before deploying Bugzilla. If, however, it gives you a
        "Forbidden" error, then it probably respects the .htaccess
        conventions and you are good to go.</P
></LI
><LI
><P
>When you run checksetup.pl, the script will attempt to modify
        various permissions on files which Bugzilla uses. If you do not have
        a webservergroup set in the <TT
CLASS="filename"
>localconfig</TT
> file,
        then Bugzilla will have to make certain files world readable and/or
        writable. 
        <EM
>THIS IS INSECURE!</EM
>

        . This means that anyone who can get access to your system can do
        whatever they want to your Bugzilla installation.</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>This also means that if your webserver runs all cgi scripts
          as the same user/group, anyone on the system who can run cgi
          scripts will be able to take control of your Bugzilla
          installation.</P
></TD
></TR
></TABLE
></DIV
><P
>On Apache, you can use <TT
CLASS="filename"
>.htaccess</TT
> files to
        protect access to these directories, as outlined in Bugs 
        <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
TARGET="_top"
>&#13;        57161</A
> and
        <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
TARGET="_top"
>&#13;        186383</A
>

        for the <TT
CLASS="filename"
>localconfig</TT
> file, and 
        <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
TARGET="_top"
>Bug
        65572</A
>

        for adequate protection in your <TT
CLASS="filename"
>data/</TT
> directory.
        Also, don't forget about the <TT
CLASS="filename"
>template/</TT
> and
        <TT
CLASS="filename"
>Bugzilla/</TT
> directories and to allow access to the
        <TT
CLASS="filename"
>data/webdot</TT
> directory for the
        <TT
CLASS="computeroutput"
>192.20.225.10</TT
> IP address if you are
        using webdot from research.att.com.  The easiest way to
        accomplish this is to set <TT
CLASS="function"
>$create_htaccess</TT
> to 1
        in <TT
CLASS="filename"
>localconfig</TT
>.  However, the information below
        is provided for those that want to know exactly what is created.
        </P
><P
>FIX ME BEFORE RELEASE!!!!!
        Note the instructions which follow are Apache-specific. If you
        use IIS, Netscape, or other non-Apache web servers, please consult
        your system documentation for how to secure these files from being
        transmitted to curious users.</P
></LI
></OL
>
    </P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="groups.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="cust-templates.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Groups and Group Security</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Template Customization</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>