X Display Manager (xdm(1)) May Crash Due to Invalid XDMCP Request |
|
| Category : | Security |
| Release Phase : | Resolved |
| Product : | Solaris 9 Operating System Solaris 7 Operating System Solaris 8 Operating System
|
| Bug Id : | 5023755
|
| Date of Workaround Release : | 09-AUG-2004
|
| Date of Resolved Release : | 01-DEC-2005
|
Impact
A remote unprivileged user may be able to crash the X Display Manager (xdm(1)) when using an invalid X Display Manager Control Protocol (XDMCP) request, thus causing a Denial of Service (DoS).
Contributing Factors
This issue can occur in the following releases:
SPARC Platform
x86 Platform
Symptoms
If the described issue occurs, the X Display Manager will exit without warning.
Workaround
To reduce the possibility of the described issue from occurring, network administrators should block UDP(7P) packets to port 177 across any firewall where XDMCP remote session service is not required.
If XDMCP remote session access to a machine is not required at all, but graphical login access via xdm(1M) for console devices is required, xdm(1M) can be configured to not listen for XDMCP connections by editing the "/usr/openwin/lib/X11/xdm/xdm-config" file and adding the following line:
DisplayManager.requestPort: 0
Note: Controlling access via the access control list in the "Xaccess" file is not effective at preventing this issue.
Resolution
This issue is addressed in the following releases:
SPARC Platform
x86 Platform
Modification HistoryDate: 13-OCT-2004
-
Updated Contributing Factors and Resolution sections
Date: 07-OCT-2004
-
Updated Contributing Factors and Resolution sections
Date: 30-NOV-2005
- Updated Contributing Factors and Resolution sections
Date: 01-DEC-2005
- State: Resolved
- Updated Contributing Factors and Resolution sections
AttachmentsThis solution has no attachment