Bug 22687 - xinetd.conf: Please consider removing RECORD option
Summary: xinetd.conf: Please consider removing RECORD option
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xinetd
Version: 7.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
Keywords: Security
: 28049 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-12-21 19:51 UTC by Chris Evans
Modified: 2007-04-18 16:30 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2001-01-21 12:55:44 UTC

Attachments (Terms of Use)

Description Chris Evans 2000-12-21 19:51:40 UTC

Please see the summary line.

I think the RECORD option should be removed from the default config; it is
a security risk. As well as being a risk, it also brings very little
benefit to an installation, as it only kicks in when the target service
cannot be launched!

The reasons for this being a security risk are:
- Lots of parsing/logging of malicious remote supplied data (usernames,
commands, etc).
- In the case of "rexec", a 1-byte overflow (xinetd author informed)
- Dangerous "connect back" facility, which mixed in with a bit of spoofing,
can allow a malicious remote to force a host to make connections to
privileged ports from privileged ports.

Comment 1 Trond Eivind Glomsrxd 2000-12-26 23:17:59 UTC
Done, in xinetd-

Comment 2 Henri Schlereth 2001-01-21 12:50:07 UTC
However, removing the RECORD option generates the following error message:

Jan 21 05:29:38 test1 xinetd: xinetd shutdown succeeded
Jan 21 05:29:38 test1 xinetd[6231]: Bad log-on_failure flag: PID [line=11]

This is in beta2. I have no objections to removing the RECORD option but in xinetd-
the settings are:

log_on_success      = HOST PID
log_on_failure          = HOST PID

and that craps out with the error message above.

Comment 3 Henri Schlereth 2001-01-21 12:55:40 UTC
Sorry I guess I need to be more exact. By crapping out I mean it generates the noted error message and continues.

Comment 4 Trond Eivind Glomsrxd 2001-01-30 18:50:08 UTC
Fixed in  xinetd-

Comment 5 Trond Eivind Glomsrxd 2001-02-19 16:11:21 UTC
*** Bug 28049 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.