Bug 87863 - socket leak
socket leak
Product: Red Hat Linux
Classification: Retired
Component: xinetd (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Jay Fenlason
Brock Organ
: Security
Depends On:
  Show dependency treegraph
Reported: 2003-04-03 06:28 EST by Kasper Dupont
Modified: 2014-08-31 19:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-05-13 13:14:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kasper Dupont 2003-04-03 06:28:45 EST
Description of problem:
If fork() fails xinetd will leak sockets.
Leaked sockets will be inherited by child processes.

Version-Release number of selected component (if applicable):

How reproducible:
Easy to reproduce if compiled with the DEBUG_RETRY
option. Otherwise hard to reproduce.

Steps to Reproduce:
1. Compile xinetd with the DEBUG_RETRY option
2. Install xinetd and enable telnet
3. Open a lot of incomming telnet sessions
Actual results:
xinetd leaks filedescriptors and eventually stops
accepting connections. Child processes inherit the
leaked descriptors. (In case of telnet the child
will close the descriptor, so this is not immediately
exploitable by arbitrary users.)

Expected results:
On fork failing xinetd closes the connection
before going back to accept more connections.

Additional info:
Severity set to security, because xinetd services not
running as root could potentially take over the leaked
descriptors and snoop passwords. Priority set to low
because the default install is not believed to be
Comment 1 Mark J. Cox (Product Security) 2003-05-01 11:10:46 EDT
xinetd update (to 2.3.11) is in progress.
Comment 2 Mark J. Cox (Product Security) 2003-05-13 13:14:05 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


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