Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Pulling WEP KEYs/MAC FILTER From Linksys/D-link ect

  1. #1
    Junior Member
    Join Date
    Jan 2003
    Posts
    7

    Pulling WEP KEYs/MAC FILTER From Linksys/D-link ect

    Dumb Newbie quesiton regarding this exploit:
    http://www.securiteam.com/securitynews/6P0021P60A.html
    (searched web and AO, I don't know where to look i guess)

    I Copied and pasted exploit to a file named "exploit" on my Slackware *nix box and tried to execute by doing sh ./exploit I've chmod 4711 it but to know avail I keep getting errors when I run the exploit:

    bash-2.05a# ./exploit
    ./exploit: typedef: command not found
    ./exploit: char: command not found
    ./exploit: char: command not found
    ./exploit: char: command not found
    ./exploit: char: command not found
    ./exploit: line 12: syntax error near unexpected token '}'
    ./exploit: line 12: '}'

    I'm sure i'm executing the script the wrong way
    Thanks

  2. #2
    Junior Member
    Join Date
    Jan 2003
    Posts
    7

    Pulling WEP KEYs/MAC FILTER From Linksys/D-link ect

    Dumb Newbie quesiton regarding this exploit:
    http://www.securiteam.com/securitynews/6P0021P60A.html
    (searched web and AO, I don't know where to look i guess)

    I Copied and pasted exploit to a file named "exploit" on my Slackware *nix box and tried to execute by doing sh ./exploit I've chmod 4711 it but to know avail I keep getting errors when I run the exploit:

    bash-2.05a# ./exploit
    ./exploit: typedef: command not found
    ./exploit: char: command not found
    ./exploit: char: command not found
    ./exploit: char: command not found
    ./exploit: char: command not found
    ./exploit: line 12: syntax error near unexpected token '}'
    ./exploit: line 12: '}'

    I'm sure i'm executing the script the wrong way
    Thanks

  3. #3
    Senior Member
    Join Date
    Sep 2001
    Posts
    144
    since it's a program and not a script.. you have to compile it.

  4. #4
    Senior Member
    Join Date
    Sep 2001
    Posts
    144
    since it's a program and not a script.. you have to compile it.

  5. #5
    Senior Member
    Join Date
    Nov 2002
    Posts
    186
    It's a c program, not a shell script. You have to compile it, not just make it executable.
    It would be best to save it as exploit.c and then run

    # cc exploit.c

    You can then run ./a.out to try the exploit.
    Good luck!
    \"When you say best friends, it means friends forever\" Brand New
    \"Best friends means I pulled the trigger
    Best friends means you get what you deserve\" Taking Back Sunday
    Visit alastairgrant.ca

  6. #6
    Senior Member
    Join Date
    Nov 2002
    Posts
    186
    It's a c program, not a shell script. You have to compile it, not just make it executable.
    It would be best to save it as exploit.c and then run

    # cc exploit.c

    You can then run ./a.out to try the exploit.
    Good luck!
    \"When you say best friends, it means friends forever\" Brand New
    \"Best friends means I pulled the trigger
    Best friends means you get what you deserve\" Taking Back Sunday
    Visit alastairgrant.ca

  7. #7
    Senior Member
    Join Date
    Feb 2002
    Posts
    518
    pretty wild... My old boss told me how impossible it is to get this stuff cracked with all the encryption... and then against my advice installed a linksys WAP in a bank system....
    Yikes.
    Remember -
    The ark was built by amatures...
    The Titanic was built by professionals.

  8. #8
    Senior Member
    Join Date
    Feb 2002
    Posts
    518
    pretty wild... My old boss told me how impossible it is to get this stuff cracked with all the encryption... and then against my advice installed a linksys WAP in a bank system....
    Yikes.
    Remember -
    The ark was built by amatures...
    The Titanic was built by professionals.

  9. #9
    Junior Member
    Join Date
    Jan 2003
    Posts
    7
    Algaen or anyone else that wants to help my dumb arse,

    I tried 'cc exploit.c -o exploit' and also 'gcc exploit.c -o exploit' .. However to no avail I keep getting errors

    bash-2.05a# cc exploit.c -o exploit
    exploit.c:8: parse error before character 0240
    exploit.c:8: warning: no semicolon at end of struct or union
    exploit.c:13: warning: `packed' attribute ignored
    exploit.c: In function `main':
    exploit.c:17: parse error before character 0240

    Thanks Algaen for your help..

    for those of you that want to try this exploit on windows boxes lookup pong.exe and wepcrck.exe on google.com. In regards to Avenger_jcc's post, this exploit only works if you are associated with the victim access point, also if you have updated firmware on your access point you should be in the clear for now!

  10. #10
    Leftie Linux Lover the_JinX's Avatar
    Join Date
    Nov 2001
    Location
    Beverwijk Netherlands
    Posts
    2,534
    it did compile for me (with 1 warning)

    gcc -c exploit.c -o exploit

    ./exploit

    got me an exception error (sigsev)

    so the compilation did work, the execution didn't..

    well too bad..

    tested on slackware 9.0 rc3 (build 14-03-2003)
    ASCII stupid question, get a stupid ANSI.
    When in Russia, pet a PETSCII.

    Get your ass over to SLAYRadio the best station for C64 Remixes !

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •