This file is indexed.

/usr/lib/tiger/doc/inetd.html is in tiger 1:3.2.3-10.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  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
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
<HR><PRE>








</PRE><HR>
<CENTER><H2> Documents for inetd</H2></CENTER>
<A NAME="inet001e"><P><B>Code [inet001e]</B><P>
One or the other of the two listed files are unavailable. These
files are required for the checks to proceed. This either indicates
an incorrect configuration, or that a port to this machine has not
been completed.
<PRE>










</PRE><HR>
<A NAME="inet002f"><P><B>Code [inet002f]</B><P>
The indicated service is assigned to the wrong port. This indicates
either a misconfiguration in the services database, or a possible
sign of an intrusion. This should be checked and corrected. If it
is not apparent why it is like this, the system should be checked
for other signs of intrusion.
<PRE>










</PRE><HR>
<A NAME="inet003w"><P><B>Code [inet003w]</B><P>
The indicated port number is assigned to another service. This
indicates either a misconfiguration in the services database, or a
possible sign of an intrusion. This should be checked and corrected.
If it is not apparent why it is like this, the system should be
checked for other signs of intrusion.
<PRE>










</PRE><HR>
<A NAME="inet004i"><P><B>Code [inet004i]</B><P>
The indicated service has been added to the services database
as distributed. These are normal output, but you should be
familiar with what is there, and note any changes.
<PRE>










</PRE><HR>
<A NAME="inet005w"><P><B>Code [inet005w]</B><P>
'inetd' is using the indicated binary for the listed service instead
of what is normally expected there. Unexpected differences should
be checked, and if anything unusual is found, the system should
be checked for other signs of intrusion.
<PRE>










</PRE><HR>
<A NAME="inet006f"><P><B>Code [inet006f]</B><P>
The 'rexd' (or 'exec') service is very insecure and should never be
enabled. Known rexd servers have little or no security in their design
or implementation. Intruders can exploit this service to execute
commands as any user.
<P>
It should be disabled immediately by editing the inetd.conf file
and removing the 'rexd' entry, and sending a HUP signal to the
'inetd' process.
<P>
For AIX systems, CERT Advisory CA-92:05 is applicable.
<P>
Notice that some intruders may turn on a service
that you previously thought you had turned off, or replace
the inetd program with a Trojan horse program.
<PRE>










</PRE><HR>
<A NAME="inet007w"><P><B>Code [inet007w]</B><P>
'inetd' is using the indicated executable for a port other than
what would normally be expected for this port. This may indicate
a backdoor into the system and should be checked. If anything
unusual is found, the system should be checked for other signs
of intrusion.
<PRE>










</PRE><HR>
<A NAME="inet008"><P><B>Code [inet008]</B><P>
The owner of the indicated executable is not 'root'. The owner
of the executable should be root in order to reduce the possibility
of it being altered or replaced.
<PRE>










</PRE><HR>
<A NAME="inet009"><P><B>Code [inet009]</B><P>
The indicated executable is group writable, world writable or both.
The executable should be owned by root and writable only by the
owner. This reduces the possibility of it being altered or replaced.
<PRE>










</PRE><HR>
<A NAME="inet010i"><P><B>Code [inet010i]</B><P>
The program listed in the `inetd' configuration file does not
exist or is not executable.
<PRE>










</PRE><HR>
<A NAME="inet011i"><P><B>Code [inet011i]</B><P>
The listed entry is a local addition to the `inetd.conf' file.
This should be checked to see if it is a valid addition. If it
is not, it should be removed.
<PRE>










</PRE><HR>
<A NAME="inet012w"><P><B>Code [inet012w]</B><P>
The 'systat' service is enabled, this system provides a considerable
number of information to remote anonymous users.
Consider disabling it by editing the inetd.conf file,
removing the 'systat' entry, and sending a HUP signal to the
'inetd' process.
<PRE>










</PRE><HR>
<A NAME="inet013w"><P><B>Code [inet013w]</B><P>
The 'netstat' service is enabled, this system provides a considerable
number of information to remote anonymous users.
Consider disabling it by editing the inetd.conf file,
removing the 'netstat' entry, and sending a HUP signal to the
'inetd' process.
<PRE>










