Accessible XDMCP Service Report

This report identifies hosts that have the X Display Manager service running and accessible on the Internet.

Our probe tests to see if the X Display Manager is accessible by sending a “Query” packet to the XDMCP port (177/UDP) and listening for the responses.

The responses received are typically either of the “Willing” type, which means that the X Display Manager is willing to provide service, or the “Unwilling” type, which means that the X Display Manager is not willing to provide services.

XDMCP leaks information about the host system and, in addition, it can be used in an amplification attack, providing an approximate 7x amplification. Please note that it does not matter if XDMCP responds with a “Willing” or an “Unwilling”; the service provides the same level of amplification.

Technical details of the XDMCP protocol can be found on the x.org website.

Fields

  • timestamp
    Time that the IP was probed in UTC+0
  • ip
    The IP address of the device in question
  • protocol
    Protocol that the XDMCP response came on (always UDP)
  • port
    Port that the XDMCP response came from (usually 177/UDP)
  • hostname
    Reverse DNS name of the device in question
  • tag
    Will always be xdmcp
  • asn
    ASN of where the device in question resides
  • geo
    Country where the device in question resides
  • region
    State / Province / Administrative region where the device in question resides
  • city
    City in which the device in question resides
  • naics
    North American Industry Classification System Code
  • sic
    Standard Industrial Classification System Code
  • opcode
    The response of what state of action the X Display Manager is in — this will usually be "Willing" (meaning that our anonymous connection was accepted) or "Unwilling" (meaning that our connection was refused)
  • reported_hostname
    This is the self-reported hostname that is returned in the XDMCP response
  • status
    Any additional information that the X Display Manager returned to us — it may be an error condition or information about the host running XDM
  • size
    Payload response size in bytes, excluding the UDP header

Sample

"timestamp","ip","protocol","port","hostname","tag","asn","geo","region","city","naics","sic","opcode","reported_hostname","status","size"
"2016-05-17 19:04:55","61.152.122.54","udp",177,,"xdmcp",4812,"CN","SHANGHAI","SHANGHAI",0,0,"Willing","netmanage","Linux 2.6.32-573.3.1.el6.i686",50
"2016-05-17 19:04:56","218.68.63.240","udp",177,,"xdmcp",4837,"CN","TIANJIN","TIANJIN",0,0,"Willing","bimsdev1","0 users  load: 0.0, 0.0, 0.0",48
"2016-05-17 19:04:56","211.137.249.158","udp",177,,"xdmcp",9808,"CN","HEILONGJIANG","HARBIN",0,0,"Willing","zyite01","4 users  load: 28.2, 28.6, 28.8",50
"2016-05-17 19:04:57","187.174.250.38","udp",177,"customer-187-174-250-38.uninet-ide.com.mx","xdmcp",8151,"MX","VERACRUZ","MEDELLIN DE BRAVO",0,0,"Willing","PAGOS","Linux 3.12.55-52.42-default",44
"2016-05-17 19:04:57","152.231.30.35","udp",177,,"xdmcp",3549,"CO","VALLE DEL CAUCA","SANTIAGO DE CALI",0,0,"Willing","linux-ws15","0 user, load: 0.00, 0.00, 0.00",52
"2016-05-17 19:04:57","218.39.178.182","udp",177,,"xdmcp",9318,"KR","SEOUL TEUGBYEOLSI","SEOUL",0,0,"Unwilling","mvodtown","!Display not authorized to connect",51
"2016-05-17 19:04:57","121.0.141.75","udp",177,,"xdmcp",38661,"KR","SEOUL TEUGBYEOLSI","GURO-DONG",0,0,"Willing","WASWP","0 users  load: 0.1, 0.2, 0.2",45
"2016-05-17 19:04:58","89.97.0.73","udp",177,"89-97-0-73.ip2.fastwebnet.it","xdmcp",12874,"IT","NAPOLI","CASORIA",0,0,"Willing","VENDITTI.localdomain.net","Linux 2.6.32-64GB-i686",58
"2016-05-17 19:04:58","209.87.31.2","udp",177,"kasei.cecm.sfu.ca","xdmcp",11105,"CA","BRITISH COLUMBIA","BURNABY",0,0,"Willing","kasei","0 users  load: 11., 11., 11.",45

Our 76 Report Types