Thomas Swan reported a service disclosure flaw in xinetd. xinetd allows for services to be configured with the TCPMUX or TCPMUXPLUS service types, which makes those services available on port 1, as per RFC 1078 [1], if the tcpmux-server service is enabled. When the tcpmux-server service is enabled, xinetd would expose _all_ enabled services via the tcpmux port, instead of just the configured service(s). This could allow a remote attacker to bypass firewall restrictions and access services via the tcpmux port. In order for enabled services handled by xinetd to be exposed via the tcpmux port, the tcpmux-server service must be enabled (by default it is disabled). The tcpmux-server should only ever expose services with the 'type = TCPMUX' or 'type = TCPMUXPLUS' configuration options set. To reproduce: - enable tcpmux-server - restart xinetd - telnet localhost 1 - type service name of a running service (e.g. cvspserver) The service will be launched and respond on the port: # telnet localhost 1 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. cvspserver cvs [pserver aborted]: bad auth protocol start: There is no upstream fix for this as of yet. [1] http://tools.ietf.org/html/rfc1078
Acknowledgements: Red Hat would like to thank Thomas Swan of FedEx for reporting this issue.
Created attachment 583311 [details] Patch for CVE-2012-0862 as provided by Thomas Swan of FedEx. Reviewed by a former xinetd upstream maintainer and the current Red Hat xinetd maintainer.
Now public via: http://www.openwall.com/lists/oss-security/2012/05/09/5
Created xinetd tracking bugs for this issue Affects: fedora-all [bug 820318]
Already fixed in f17 and f18 by http://lists.fedoraproject.org/pipermail/scm-commits/2012-May/781809.html
This is corrected in upstream 2.3.15.
xinetd-2.3.14-47.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
xinetd-2.3.14-37.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
This issue has been addressed in following products: Red Hat Enterprise Linux 6 Via RHSA-2013:0499 https://rhn.redhat.com/errata/RHSA-2013-0499.html
GSS are requesting further information regards the ETA for this update being provided to RHEL 5, can you contact John Jong Bae Ko <jko> and provide additional details. I am setting need info but please contact John directly as he does not have visibility of this BZ. John
Created attachment 799731 [details] updated, simpler patch I believe that child_process not exec_server should be called. This does not affect the existing behaviour of other exec_server calls.
disregard last update and patch.
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Via RHSA-2013:1302 https://rhn.redhat.com/errata/RHSA-2013-1302.html
Statement: Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This flaw has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.