</PRE><HR>
<A NAME="inet014i"><P><B>Code [inet014i]</B><P>
The listed entry was protected by tcp wrappers by the default installation
and is currently protected this way too. This is a good thing!
<PRE>










</PRE><HR>
<A NAME="inet015i"><P><B>Code [inet015i]</B><P>
The listed entry has been modified in order for it to be protected
by using tcp wrappers. This has been changed from default installation
(which did not provide it) but is probably a better setup.
<PRE>










</PRE><HR>
<A NAME="inet016f"><P><B>Code [inet016f]</B><P>
The listed entry was protected by tcp wrappers by the system but has,
for some unknown reason, changed to no longer be protected by them. Make
sure that the service is secured since, if not using tcp wrappers,
access control for it might be disabled.
<PRE>










</PRE><HR>
<A NAME="inet017w"><P><B>Code [inet017w]</B><P>
The inetd configuration file permissions is not 600. This is the recommended
setting by CERT's 'UNIX Security Checklist v2.0'. You should check that the
file permissions on that file are correct.
If an attacker can access the file due to lack of file permissions it might
enable him to add new lines to the file which would, when inetd is restarted,
allow him to introduce backdoors in the system.
<PRE>










</PRE><HR>
<A NAME="inet018w"><P><B>Code [inet018w]</B><P>
The inetd configuration file can be written by any user of a given group since
the file permissions ensure this. If the group is not an administrative group
you should consider changing its permissions to 600.
If the group includes untrusted users, one of them could
add new lines to the file which would, when inetd is restarted,
allow him to introduce backdoors in the system.
<PRE>










</PRE><HR>
<A NAME="inet019a"><P><B>Code [inet019a]</B><P>
The inetd configuration file can be written by any user of the system.
This makes it possible for any user to add new lines to the file which
would, when inetd is restarted, allow him to introduce backdoors in the
system.
You should review your inetd configuration file to determine if there are
suspicious services enabled since this might indicate that an intrusion
has taken placed on the system. Also change the file permissions to restrict
this misuse.
<PRE>










</PRE><HR>
<A NAME="inet020f"><P><B>Code [inet020f]</B><P>
The inetd configuration file is not owned by root which is usually the owner
of this file in most systems. This might indicate that the system has
been affected by an intrusion and permissions of both the file and
the directory it is stored in should be reviewed. Also review the content
of this file in order to check if there are suspicious services enabled
since this might indicate that an intrusion has taken place.
<PRE>










</PRE><HR>
<A NAME="inet021f"><P><B>Code [inet021f]</B><P>
TCP wrappers do not seem to be installed in the system since the 'tcpd' program
is not found in the system. Tcp wrappers allows you to monitor and filter
incoming requests for common network services (through the use of the
hosts.allow and hosts.deny files) and can be used to 'wrap' services either
running through the inetd or in rc.d files.
It is available via anonymous FTP from: ftp://ftp.porcupine.org/pub/security/
<PRE>










</PRE><HR>
<A NAME="inet022w"><P><B>Code [inet022w]</B><P>
The tftpd service is enabled, disable tftp if not needed by
commenting it out from the file /etc/inetd.conf and restarting the
inetd process.
<P>
If the tftpd service is required, create a separate partition to
store the files to be served by tftp and limit the tftp daemon
to the directory where this partition is mounted. Also make sure
that the files in the tftpd area are not writable.
<P>
If it is not required, disable it by editing the inetd.conf file,
removing the 'tftp' entry, and sending a HUP signal to the 'inetd' process.
<PRE>










</PRE><HR>
<A NAME="inet023w"><P><B>Code [inet023w]</B><P>
The 'finger' service is enabled, this system provides a considerable
number of information to remote anonymous users. An
intruder can obtain quite a number of information about a remote host.
Also, if improperly configured it can be used to create a 'finger war'
DoS loop and can be used to do indirect finger requests
(that is contact remote servers when a remote user sends a request
for 'user@other_host@your_host')
<P>
You should make sure that you have an up-to-date version of fingerd.
Do not use a version of fingerd that is older than 16 October, 2000.
For more information consult the AusCERT ESB available at
ftp://ftp.auscert.org.au/pub/auscert/ESB/ESB-2000.286
<P>
Consider disabling it unless it is considered essentially
by editing the inetd.conf file, removing the 'finger' entry,
and sending a HUP signal to the 'inetd' process.
<P>
If you cannot remove finger consider reducing the content by replacing
it with a version which only offers restricted information.
<PRE>










