CVE-2011-0465: Input Validation

Published Feb 24, 2011
·
Updated

It was found that xrdb, the X server resource database utility, did not properly sanitize system host names, containing shell escape characters, during launch of user graphical session (when the display manager retrieved the system host name from resource database via xrdb). When the display manager was configured to listen for X Display Manager Control Protocol (XDMCP) messages, a remote attacker could use this flaw to remotely execute arbitrary code with the privileges, of the user running the display manager (usually privileged system user, root). On systems, where the XDMCP messages were disabled and the system was configured to retrieve its host name from remote DHCP server, a rogue DHCP server could use this flaw to possibly execute arbitrary code with the privileges of the user running the display manager (usually root) via a specially-crafted host name assigned to the victim host in question.

Note: ===== The display managers, shipped with Red Hat Enterprise Linux 4, 5, and 6 do not listen for remote XDMCP messages in the default configuration, which mitigates this security flaw to be exploitable only by rogue remote DHCP servers.

The display managers, shipped with Fedora release of 13 and 14 do not listen for remote XDMCP messages in the default configuration, which mitigates this security flaw to be exploitable only by rogue remote DHCP servers.

Other sources

xrdb.c in xrdb before 1.0.9 in X.Org X11R7.6 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in a hostname obtained from a (1) DHCP or (2) XDMCP message.

MITRE

Affected Software

31 affected components
X X11=r7.0
X X11=r3
X X11=r6.1
X X11=r6.8.0
Matthias Hopf Xrdb=1.0.2
X X11=r6.7
X X11=r7.2
X X11=r2
X X11<=r7.6
X X11=r7.1
X X11=r7.5
X X11=r5
X X11=r6.9.0
X X11=r7.3
X X11=r1
X X11=r6.8.1
X X11=r6.4
Matthias Hopf Xrdb=1.0.4
Matthias Hopf Xrdb<=1.0.8
Matthias Hopf Xrdb=1.0.7
Matthias Hopf Xrdb=1.0.5
X X11=r4
X X11=r7.4
Matthias Hopf Xrdb=1.0.3
X X11=r6.6
X X11=r6.8.2
X X11=r6.5.1
X X11=r6.3
X X11=r6.7.0
X X11=r6
Matthias Hopf Xrdb=1.0.6

Event History

Feb 24, 2011
Data Sourced
04:03 PM
DescriptionSeverityAffected Software
Apr 8, 2011
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2011-0465?

The severity of CVE-2011-0465 is typically rated as medium, indicating that it can potentially lead to security risks if not addressed.

2

How do I fix CVE-2011-0465?

To fix CVE-2011-0465, users should update to the latest patched version of the affected software, particularly the X.Org Server or xrdb.

3

Which software versions are affected by CVE-2011-0465?

CVE-2011-0465 affects multiple versions of X.Org Server, specifically from r1 to r7.6, as well as specific versions of xrdb including 1.0.2, 1.0.4, 1.0.7, 1.0.6, etc.

4

What type of vulnerability is CVE-2011-0465?

CVE-2011-0465 is a security vulnerability that involves improper sanitization of system hostnames, which could allow for shell escape attacks.

5

Who is impacted by CVE-2011-0465?

Users of the affected versions of X.Org Server and xrdb, particularly those running graphical sessions on vulnerable systems, are impacted by CVE-2011-0465.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203