OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
NTBugtraq And NTSecurity Archives: UDP 135 - Responding to &quo

UDP 135 - Responding to "aa" ??


Subject: UDP 135 - Responding to "aa" ??
From: WayneDiamondCS.com.au
Date: Wed Dec 29 1999 - 08:33:55 CST


Can somebody tell me what is happening here?
One day, for no reason in particular, I was testing a LAN UDP scanner, and
sent the packet "aa" to UDP:135
I received two packets back from the only machines that were alive in my LAN
(my workstation and the server)
 - both 84 bytes, with mostly undisplayable bytes (stripped here to ASCII
values)

-------
RECEIVED: From 10.0.0.2:135 ,84 bytes,
,4,6,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,155,254,E8,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,4,0,0,0,0,0,8,0,0,28,
RECEIVED: From 10.0.0.10:135 ,84 bytes,
,4,6,0,0,16,0,0,-,141,189,211,17,153,204,0,144,'.,183,v,8,0,0,0,0,0,0,0,8,0,
0,0RasAuto0,4,0,0,0,2,0,0,0,0,0,0,0,0,0,0,0,U,189,f,8,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,4,0,0,0,0,0,8,0,0,28
-------

All that from sending "aa" - why ? It only works if your local UDP port
_isn't_ 135, and it works with any string starting with "aa".
Sending "ba" or any other combinations that I've tried has resulted in
silence.

Can anyone tell me what this is?

Kind regards,
Wayne



This archive was generated by hypermail 2b27 : Wed Dec 29 1999 - 16:23:51 CST