</PRE><HR>
<A NAME="inet024w"><P><B>Code [inet024w]</B><P>
The 'rusers' service is enabled, this system provides a considerable
number of information to remote anonymous users.
<P>
Consider disabling it by editing the inetd.conf file,
removing the 'rusers' entry, and sending a HUP signal to the
'inetd' process.
<PRE>










</PRE><HR>
<A NAME="inet025w"><P><B>Code [inet025w]</B><P>
The 'echo' and 'chargen' UDP servers are potentially problematic
since they can be used to setup ping-pong DoS attacks targeted at
other systems by means of IP address spoofing.
<P>
Consider disabling it by editing the inetd.conf file,
removing the 'echo' and/or 'chargen' entries, and sending a HUP signal to the
'inetd' process.
<PRE>










</PRE><HR>
<A NAME="inet026w"><P><B>Code [inet026w]</B><P>
The linuxconf service can be utilized for remote administration.
<P>
Consider disabling it by editing the inetd.conf file,
removing the 'linuxconf' entry, and sending a HUP signal to the
'inetd' process.
<PRE>










</PRE><HR>
<A NAME="inet027w"><P><B>Code [inet027w]</B><P>
The 'identd or auth' service is enabled, this system provides a considerable
number of information to remote anonymous users.
<P>
Consider disabling it by editing the inetd.conf file, removing the 'auth' entry,
and sending a HUP signal to the 'inetd' process.
<PRE>










</PRE><HR>
<A NAME="inet098w"><P><B>Code [inet098w]</B><P>
Services that pass sensitive information (including passwords) should
be replaced with the family of programs that comprise secure shell (ssh)
which use strong encryption based on public-key cryptography.
<P>
You can use the freely-available OpenSSH implementation at
http://www.openssh.org
<PRE>










</PRE><HR>
<A NAME="inet099w"><P><B>Code [inet099w]</B><P>
The indicated service is not protected by tcp wrappers or xinetd access
control. The use of this facility is encouraged to limit access and to
improve logging.
The listed entry was protected by tcp wrappers by the default installation
and is currently protected this way too. This is a good thing!
<PRE>










</PRE><HR>
<A NAME="inet100w"><P><B>Code [inet100w]</B><P>
The inetd services does not have logging enabled. Adding logging to the
inetd services will help identify potential mis-use of system system resources.
<P>
To enable logging for the inetd service add the -l option in the inetd startup
scripts.
<P>
To enable logging for the xinetd services add the log_type, log_on_success
and/or log_on_failure to the /etc/xinetd.conf file.
<PRE>










</PRE><HR>
<A NAME="xnet001e"><P><B>Code [xnet001e]</B><P>
The script cannot find an xinetd configuration file in this system. This
might happen if Xinetd is not installed of if the XINETDCONF configuration
variable is not properly defined. The script will try to find this configuration
file in standard locations (/etc/xinetd.conf) but if it's not there
you will need to define it in the siterc configuration file.
<PRE>










</PRE><HR>
<A NAME="xnet002e"><P><B>Code [xnet002e]</B><P>
A directory which is being included by the XINETDCONF configuration file
is not really a directory. This prevents the script from analysing all
the active services and might be a configuration issue. Please check
Xinetd's configuration file.
<PRE>










</PRE><HR>
<A NAME="xnet003e"><P><B>Code [xnet003e]</B><P>
The script cannot read the xined configuration file in this system. This
should not usually happen since the script should be running with
root privileges. In order to analyse the configuration file you need
to run this script as a user who can read all the Xinetd configuration
files.
<PRE>










</PRE><HR>
<A NAME="xnet004i"><P><B>Code [xnet004i]</B><P>
The service is enabled in the Xinetd configuration file. You should verify
that services enabled in the server are legitimate and consider disabling
unused services in order to minimise exposure (and associated risk)
<PRE>










</PRE><HR>
<A NAME="xnet005i"><P><B>Code [xnet005i]</B><P>
The service is disabled in the Xinetd configuration file. This is usually
a good thing, since this limits exposure of the server and prevents
external attacks.